Connect an MCP client to the documentation server

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 research workflow that the Agent Runtime can use inside a Task to find and read public pages.

Suggested name: dualeai-docs
URL: https://api.beta.duale.ai/mcp
Transport: Streamable HTTP
Authentication: None

For 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 publishes discovery metadata shaped against pinned snapshots of the draft AI Catalog 1.0 format (opens in a new tab) and the experimental MCP Server Card format (opens in a new tab). Neither format is an accepted MCP core extension or a stable conformance target. 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 dualeai-docs --url https://api.beta.duale.ai/mcp

Verify with codex mcp list. The ChatGPT desktop app, Codex CLI, and Codex IDE extension share this configuration. See the Codex MCP documentation (opens in a new tab) 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.

1. Enter https://api.beta.duale.ai/mcp, then add or connect the connector.
2. In a conversation, select the + button, open Connectors, and enable the Duale AI connector.

See the Claude custom connector documentation (opens in a new tab) for plan-specific controls.

Claude Code

Add the server for all projects:

claude mcp add --transport http --scope user dualeai-docs https://api.beta.duale.ai/mcp

Verify with claude mcp list; use /mcp to inspect the tools. See the Claude Code MCP documentation (opens in a new tab) for project and managed configuration.

ChatGPT

Availability and setup depend on your plan and workspace role.

1. 1
   Enable developer mode

   Follow OpenAI’s plan-specific developer-mode instructions. Your plan can require a workspace administrator to grant access.

2. 2
   Create the app

   Under Settings → Apps or Workspace settings → Apps, start creating an app with https://api.beta.duale.ai/mcp and no authentication. Select Scan tools, confirm that the app exposes search and fetch, then select Create.

3. 3
   Use it in a conversation

   Start a new chat and select the app from the tools menu.

See OpenAI’s developer mode and MCP apps documentation (opens in a new tab) for plan and role requirements.

Cursor

Add the server globally in ~/.cursor/mcp.json:

{
  "mcpServers": {
    "dualeai-docs": {
      "url": "https://api.beta.duale.ai/mcp"
    }
  }
}

Verify with agent mcp list. See the Cursor MCP documentation (opens in a new tab) 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 dualeai-docs for the conversation and retry.

Use search and fetch

Choose the tool from the result you need:

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:

If these actions do not restore access, keep the exact error and the client details for support.