scrape_chatgpt
prompt, country (ISO 3166-1 a2), optional state, include
LABSCO SUMMARY
Per-provider credit rates mean the choice of assistant is a cost decision, not just a coverage one.
If you are tracking how AI assistants describe your brand, the honest approach is to check several — and here each one prices differently, so a daily sweep across five assistants and twenty countries needs arithmetic before it needs a schedule. The documented Grok outage is worth noting too: the tool is registered and will fail, which is better disclosed than discovered. list_countries exists precisely so a model does not invent country codes.
What it is
Cloro's endpoint, a thin wrapper over their API. Ten tools: one per AI assistant, two for Google, and two that tell you the valid country and state values.
What you get
- scrape_chatgpt, scrape_gemini, scrape_copilot, scrape_perplexity — a prompt and an ISO country code, optionally a state
- scrape_grok — registered, but the documentation notes the provider is temporarily unavailable and calls fail
- scrape_google_ai_mode and scrape_google — search results with location, device and page controls, or a full search URL
- scrape_google_news — news for a query and country
- list_countries and list_states — the valid values, so filters are not guesswork
Requirements
A cloro account with credits. In Claude and Claude Code you sign in to cloro in the browser and choose the organization whose credits pay; other clients use an API key, as a bearer token or in the URL path. Credits: free gives 500 a month, Lite is $30 for 37,500, Hobby $100 for 250,000, and the per-thousand rate falls from $0.80 to $0.31 with volume. Providers cost different amounts — a full ChatGPT scrape is 7 credits, the web variant 5.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Seeing how assistants answer about you
Run the same prompt across ChatGPT, Gemini, Copilot and Perplexity and compare.
02
Checking answers vary by country
Repeat the prompt with different ISO country codes, using the valid list rather than guessing.
03
Comparing against classic search
Pull Google's AI mode and its normal results for the same query.
10 tools
Listed in project docs. Your client may show a different list.
scrape_gemini
prompt, country, optional state, include
scrape_copilot
prompt, country, optional state, include
scrape_perplexity
prompt, country, optional state, include
scrape_grok
prompt, country, optional state; REGISTERED BUT PROVIDER TEMPORARILY UNAVAILABLE (calls fail)
scrape_google_ai_mode
prompt, country, sub-country via location/uule, device
scrape_google
query+country (optional location/uule/device/pages) OR full google.com/search url; include.aioverview, include.paaAioverview
scrape_google_news
query, country, optional device, pages
list_countries
optional model filter
list_states
country
BEFORE YOU INSTALL
What to know first
Tools you get
10 tools named in the project's documentation.
Requires
- an MCP client that can reach a remote endpoint
- A cloro account with credits; an API key from https://dashboard.cloro.dev for clients other than Claude and Claude Code, in the URL path or as an Authorization: Bearer header
Where it runs
All 3 documented setups connect to a hosted endpoint.
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://mcp.cloro.dev/mcpRequirements
- OAuth sign-in in Claude and Claude Code; an API key, as a Bearer header or in the URL path, everywhere else
MCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add --transport http cloro https://mcp.cloro.dev/mcpAfter adding the server, run /mcp in a Claude Code session and sign in to cloro in the browser. No API key is needed.
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"cloro": {
"type": "http",
"url": "https://mcp.cloro.dev/<YOUR_CLORO_API_KEY>/mcp"
}
}
}<YOUR_CLORO_API_KEY> is your cloro API key from https://dashboard.cloro.dev. The key sits in the URL path so this works in clients that can't set headers; if yours can, use https://mcp.cloro.dev/mcp with an Authorization: Bearer header instead.
Any MCP client — Header
ANY MCP CLIENT — HEADER · JSON
{
"mcpServers": {
"cloro": {
"type": "http",
"url": "https://mcp.cloro.dev/mcp",
"headers": {
"Authorization": "Bearer <YOUR_CLORO_API_KEY>"
}
}
}
}For clients that can send headers: with <YOUR_CLORO_API_KEY> sent this way, the key stays out of the URL.
