Access, auth, and limits
Point your client at https://mcp.searchable.com/mcp and sign in. Searchable uses OAuth 2.1 with PKCE and Dynamic Client Registration, so the client registers itself, opens Searchable in your browser, and shows a consent screen listing what it will be allowed to do. No API key in a config file, and origin validation on the server side. Probed on 2026-07-30, an unauthenticated JSON-RPC initialize returns 401, so the endpoint is live and genuinely gated. An API-key connection is still documented as the legacy path if your client cannot do OAuth.
The plan rule is simple and worth stating plainly: MCP requires a paid Searchable plan, and both connection methods are unavailable on the free plan, as are API keys. Once you are paying, though, there is no further tier-gating, MCP is listed on Pro at $125/mo exactly as it is on Enterprise at $999/mo. Safety defaults are sensible: read-only unless you grant write scope, and the three write tools (generate_report, trigger_audit, refresh_sitemap) are the low-risk kind.
Where it works and what to build
Client coverage is broad because it is a remote streamable-HTTP server: Claude.ai on web and mobile as a connector, Claude Desktop and Claude Code, ChatGPT through developer-mode connectors, Cursor, Windsurf, and anything else that speaks MCP. Nothing to install per machine, and interactive cards render results inline in clients that support them.
Where it earns its keep is the question a dashboard makes tedious. Ask why your visibility on a topic dropped, and the agent can pull get_visibility_by_topic, check get_share_of_voice against competitors, look at which domains the models cited with search_sources, then cross-reference get_gsc_performance and get_ai_traffic to see whether real traffic moved with it. That chain is four dashboards and a spreadsheet by hand. With write scope granted it can finish by calling trigger_audit and generate_report so the follow-up work is queued and the summary is ready to send.
Which AI clients can use Searchable MCP?
Not every AI assistant supports MCP natively. Per-client picture for Searchable:
| Client | Support | Notes |
|---|---|---|
| Claude (Desktop/Web) | Via connectors | Added as a connector on Claude.ai (web and mobile) and Claude Desktop; OAuth sign-in, no key pasting. |
| Claude Code | Native MCP | Documented client for the mcp.searchable.com/mcp streamable HTTP server. |
| ChatGPT | Via connectors | Supported through ChatGPT developer-mode connectors. |
| Cursor | Native MCP | Standard MCP config against the same server URL. |
| Windsurf | Native MCP | Listed as supported alongside any other MCP-compatible client. |
How to connect Searchable 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": {
"searchable": {
"command": "npx",
"args": ["mcp-remote", "<YOUR_MCP_URL>"]
}
}
}
// HTTP-transport MCP. Get your <YOUR_MCP_URL> from the vendor dashboard.
// Server source: https://mcp.searchable.com/mcp
// Claude Code (one-liner): claude mcp add searchable <YOUR_MCP_URL> --transport httpSome MCP servers require an API key. Check the source page for setup: mcp.searchable.com/mcp.
Does Searchable MCP cost extra?
Searchable ships an official MCP server that uses your existing subscription credentials.
- No separate MCP licence to buy. You pay for your Searchable 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.
Searchable also publishes a REST API
Searchable publishes an API, but per-tier gating wasn't extracted automatically.
What you can do with Searchable 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 Searchable 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 Searchable account
- Multi-account workflows without context-switching the Searchable UI
- Reports you'd normally spend hours on, done before standup
Production agent workflows
- Embed in your internal Codex / Cursor agents that triage Searchable data daily
- Combine with other MCP servers in a multi-step agent chain
- Constrain agents to read-only roles to keep production Searchable safe
Limits and gotchas
- Official MCP server — published by Searchable 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 (bearer). Expect to configure that on first install.
- Rate limits: MCP calls count against your underlying Searchable API quota. Burst usage from a curious agent can drain a daily allowance fast.
Agent-readiness verdict
A 9, and the reason Searchable is worth a look even next to cheaper trackers. The surface is broad enough that an agent can run a real investigation rather than fetch one metric, the auth is the modern pattern rather than a key in a JSON file, read-only-by-default with scoped writes is the right safety posture, and access is on the $125 entry plan instead of behind an enterprise upsell. What keeps it off a 10: no webhooks, so an agent cannot be woken by a change, and MCP needs a paid plan, so there is no free way to prototype against it.
One of the widest MCP surfaces in AI search, and it sits on the entry plan rather than behind an enterprise upsell. Searchable's official server at mcp.searchable.com/mcp exposes 52 read-only tools covering visibility (get_visibility_by_prompt, get_visibility_by_topic, get_share_of_voice, get_competitors), sources and citations (search_sources, get_source_domain, get_source_page_content), sentiment history, query fanout, prompts and raw AI answers, site health and page audits, content and opportunities, plus the traffic joins most rivals skip (get_ga4_traffic, get_gsc_performance, get_ai_traffic) and get_shopping_visibility and get_ads. Writes are scope-gated to three low-risk actions (generate_report, trigger_audit, refresh_sitemap). Auth is OAuth 2.1 with PKCE and Dynamic Client Registration, so nothing is pasted into a config file. The REST API at app.searchable.com uses sea_-prefixed Bearer keys with read/write/admin scopes and optional project binding, documented with an interactive playground, idempotency and an error reference, alongside a separate ingest API for AI-bot traffic with edge recipes for Vercel, Cloudflare, Netlify, Fastly, Akamai, CloudFront and GCP. Short of a 10 because there are no webhooks (alerting means polling), no first-party API client SDK, and MCP and API keys both require a paid plan, so there is no free way to prototype.
Scored by Joonas (TMB).
Searchable MCP & API FAQ
Is the Searchable MCP server official?+
Can I use the Searchable MCP with Cursor or Codex?+
Does Searchable have a public API?+
Sources
- Searchable official site: https://www.searchable.com
- MCP server page: https://mcp.searchable.com/mcp
- API docs: https://docs.searchable.com/advanced/api-usage
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.