MCP server (AI agents)

Crisps ships a native Model Context Protocol server, so an LLM (Claude, Cursor, or any MCP client) can discover and call your search & extract tools at runtime — no glue code.

POST /mcp — a JSON-RPC 2.0 endpoint (Streamable-HTTP transport).

Tools

Tool	Maps to	Description
`search`	`/search`	Web search with clean extracted content.
`extract`	`/extract`	Extract content from specific URLs.

Authenticate with your API key as a Bearer token, exactly like the REST API:

POST /mcp
Authorization: Bearer csp_live_…
Content-Type: application/json

Discover the tools

An MCP client begins with tools/list:

curl -X POST https://api.crisps.ai/mcp \
  -H "Authorization: Bearer $CRISPS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "jsonrpc": "2.0", "id": 1, "method": "tools/list" }'

Call a tool

curl -X POST https://api.crisps.ai/mcp \
  -H "Authorization: Bearer $CRISPS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/call",
    "params": {
      "name": "search",
      "arguments": { "query": "state of MoE routing 2026", "search_depth": "advanced" }
    }
  }'

Connect from Claude

Add Crisps as a remote MCP server — from the dashboard (MCP Server card generates a ready config), or directly:

Claude Code (CLI)
Config (JSON)

claude mcp add --transport http crisps https://api.crisps.ai/mcp \
  --header "Authorization: Bearer csp_live_…"

{
  "mcpServers": {
    "crisps": {
      "type": "http",
      "url": "https://api.crisps.ai/mcp",
      "headers": { "Authorization": "Bearer csp_live_…" }
    }
  }
}