cloro
Query ChatGPT, Gemini, Perplexity, Copilot, Grok, Google AI Mode, and Google Search/News from any country as MCP tools.
Documentation
MCP server: give any agent cloro's monitoring tools
Connect Claude, Cursor, or any MCP client to cloro's hosted MCP server and query ChatGPT, Gemini, Google AI Mode, Bing AI Mode, Google Search, and Google News.
The cloro MCP server exposes cloro's sync monitor endpoints as tools for any MCP-capable client: Claude, Claude Code, Cursor, or your own agent. Ask your agent to "check whether ChatGPT recommends us for best SERP API" and it calls the cloro API and reasons over the parsed result: the answer text and the sources it cited.
The server is a thin wrapper over api.cloro.dev holding no business logic and no secrets: each request forwards your own credential, either a cloro API key or an OAuth access token, so the API enforces authentication, credit billing, rate limiting, and concurrency limits. Tool input schemas are the same schemas the API validates with, so the MCP contract can't drift from the API reference.
Prerequisites
- An MCP-capable client (Claude, Claude Code, Cursor, or any other)
- A cloro account with credits at dashboard.cloro.dev
Connect Claude with OAuth
In Claude (web or desktop), you sign in to cloro in the browser. You do not paste an API key.
- Go to Customize → Connectors and select Add custom connector.
- Enter
https://mcp.cloro.dev/mcpas the URL. - Under Authentication, choose Sign in when needed.
- Ask Claude to use a cloro tool. Claude shows a Connect prompt. Sign in to cloro and select the organization whose credits pay for the calls.
[!NOTE]
Claude can preselect No sign-in, because the server lists its tools before you sign in. Change it to Sign in when needed.
Connect other clients with an API key
For every other client, use a cloro API key (see Authentication). The hosted server speaks Streamable HTTP. Pass your API key in the URL path so it works even in clients that can't set custom headers:
{
"mcpServers": {
"cloro": {
"type": "http",
"url": "https://mcp.cloro.dev/YOUR_CLORO_API_KEY/mcp"
}
}
}
If your client can set headers, you can instead point it at https://mcp.cloro.dev/mcp and send your key as Authorization: Bearer YOUR_CLORO_API_KEY.
[!TIP]
In Claude Desktop and Cursor, add this block to the app's MCP settings (Settings → Developer / MCP). In Claude Code, run
claude mcp add --transport http cloro https://mcp.cloro.dev/mcp, then run/mcpin a session to sign in with OAuth. No API key is needed.
Available tools
| Tool | Endpoint |
|---|---|
scrape_chatgpt | POST /v1/monitor/chatgpt |
scrape_gemini | POST /v1/monitor/gemini |
scrape_google_ai_mode | POST /v1/monitor/aimode |
scrape_bing_aimode | POST /v1/monitor/bing/aimode |
scrape_google | POST /v1/monitor/google |
scrape_google_news | POST /v1/monitor/google/news |
resolve_google_redirect | POST /v1/monitor/google/goto |
list_countries | GET /v1/countries |
list_states | GET /v1/states |
Leave include unset on the scrape tools for the leanest response. Use list_countries (optionally filtered by model) and list_states (with a country) to discover valid geo-targeting codes.
The server has no Grok, Copilot, or Perplexity tools, and list_countries does not accept them as a model.
Resolve empty Google links
A Google Search, Google News, or AI Mode result can come back with an empty or missing link, or a google.com/goto URL, alongside a redirectLink. Your agent passes that redirectLink to resolve_google_redirect, which returns { "url": "..." } with the destination. If the link does not resolve, the tool returns a 502. Retry it later.
Credit costs
Each tool description states its credit cost, and the server sends the same cost rules to your agent as instructions:
- Scrape tools: each call is a sync request, billed at the provider's base rate plus any add-ons plus the +2 sync surcharge. Each call counts against your concurrency limits.
resolve_google_redirect: 1 credit, with no sync surcharge, charged only when the destination comes back.list_countriesandlist_states: free.
Each tool result includes credits.charged and credits.remaining. For large batches, such as tracking many prompts across engines, use the async API directly instead of looping tool calls. It has no sync surcharge.
Example prompts
- "Ask ChatGPT what the best SERP APIs are and list which vendors it cites."
- "Compare how ChatGPT and Gemini answer 'best CRM for startups'. Which sources do they cite?"
- "Does Google's AI Overview for 'ai visibility tracking' mention cloro? Check in the US and Germany."
- "Pull the latest Google News articles about our brand."
- "Get the top 10 Google results for 'ai visibility tracking' and resolve any empty links."
This documentation is built and hosted on Mintlify, a developer documentation platform.