MCP Setup

ctxd exposes search and retrieval through a remote MCP endpoint. Any MCP-compatible agent that supports remote HTTP MCP servers can search your files.

Endpoint

URL: https://mcp.ctxd.dev/mcp

Authentication: Authorization: Bearer <your-api-key>

Client configuration

Configure your MCP client with the remote endpoint and bearer token. The exact config shape depends on the client, but it should include:

{
  "url": "https://mcp.ctxd.dev/mcp",
  "headers": {
    "Authorization": "Bearer your-api-key"
  }
}

For clients that use an mcpServers map, the configuration usually looks like:

{
  "mcpServers": {
    "ctxd": {
      "url": "https://mcp.ctxd.dev/mcp",
      "headers": {
        "Authorization": "Bearer your-api-key"
      }
    }
  }
}

No local CLI server command is required.

Available tools

The remote MCP server exposes three tools:

search

Search across all connected apps.

query: "text:deployment application:slack"

Returns a list of results with document_uid, title, url, optional snippet, is_snippet, and requires_fetch_for_full_text.

fetch_document

Fetch the full content of a specific document.

document_uid: "doc-uid-123"

Returns the full document text with metadata.

get_profile

Get the user’s connected integrations and file tree. Call this first to understand what data is available before searching.

Returns installed apps, connection status, and a hierarchical file tree of indexed files.

How agents use ctxd

A typical agent workflow:

Call get_profile to see what apps are connected and what files exist
Use the file tree to understand where data lives
Call search with a DSL query targeting the right apps and folders
Call fetch_document to get full content of specific results
Reason over the content and cite sources

title: ‘MCP Setup’