MCP Server

The documentation agent exposes an MCP (Model Context Protocol) server so AI coding tools — Claude Desktop, Claude Code CLI, and Cursor — can query the knowledge base as a native tool during conversations.

Transport

The MCP server uses HTTP transport (Streamable HTTP, the latest MCP protocol). This is different from the older stdio transport used by some MCP servers. All MCP-compatible clients that support HTTP transport can connect to it.

The server is available at:

https://your-host/mcp

Connecting Claude Desktop

Add the server to your claude_desktop_config.json:

{
  "mcpServers": {
    "cape-docs": {
      "type": "http",
      "url": "https://your-host/mcp",
      "headers": {
        "Authorization": "Bearer cape_..."
      }
    }
  }
}

Restart Claude Desktop after saving. The Cape documentation tools will appear in the tool list.

Connecting Claude Code (CLI)

claude mcp add cape-docs \
  --transport http \
  --url https://your-host/mcp \
  --header "Authorization: Bearer cape_..."

Or add it to your project's .claude/settings.json:

{
  "mcpServers": {
    "cape-docs": {
      "type": "http",
      "url": "https://your-host/mcp",
      "headers": {
        "Authorization": "Bearer cape_..."
      }
    }
  }
}

Connecting Cursor

In Cursor settings, go to MCP Servers and add:

{
  "cape-docs": {
    "type": "http",
    "url": "https://your-host/mcp",
    "headers": {
      "Authorization": "Bearer cape_..."
    }
  }
}

Available tools

The MCP server exposes the following tools:

search_docs

Semantic search over the knowledge base. Returns ranked document chunks.

Parameters:

Name	Type	Required	Description
query	string	Yes	The search query
source	string	No	Namespace filter (user_docs, tech_docs, api_endpoints, confluence)
topK	number	No	Max results (1–20). Default: 5

ask_docs

Ask a natural language question. Returns a generated answer grounded in the documentation, with source attribution.

Parameters:

Name	Type	Required	Description
question	string	Yes	The question to answer
source	string	No	Namespace filter
retrieval	string	No	standard or smart. Default: standard
language	string	No	BCP 47 language code. Auto-detected if omitted.

Authentication

All MCP requests require a valid API key. Create one in the API Keys section of the admin panel and include it as a Bearer token in the Authorization header (as shown in the configuration examples above).

Rate limiting configured on the key applies to MCP requests as well.

Usage example

Once connected, you can ask Claude or Cursor to use the knowledge base directly:

"Using the cape-docs MCP tool, find how asset collections work"

The tool will retrieve relevant documentation chunks and include them in Claude's context, grounding the response in the actual documentation.