cloro MCP server
Commit Nov 7, 2026Scrape AI answer engines and Google Search or News results with country and state-level geo-targeting.
Also known as cloro-dev/mcp-server, mcp-server
- Stars
- 0
- Tools
- 9
- Downloads, 30 days
- —
- Latest version
- 0.5.0
- Last commit
- Nov 7, 2026
- License
- MIT
What is cloro MCP?
cloro is an MCP server. Scrape AI answer engines and Google Search or News results with country and state-level geo-targeting. It exposes 9 tools, such as scrape_chatgpt, scrape_gemini, scrape_google_ai_mode.
Summary generated from the project's README
About cloro MCP server
Scraping AI answer engines and Google Search or News results with country and state-level geo-targeting is what cloro enables for developers using MCP clients. This server allows agents to access data from ChatGPT, Gemini, Google AI Mode, Google AI Overview, and Bing AI Mode, alongside standard Google web search and news results. It is designed for use with Claude, Cursor, and Codex, providing a way to compare different AI responses or research specific geographic regions.
Users can connect via a hosted endpoint at mcp.cloro.dev using OAuth for Claude or an API key for other clients. The server can also be run locally via stdio. It provides specialized tools like scrape_chatgpt, scrape_google, and scrape_google_news to fetch real-time information. For precise research, the server supports targeting specific countries and US states, and includes a utility to resolve Google redirect links to their final destinations.
What you can do with it
- 1Compare AI engine responsesAsk your agent to compare the top results from Google with the specific answers provided by ChatGPT.
- 2Perform geo-targeted researchRetrieve search or AI results that are specifically filtered by a particular country or US state.
- 3Resolve search redirectsFind the actual destination URL for a Google search result that uses a redirect link.
Written from the project's README. Every use case is checked against a quote from it.
How to install cloro MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall cloro MCP in Claude Code
$ claude mcp add --transport http mcp-server https://mcp.cloro.dev/mcpInstall cloro MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server": {
"url": "https://mcp.cloro.dev/mcp"
}
}
}Install cloro MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp-server": {
"type": "http",
"url": "https://mcp.cloro.dev/mcp"
}
}
}Install cloro MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp-server","type":"http","url":"https://mcp.cloro.dev/mcp"}'Install cloro MCP in Codex
$ codex mcp add mcp-server --url https://mcp.cloro.dev/mcpInstall cloro MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp-server] url = "https://mcp.cloro.dev/mcp"
Install cloro MCP in Gemini CLI
$ gemini mcp add -s user --transport http mcp-server https://mcp.cloro.dev/mcpInstall cloro MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp-server": {
"url": "https://mcp.cloro.dev/mcp",
"type": "http"
}
}
}cloro MCP tools 9
Detected from the READMEscrape_chatgptscrape_geminiscrape_google_ai_modescrape_bing_aimodescrape_googlescrape_google_newsresolve_google_redirectlist_countrieslist_states
| scrape_chatgpt | — | |
| scrape_gemini | — | |
| scrape_google_ai_mode | — | |
| scrape_bing_aimode | — | |
| scrape_google | — | |
| scrape_google_news | — | |
| resolve_google_redirect | — | |
| list_countries | — | |
| list_states | — |
Configuration
MCP_TRANSPORT
| Name | Description | |
|---|---|---|
| MCP_TRANSPORT | — |
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablecloro-dev/mcp-server is public and reachablegithub.com/cloro-dev/mcp-server ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-07github.com/cloro-dev/mcp-server ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model9 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 740 msPass
README
View on GitHubcloro MCP Server
A Model Context Protocol (MCP) server for cloro, the LLM scraping API that includes a Google SERP API. It gives Claude, Codex, Cursor and any MCP client answers from ChatGPT, Gemini, Google AI Mode, Google AI Overview and Bing AI Mode, plus Google web search and Google News results. Ask your agent "compare Google's top results for best LLM scraping API with ChatGPT's answer" and it calls cloro and reasons over the parsed results and cited sources.
Runs hosted at mcp.cloro.dev, or locally over stdio.
How do you connect an agent to the cloro MCP server?
In Claude, you sign in with OAuth and do not need a key:
- Go to Customize → Connectors and select Add custom connector.
- Enter
https://mcp.cloro.dev/mcp. Under Authentication, choose Sign in when needed. - Ask Claude to use a cloro tool. Sign in to cloro and select the organization whose credits pay for the calls.
Other clients use a cloro API key from the dashboard. The hosted server speaks Streamable HTTP. Put the key in the URL path so it works in clients that cannot set custom headers:
{
"mcpServers": {
"cloro": {
"type": "http",
"url": "https://mcp.cloro.dev/YOUR_CLORO_API_KEY/mcp"
}
}
}
If your client can set headers, use https://mcp.cloro.dev/mcp with Authorization: Bearer YOUR_CLORO_API_KEY. In Claude Code:
claude mcp add --transport http cloro https://mcp.cloro.dev/YOUR_CLORO_API_KEY/mcp
In Cursor
This repo is also a Cursor plugin. Install it from the Cursor marketplace, or point Cursor at the repo, and Cursor prompts for one variable:
| Variable | Value |
|---|---|
CLORO_API_KEY |
Your key from the dashboard |
Cursor stores the key on its side and sends it as Authorization: Bearer, so the key stays out of the URL and out of the repo. The manifest is .cursor-plugin/plugin.json and the server definition is mcp.json.
Running it yourself
npm install
npm run build
MCP_TRANSPORT=stdio CLORO_API_KEY=your_key node dist/index.js
MCP_TRANSPORT is http (default) or stdio. In stdio mode the client spawns the process and the key comes from CLORO_API_KEY; in http mode keys arrive per request and no key is configured on the server. PORT defaults to 8095 and CLORO_API_URL to https://api.cloro.dev.
OAuth is off unless you set CLERK_ISSUER. The hosted server sets it to https://clerk.cloro.dev. api.cloro.dev accepts only tokens from that issuer, so a self-hosted server that forwards to it must use the same value. MCP_PUBLIC_URL (default https://mcp.cloro.dev) sets the resource URL in the protected resource metadata.
What tools does it expose?
| 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 |
The assistant tools take a prompt and a country (ISO 3166-1 alpha-2), plus an optional state for US state-level targeting. The Google tools take gl for the result geography and an optional hl for the interface language; country still works as a deprecated alias for gl. scrape_google_ai_mode targets sub-country with location or uule rather than state. scrape_google runs either from a query plus gl, or from a complete google.com/search URL that carries the query and pagination itself, and accepts include.aioverview for Google's AI Overview. Every tool takes an optional include object for heavier payload fields; leave it unset for the leanest response.
A Google result link can come back empty, or as a google.com/goto URL, with a redirectLink beside it. Pass the redirectLink to resolve_google_redirect to get the destination.
There is no Grok tool. Grok is discontinued: grok.com shows a sign-up wall to logged-out visitors, and the cloro API rejects Grok calls with a 400 (MODEL_UNAVAILABLE).
There are no Copilot or Perplexity tools. Both are discontinued: they block access for logged-out sessions, and the cloro API rejects their calls with a 400 (MODEL_UNAVAILABLE). These calls cost no credits.
How it works
The server holds no business logic and no secrets. Each request forwards the caller's own credential, an API key or an OAuth access token, to api.cloro.dev as a Bearer token, so authentication, credit billing, rate limiting and concurrency are all enforced by the API rather than here. In http mode every POST builds a fresh server and transport bound to that caller's credential, which is why one deployment serves everyone with no session state.
initialize and tools/list answer without a credential, so a client can list the tools before sign-in. The first tools/call without one returns 401 with a WWW-Authenticate header that points at /.well-known/oauth-protected-resource/mcp. An OAuth client reads the authorization server from there and runs the flow. The server checks a token's signature against the issuer's public JWKS (code in src/oauth-tokens/), so it needs no Clerk secret.
Tool input schemas are the same zod schemas the API validates with, vendored into src/schemas/ from cloro's backend. They are copied rather than imported because that package is not published. The API reference is authoritative if the two ever disagree.
FAQ
Do I need to self-host this?
No. mcp.cloro.dev is hosted and is the path most people should take. This repo exists so you can read what runs, and self-host if your setup calls for it.
Does it cost credits?
Yes. The scrape tools call the sync API, so each call costs the API rate plus a 2-credit sync surcharge. For example, a ChatGPT call costs 7 credits (5 + 2). Each tool description states its cost, and each result returns the credits charged and remaining. resolve_google_redirect costs 1 credit, with no surcharge. list_countries and list_states read fixed reference lists and charge nothing. See pricing.
Why is my API key in the URL?
Because several MCP clients cannot set custom headers. If yours can, use the Authorization header form instead and keep the key out of the path. If your client supports OAuth, use that and there is no key at all. The URL path accepts API keys only, never OAuth tokens.
What is the request timeout?
320 seconds. Sync scrapes can take up to five minutes server-side, so the client budget leaves headroom. For long-running batches use the async task API rather than MCP.
Are there agent skills for cloro?
Yes. cloro-dev/skills has one skill per surface (ChatGPT, Gemini, Google AI Mode, Google AI Overview, Google Search, Google News) and skills for SERP research, LLM answer monitoring and AI visibility tracking. Install them with npx skills add cloro-dev/skills. The skills tell the agent which tool or endpoint to call, what it costs, and how to read the result. They work with this server or with the REST API.
Learn more
- Integration guide: cloro.dev/docs/integrations/mcp
- API reference: cloro.dev/docs
- Agent skills: github.com/cloro-dev/skills
License
MIT. See LICENSE.
cloro MCP questions
How do I add cloro MCP to Claude Code?
Run claude mcp add --transport http mcp-server https://mcp.cloro.dev/mcp in your terminal. Add --scope user to make it available in every project.
How do I add cloro MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does cloro MCP provide?
It exposes 9 tools, including scrape_chatgpt, scrape_gemini, scrape_google_ai_mode, scrape_bing_aimode, scrape_google.
Do I need to self-host this?
No, the hosted version at mcp.cloro.dev is the recommended path for most users.
Does using the scrape tools cost credits?
Yes, each scrape tool call costs the API rate plus a 2-credit sync surcharge.
Why is my API key included in the URL?
Some MCP clients are unable to set custom headers, so the URL path allows for API key authentication in those cases.
What is the request timeout for the server?
The request timeout is 320 seconds to allow for sync scrapes that can take up to five minutes.