Setup snippets

Every MCP-capable AI tool has a config file where you register external servers. Snippets below for the most common tools.

These work for either the reader MCP or the author MCP — just substitute the right URL. Reader MCPs need no auth header; author MCPs do.

Claude Code

The fastest path is the CLI:

claude mcp add <server-name> --transport http <url>

For an author MCP (with auth):

claude mcp add <server-name> --transport http <url> --header "Authorization: Bearer <your-token>"

Or edit .mcp.json in your project root:

{
  "mcpServers": {
    "acme-docs": {
      "type": "http",
      "url": "https://docsio.co/api/mcp/<your-project-id>"
    }
  }
}

Restart Claude Code (or run /mcp in any session) to confirm the server is connected.

Cursor

Edit Cursor's MCP config — ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-workspace):

{
  "mcpServers": {
    "acme-docs": {
      "url": "https://docsio.co/api/mcp/<your-project-id>"
    }
  }
}

For an author MCP, add headers:

{
  "mcpServers": {
    "acme-docs-author": {
      "url": "https://docsio.co/api/mcp/author/<your-token>"
    }
  }
}

Restart Cursor.

VS Code (Copilot Chat with MCP)

Add to .vscode/mcp.json in your workspace:

{
  "servers": {
    "acme-docs": {
      "type": "http",
      "url": "https://docsio.co/api/mcp/<your-project-id>"
    }
  }
}

Reload VS Code.

OpenAI Codex

Run from your terminal:

codex mcp add acme-docs --url https://docsio.co/api/mcp/<your-project-id>

Or add to ~/.codex/config.toml:

[mcp_servers.acme-docs]
url = "https://docsio.co/api/mcp/<your-project-id>"

For an author MCP:

[mcp_servers.acme-docs-author]
url = "https://docsio.co/api/mcp/author/<your-token>"

Antigravity (Gemini)

Add to ~/.gemini/antigravity/mcp_config.json:

{
  "mcpServers": {
    "acme-docs": {
      "serverUrl": "https://docsio.co/api/mcp/<your-project-id>"
    }
  }
}

Restart Antigravity.

Generic JSON-RPC HTTP

For any tool that supports JSON-RPC over HTTP MCP transport:

POST <url>
Content-Type: application/json
Authorization: Bearer <token>   # author MCP only

{ "jsonrpc": "2.0", "method": "...", "params": {...}, "id": 1 }

Verifying

Once configured, ask your AI tool: "What MCP tools do you have available?" It should list either three (reader) or sixteen (author) tools prefixed with the server name you chose.

If they don't show up:

• Restart the tool fully (close and reopen, not just refresh).
• For author MCPs, double-check the token is correct and not yet revoked.
• Check the tool's MCP debug log — most have one (Claude Code: /mcp, Cursor: View > Output > MCP).

Multiple Docsio projects

You can register multiple Docsio MCP servers in the same tool — one per project. Use distinct names so the tool can call the right one:

{
  "mcpServers": {
    "acme-docs": { "url": "..." },
    "frontend-docs": { "url": "..." },
    "internal-docs": { "url": "..." }
  }
}

The AI tool decides which to call based on context.

Connection details

• Transport: HTTP (JSON-RPC over HTTPS).
• Streaming: not used; each tool call is a single request/response.
• Auth: none for reader MCP; Authorization: Bearer <token> for author MCP.
• Rate limits: liberal for reads, 5/hour per project for publish.