MCP Client Setup

Point your AI agent at Pathfinder. Any client that supports Streamable HTTP transport works.

Client Configurations

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json (macOS)

Claude Desktop uses its own config file with mcpServers as the top-level key.

{ "mcpServers": { "docs": { "type": "http", "url": "http://localhost:3001/mcp" } } }

Claude Code

~/.claude/mcp.json

Claude Code uses a separate config file with mcp-servers as the key.

{ "mcp-servers": { "docs": { "type": "http", "url": "http://localhost:3001/mcp" } } }

Cursor

.cursor/mcp.json

Place this in your project root. Cursor picks it up automatically.

{ "mcpServers": { "docs": { "type": "http", "url": "http://localhost:3001/mcp" } } }

OpenAI Codex

codex CLI --mcp-config

Codex supports MCP servers via the --mcp-config flag or a config file. Pass a JSON file with the server definition:

{ "mcpServers": { "docs": { "type": "http", "url": "http://localhost:3001/mcp" } } }

VS Code (Continue)

~/.continue/config.json

Add Pathfinder to the mcpServers section of your Continue config:

{ "mcpServers": [ { "name": "docs", "transport": { "type": "http", "url": "http://localhost:3001/mcp" } } ] }

Generic (Streamable HTTP)

Any MCP-compatible client

Pathfinder exposes a single Streamable HTTP endpoint. Any MCP client that supports this transport can connect with:

# Endpoint URL: http://localhost:3001/mcp Transport: Streamable HTTP Method: POST

Remote Servers

For deployed Pathfinder instances, replace localhost:3001 with your server's URL:

{ "mcpServers": { "docs": { "type": "http", "url": "https://docs.example.com/mcp" } } }

Pathfinder handles session management automatically. Each MCP connection gets its own session with independent state (working directory, workspace, etc.).

Verifying the Connection

Once connected, your agent should see Pathfinder's tools in its available tools list. The exact tools depend on your configuration — typically a combination of search and bash tools.

Try asking your agent to run a simple command like find / -name "*.md" | head -5 to verify the bash tool is working, or ask a question about your docs to test semantic search.