Connect an MCP client to the documentation server
The Duale AI MCP server lets clients search documentation and fetch complete pages with canonical URLs without an account or API key.
Connect an MCP client to the Duale AI documentation server to search and fetch pages using a public, read-only endpoint with no authentication.
- Search returns up to eight matches with page IDs; fetch returns the full indexed page.
- Published changes become searchable within six minutes, and page IDs remain stable across updates.
- Raw query text is excluded from telemetry; derived embeddings may persist about one year.
- Discovery complies with AI Catalog 1.0 and MCP Server Card specifications at a well-known URL.
Summaries were generated by AI. Generative AI is experimental.
Connect an MCP client to the Duale AI documentation server to search documentation and fetch complete pages with canonical URLs. The public, read-only server requires no account or API key.
This server searches Duale AI documentation. It is separate from the Web search that an agent can use inside a task to find and read public pages.
Suggested name: duale-docs
URL: https://api.beta.duale.ai/mcp
Transport: Streamable HTTP
Authentication: NoneFor a client not listed below, add a remote Streamable HTTP server with these values and leave authentication empty.
How clients find this server
Duale AI’s public MCP discovery complies with the AI Catalog 1.0 specification and the
MCP Server Card specification. Clients can
retrieve the catalog at
https://duale.ai/.well-known/ai-catalog.json.
Connect a client
Choose your client below, add the same read-only endpoint, then run the verification step for that client.
Codex
Add the server:
codex mcp add duale-docs --url https://api.beta.duale.ai/mcpVerify with codex mcp list. The ChatGPT desktop app, Codex CLI, and Codex IDE extension share this configuration. See
the Codex MCP documentation for other scopes and interfaces.
Claude.ai and Claude Desktop
On Team and Enterprise plans, an owner must first add the custom connector under Admin settings → Connectors. Members can then find it under Settings → Connectors. On Free, Pro, and Max plans, select Settings → Connectors → Add custom connector.
- Enter
https://api.beta.duale.ai/mcp, then add or connect the connector. - In a conversation, select the + button, open Connectors, and enable the Duale AI connector.
See the Claude custom connector documentation for plan-specific controls.
Claude Code
Add the server for all projects:
claude mcp add --transport http --scope user duale-docs https://api.beta.duale.ai/mcpVerify with claude mcp list; use /mcp to inspect the tools. See the
Claude Code MCP documentation for project and managed configuration.
ChatGPT
Availability and setup depend on your plan and workspace role.
- Enable developer mode
Follow OpenAI’s plan-specific developer-mode instructions. Your plan can require a workspace administrator to grant access.
- Create the app
Under Settings → Apps or Workspace settings → Apps, start creating an app with
https://api.beta.duale.ai/mcpand no authentication. Select Scan tools, confirm that the app exposessearchandfetch, then select Create. - Use it in a conversationStart a new chat and select the app from the tools menu.
See OpenAI’s developer mode and MCP apps documentation for plan and role requirements.
Cursor
Add the server globally in ~/.cursor/mcp.json:
{
"mcpServers": {
"duale-docs": {
"url": "https://api.beta.duale.ai/mcp"
}
}
}Verify with agent mcp list. See the Cursor MCP documentation for project-scoped
configuration.
Verify the connection
Use this prompt:
Use the Duale AI documentation server to explain how model routing works. Fetch the most relevant page and cite its
canonical URL.Success means the client calls search, passes one returned page ID to fetch, and cites a https://duale.ai/ URL. If
it answers without using the tools, enable duale-docs for the conversation and retry.
Use search and fetch
Choose the tool from the result you need:
- Tool
search- Input
- A natural-language
queryof 1–1,000 characters - Result
- Up to eight matches from distinct pages. Each match contains an opaque page
id, matched title, excerpt, and canonical URL.
- Tool
fetch- Input
- An exact page
idreturned bysearch - Result
- The current indexed page, including its
id, page title, complete indexed text, and canonical URL.
Pass a page ID returned by search to fetch. IDs are opaque, and fetch returns the current full page even when
search matched a section.
Content updates
Published changes normally become searchable within six minutes. Page IDs remain stable across updates, and fetch
returns the current indexed page. If a page was removed and fetch rejects its ID, search again.
Protect search data
Use the server for public documentation questions. Do not put secrets or personal data in a query. The service excludes raw query text from application telemetry, but it can retain a derived query embedding for about one year. See the Privacy notice.
Troubleshoot the MCP connection
Match the symptom to the first recovery action:
- Symptom
- The client cannot connect
- Action
- Use the exact
/mcpURL, Streamable HTTP transport, and no authentication.
- Symptom
- The client does not show the tools
- Action
- Refresh or reconnect the server, then confirm that
searchandfetchare enabled.
- Symptom
- Search is unavailable or times out
- Action
- Retry the request. If it still fails, reconnect the server and keep the exact error to report.
If these actions do not restore access, keep the exact error and the client details for support.