Serpkite MCP Server

SerpKite MCP

Give AI agents Google search and public web content through the SerpKite remote Model Context Protocol server. Maintained by the SerpKite team.

This repository contains connection examples and registry metadata for the hosted service. The API implementation is proprietary; the documentation and configuration in this repository are MIT licensed.

Connection

• Endpoint: https://api.serpkite.com/v1/mcp
• Transport: stateless Streamable HTTP
• Authentication: Authorization: Bearer <your-api-key>
• Protocols: 2025-06-18, 2025-03-26, 2024-11-05

Get an API key at app.serpkite.com. Read the pricing and MCP documentation. Credits never expire; failed and empty searches are free. Set a dedicated key's monthly credit limit to control agent spending.

OAuth is planned. Clients must currently support custom headers or use the stdio bridge below. No SerpKite npm MCP package is required.

Claude Code

claude mcp add --transport http serpkite https://api.serpkite.com/v1/mcp \
  --header "Authorization: Bearer $SERPKITE_API_KEY"

Cursor

Add to ~/.cursor/mcp.json or your project's .cursor/mcp.json:

{
  "mcpServers": {
    "serpkite": {
      "url": "https://api.serpkite.com/v1/mcp",
      "headers": { "Authorization": "Bearer ${env:SERPKITE_API_KEY}" }
    }
  }
}

VS Code

Add to .vscode/mcp.json. The password input keeps the API key out of the committed file:

{
  "inputs": [
    { "type": "promptString", "id": "serpkite-key", "description": "SerpKite API key", "password": true }
  ],
  "servers": {
    "serpkite": {
      "type": "http",
      "url": "https://api.serpkite.com/v1/mcp",
      "headers": { "Authorization": "Bearer ${input:serpkite-key}" }
    }
  }
}

Cline

Follow llms-install.md for Cline's remote connection configuration.

Claude Desktop and stdio clients

With Node.js installed, use the third-party mcp-remote bridge in your client's MCP configuration:

{
  "mcpServers": {
    "serpkite": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.serpkite.com/v1/mcp", "--header", "Authorization: Bearer ${SERPKITE_API_KEY}"],
      "env": { "SERPKITE_API_KEY": "YOUR_API_KEY" }
    }
  }
}

Keep API keys out of source control. ChatGPT connectors that only support OAuth or no authentication cannot currently connect directly.

Tools

Tool results are LLM-ready Markdown. Pricing follows the matching REST endpoints. Only public, logged-out pages are fetched. See tool inputs and costs.

Verify the connection

These metadata requests do not run searches:

curl https://api.serpkite.com/v1/mcp \
  -H "Authorization: Bearer $SERPKITE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"1.0"}}}'

curl https://api.serpkite.com/v1/mcp \
  -H "Authorization: Bearer $SERPKITE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'

The remote endpoint and all fourteen tool names were verified on 2026-10-05.

Support

Documentation · Status · support@serpkite.com

Google is a trademark of Google LLC. SerpKite is not affiliated with Google.