Hosted, local, or self-hosted

Three ways to run Datpaq through MCP. Use the hosted endpoint if you want zero install and a streamable-HTTP URL you can paste into any client. Use the bundled stdio server from the Datpaq CLI if you'd rather keep the auth token on disk, work offline, or expose your locally-synced SQLite database to the agent via the search and sql tools that the hosted surface intentionally omits. Or self-host the HTTP server from github.com/datpaq/mcp when you need the streamable-HTTP transport on your own infrastructure.

Hosted (recommended)

URL: https://mcp.datpaq.com/ — streamable HTTP, authenticates with your Datpaq API key, 34 tools across 13 active interfaces.

Local stdio

go install github.com/datpaq/cli/cmd/datpaq-mcp@latest
datpaq auth login

Self-hosted (HTTP)

Same MCP surface as the hosted endpoint, running on your own infrastructure. Docker image and Fly.io config ship in the repo — see the README for the full deploy flow. Each request authenticates with the user's own Datpaq API key as Authorization: Bearer <key> — no server-side credential to configure.

go install github.com/datpaq/mcp/cmd/datpaq-mcp-http@latest
datpaq-mcp-http --addr :8080

Claude Desktop

Add the block below to claude_desktop_config.json. On macOS the file lives at ~/Library/Application Support/Claude/claude_desktop_config.json; on Windows it's under %APPDATA%\Claude\claude_desktop_config.json. Restart Claude Desktop after editing.

{
  "mcpServers": {
    "datpaq": {
      "url": "https://mcp.datpaq.com/",
      "headers": {
        "Authorization": "Bearer YOUR_DATPAQ_API_KEY"
      }
    }
  }
}

Cursor

Cursor reads MCP servers from ~/.cursor/mcp.json (global) or .cursor/mcp.jsonin your workspace root (project-scoped). The schema is identical to Claude Desktop's.

{
  "mcpServers": {
    "datpaq": {
      "url": "https://mcp.datpaq.com/",
      "headers": {
        "Authorization": "Bearer YOUR_DATPAQ_API_KEY"
      }
    }
  }
}

Codex

Codex stores MCP servers in ~/.codex/config.toml. Use the CLI to add the hosted Datpaq server, and keep your API key in an environment variable instead of hardcoding it in the config file.

export DATPAQ_API_KEY="YOUR_DATPAQ_API_KEY"
codex mcp add datpaq --url https://mcp.datpaq.com/ --bearer-token-env-var DATPAQ_API_KEY

Equivalent config.toml entry:

[mcp_servers.datpaq]
url = "https://mcp.datpaq.com/"
bearer_token_env_var = "YOUR_DATPAQ_API_KEY"

Cline / Continue / others

Most VS Code-based MCP clients (Cline, Continue, Codeium agents) ship a settings UI for MCP servers. Choose "HTTP" or "streamable HTTP" as the transport, paste the Datpaq URL, and add the Authorization header. Any client following the public MCP transport spec works the same way.

Authenticate

Every request needs your Datpaq API key in the Authorization header. The hosted server validates presence and shape, then forwards the key to the Datpaq API on each tool call. Keys are never stored, logged, or shared.

Authorization: Bearer YOUR_DATPAQ_API_KEY

Grab a key from the Datpaq dashboard — same one you use for the CLI and direct API calls. Rate limits and quotas track to your existing plan.

Verify the connection

Restart your client. In Codex, run /mcp or open the MCP panel and confirm the datpaq server is connected with 34 tools. Claude Desktop and Cursor show the server status in their MCP panels.

For an out-of-client smoke test, hit the endpoint with curl:

curl -s -X POST https://mcp.datpaq.com/ \
-H "Authorization: Bearer $YOUR_DATPAQ_API_KEY" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"curl","version":"0"}}}'

A successful initialize handshake returns a JSON-RPC result with protocolVersion and an Mcp-Session-Id response header. A 401 with a WWW-Authenticate header means the Bearer token is missing or malformed.

Try a prompt

Ask the agent to do something the Datpaq API can answer. It will pick the right tool and parameters automatically — no glue code, no client SDK.

Use the Datpaq whois tool to look up example.com and tell me the registrar and expiry date.

Troubleshoot

• 401 from /mcp: the Authorization header is missing or malformed. The header must be exactly Authorization: Bearer YOUR_KEY.
• 401 on a tool call (after a clean handshake): the Datpaq API rejected the key. Check it in the dashboard, or run datpaq doctor from the CLI against the same key.
• Server connects but no tools appear: the client may have cached an earlier failed handshake. Remove and re-add the server entry, then restart the client.
• Network errors behind a corporate proxy: streamable HTTP rides on standard POST+ chunked responses, so any proxy that allows GitHub or NPM will allow Datpaq too. SSE-strict proxies don't apply.
• Tools I expected aren't there: the hosted surface is curated to the 13 active production interfaces, and excludes the CLI's local-state and shell-out tools. Run the bundled stdio server from the CLI for the full developer set.