Access, auth, and limits
SearchApi MCP authenticates via the integration URL issued from your dashboard. The URL is scoped to your account and embeds the API key, so there is no separate Authorization header to configure in your MCP client. Create an integration in the dashboard, copy the MCP URL, paste it into Claude Code, Claude Desktop, or Cursor. Every MCP call counts as a SearchApi search and draws down the same monthly quota as direct REST API calls, billed on the pay-per-success model (only 200 responses are charged).
No separate MCP-tier pricing, no MCP-only minimum: if you are on the $40/mo Developer plan (10,000 searches) and your agent makes 200 SERP calls in an afternoon, that is 200 searches off your monthly cap. Plan accordingly when wiring agents to the MCP. There is no documented sandbox for free MCP testing, so prototyping agent workflows draws from your real credit balance from the first call.
Where it works and what to build
Setup is one command per client. Claude Code: claude mcp add searchapi <YOUR_MCP_URL> --transport http. Claude Desktop: add an mcpServers entry to claude_desktop_config.json that uses npx mcp-remote against the dashboard URL (requires Node.js installed locally). Cursor: one-click deeplink install from the integrations page. ChatGPT works via custom connectors against the same REST API. Gemini chat has no native MCP client and stays API-only via Gemini Code Assist or custom code.
Workflows worth wiring once MCP is connected: ask Claude where your 50 target keywords rank across Google and Bing this week and have it group results by SERP-feature presence (AI Overview, Featured Snippet, People Also Ask). Drop a topic into Cursor and have the agent pull top-10 organic plus AI Overview citations from SearchApi, then draft a brief based on what is ranking today rather than what training data thinks. Run a scheduled local-pack audit across 100 location-keyword combinations and route the JSON into Slack via n8n. Pull competitor video performance from the YouTube engine and Amazon search rankings from the Amazon engine in the same agent context, which most single-vendor SEO MCPs cannot do.
Which AI clients can use SearchApi MCP?
Not every AI assistant supports MCP natively. Per-client picture for SearchApi:
| Client | Support | Notes |
|---|---|---|
| Claude (Desktop/Web) | Native MCP | Connect via the dashboard-issued MCP URL using npx mcp-remote in claude_desktop_config.json. |
| Claude Code | Native MCP | One-line setup: claude mcp add searchapi <YOUR_MCP_URL> --transport http |
| ChatGPT | Via connectors | Works via ChatGPT custom connectors against the REST API. |
| Cursor | Native MCP | One-click deeplink install from the SearchApi integrations page. |
| Codex | Native MCP | — |
| Windsurf | Native MCP | — |
| Cline | Native MCP | — |
| Gemini | API-only (custom code) | Gemini chat has no native MCP client; call the REST API directly from Gemini Code Assist or custom code. |
| n8n | Native MCP | MCP HTTP node or direct REST call via SearchApi credentials. |
How to connect SearchApi MCP to Claude Desktop
Add this block to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Cursor and Codex use a similar schema.
{
"mcpServers": {
"searchapi": {
"command": "npx",
"args": ["mcp-remote", "<YOUR_MCP_URL>"]
}
}
}
// HTTP-transport MCP. Get your <YOUR_MCP_URL> from the vendor dashboard.
// Server source: https://www.searchapi.io/integrations/mcp
// Claude Code (one-liner): claude mcp add searchapi <YOUR_MCP_URL> --transport httpSome MCP servers require an API key. Check the source page for setup: searchapi.io/integrations/mcp.
Does SearchApi MCP cost extra?
SearchApi ships an official MCP server that uses your existing subscription credentials.
- No separate MCP licence to buy. You pay for your SearchApi plan, the MCP server queries that account.
- Whether it's gated to a specific tier wasn't extracted automatically — verify the access requirements on the MCP page or pricing docs.
SearchApi also publishes a REST API
SearchApi publishes an API, but per-tier gating wasn't extracted automatically.
What you can do with SearchApi from an AI agent
Three shapes of agent workflow. Pick the row that matches how you actually use Claude / Cursor / Codex day to day.
Skip the dashboard, ask Claude
- "What keywords moved this week?" answered in seconds
- Quick one-off questions without leaving the editor
- Pipe SearchApi data into your personal notes / docs without writing a script
Run client analysis at agent speed
- Hand the MCP server to your team — every consultant can ask Claude about any client's SearchApi account
- Multi-account workflows without context-switching the SearchApi UI
- Reports you'd normally spend hours on, done before standup
Production agent workflows
- Embed in your internal Codex / Cursor agents that triage SearchApi data daily
- Combine with other MCP servers in a multi-step agent chain
- Constrain agents to read-only roles to keep production SearchApi safe
Limits and gotchas
- Official MCP server — published by SearchApi themselves, so it should track product changes.
- Fallback: the REST API works for any flow the MCP server doesn't cover.
- Auth flow: MCP servers usually inherit the underlying API auth method (api-key). Expect to configure that on first install.
- OpenAPI spec is published — easy to validate which endpoints the MCP server actually exposes vs the full API surface.
- Rate limits: MCP calls count against your underlying SearchApi API quota. Burst usage from a curious agent can drain a daily allowance fast.
Agent-readiness verdict
Score: 9/10 on MCP-readiness. SearchApi is one of the cleanest agent-native APIs on the market: official MCP server on the vendor's own domain, HTTP transport (no legacy stdio package wrangling), multi-client out of the box (Claude Desktop + Claude Code + Cursor), and breadth across 50+ engines covering search, social, marketplace, travel, and ad libraries under one wire-up. The score is not a 10 because heavy agent traffic shares the same pay-per-success quota as direct REST calls (a Developer-tier $40/mo plan goes fast if Claude fires 100+ SERP calls per session) and there is no native AI-Overview citation tracking at the depth DataForSEO's AI Optimization API offers.
Solid agent fit with official MCP support. SearchApi publishes its own MCP server and maintains OpenAPI documentation, making it straightforward to integrate into Claude and Cursor workflows. The main limitation is the absence of native structured outputs, which means you'll need to handle JSON parsing on your end rather than relying on the model to enforce response schemas.
Scored 2026-06-07 by Joonas (TMB).
SearchApi MCP & API FAQ
Is the SearchApi MCP server official?+
Can I use the SearchApi MCP with Cursor or Codex?+
Does SearchApi have a public API?+
Does SearchApi publish an OpenAPI / Swagger spec?+
Sources
- SearchApi official site: https://www.searchapi.io
- MCP server page: https://www.searchapi.io/integrations/mcp
- API docs: https://www.searchapi.io/docs/google
Data verified by Joonas on the dates shown. MCP server status auto-rechecked weekly.
10+ years in digital marketing. I review marketing software for AI-stack fit: real pricing, MCP and API support, and how cleanly each tool drops into an AI agent workflow, cross-checked against verified data and real user feedback.