OAuth MCP and subscriber APIs

Connect AI agents to Devano

Use Devano's MCP servers as the general integration path for Claude, ChatGPT, Codex, and other AI clients.

Connect with MCP

MCP is the preferred integration path when an AI client needs to search, inspect, and summarize Devano biomedical data. Add the product-specific remote MCP server URL in your client, complete the OAuth sign-in flow, and the client can call only the tools your Devano account is allowed to use.

1. Choose a product

Select the Devano data product you want the agent to use, such as GEO Index, GWAS Index, QTL Index, or LitTrack.

2. Add the MCP URL

Configure the remote Streamable HTTP server in Claude, ChatGPT, Codex, or another MCP-capable client.

3. Sign in with Devano

Approve the OAuth request using a Devano account with access to the selected product.

Endpoints Each product is its own server

Use the base URL with the product slug — no trailing path.

https://devano.ai/mcp/{server}

geo-index gwas-index lit-tracker qtl-index

Static token Fallback for headless clients

Static tokens are a fallback for headless clients and automation that cannot complete the OAuth flow. Devano issues these tokens directly to approved organizations — contact your account team to request one. Keep them out of source control and rotate them when team membership or infrastructure changes.

Claude

Claude.ai and Claude apps

Add a custom web connector in Claude connector settings.
Provide the Devano MCP server URL for the product you want to use.
Complete the Devano OAuth flow.
Enable the connector in the conversations where Claude should use Devano tools.

Claude Code

Register the Devano server in your project with claude mcp add.
Open the MCP panel with /mcp if Claude Code prompts for OAuth and verify your Devano account.

bash

claude mcp add --transport http devano-geo-index \
  https://devano.ai/mcp/geo-index

OpenAI and Codex

ChatGPT and OpenAI apps

In an OpenAI app or workspace, add a custom app for the Devano MCP server.
Use the product-specific MCP URL and complete OAuth when prompted.
Invoke the connected app from chat when you want ChatGPT to search or inspect Devano data.

Codex

Codex supports remote Streamable HTTP MCP servers. Add the server to your Codex MCP configuration, then start the OAuth login flow.

config.toml

[mcp_servers.devano_geo_index]
url = "https://devano.ai/mcp/geo-index"

bash

codex mcp login devano_geo_index

MCP servers

Devano MCP servers expose product-specific tools over Streamable HTTP. Each server is mounted separately so clients discover only the tools for the data product they connect to.

Product	URL	Good for	Representative tools
GEO Index	`/mcp/geo-index`	Searching curated GEO studies, contrasts, samples, and evidence.	`corpus_overview`, `search_studies`, `list_contrasts`, `study_detail`, `contrast_detail`, `sample_evidence`
GWAS Index	`/mcp/gwas-index`	Finding traits, studies, associations, and paper-level evidence.	`trait_map`, `search_studies`, `search_associations`, `study_detail`, `paper_overview`, `compare_studies`
LitTrack	`/mcp/lit-tracker`	Reviewing tracked literature corpora and compiling paper reports.	`corpus_overview`, `list_papers`, `recent_papers`, `paper_detail`, `compile_report`, `get_saved_papers`
QTL Index	`/mcp/qtl-index`	Searching QTL studies, cohorts, entities, and available result tables.	`search_studies`, `study_detail`, `search_entities`, `list_cohorts`, `list_tables`, `query_table`

Clients that use a static token set it as a bearer header in the server config:

mcp.json

{
  "mcpServers": {
    "devano-qtl-index": {
      "url": "https://devano.ai/mcp/qtl-index",
      "headers": {
        "Authorization": "Bearer dvno_your_token_here"
      }
    }
  }
}

Subscriber APIs

Devano does not currently offer general public APIs. For general developer integrations, connect through the MCP servers documented above.

If your subscription includes a dedicated API service, the full endpoint reference, credentials, examples, and service-specific limits are available from your logged-in Devano workspace or provided directly with that service.

Errors and limits

HTTP status codes

200 request succeeded.
400 malformed JSON or invalid request parameters.
401 missing, revoked, expired, or invalid token.
403 account or token is valid but does not have access to that product or resource.
404 the requested resource was not found for your organization.
429 rate limit exceeded.

Rate limits

Authenticated MCP and subscriber API calls are rate limited by account, organization, and service. Subscriber API responses include rate-limit headers when applicable.

X-RateLimit-Limit maximum requests per window.
X-RateLimit-Remaining requests left in the current window.
Retry-After seconds to wait after a 429.