cloro MCP ServerVerifiedFeatured

Query AI answer engines and Google Search as agent tools — see how ChatGPT, Gemini, Perplexity, Copilot, Grok, and Google AI Mode actually answer a prompt, and which brands and sources they cite.

Tools

• scrape_chatgpt — Submit a prompt to ChatGPT and return the answer with cited sources
• scrape_gemini — Submit a prompt to Google Gemini and return the answer with cited sources
• scrape_perplexity — Submit a prompt to Perplexity and return the answer with cited sources
• scrape_copilot — Submit a prompt to Microsoft Copilot and return the answer with cited sources
• scrape_grok — Submit a prompt to Grok (xAI) and return the answer with cited sources
• scrape_google_ai_mode — Submit a prompt to Google AI Mode and return the AI answer with cited sources
• scrape_google — Run a Google search and return organic results, with optional AI Overview and People Also Ask extraction
• scrape_google_news — Run a Google News search and return news results
• list_countries — List the country codes supported for geo-targeting, per engine
• list_states — List the state codes available for state-level targeting in a country

All ten tools are read-only and annotated as such (readOnlyHint), so hosts can surface them as safe, non-mutating operations.

Config

{
  "mcpServers": {
    "cloro": {
      "type": "http",
      "url": "https://mcp.cloro.dev/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_CLORO_API_KEY"
      }
    }
  }
}

Overview

What is cloro MCP Server?

A Model Context Protocol server that gives any MCP-capable agent live access to AI answer engines and Google Search. It runs your prompt through ChatGPT, Google Gemini, Perplexity, Microsoft Copilot, Grok, and Google AI Mode, and returns each answer together with the sources it cited.

How to use cloro MCP Server?

Use the hosted endpoint at https://mcp.cloro.dev/mcp with a cloro API key. The key can be sent as an Authorization: Bearer header, or embedded in the URL path (https://mcp.cloro.dev/YOUR_CLORO_API_KEY/mcp) for clients that cannot set headers. Prefer the header where your client supports it.

Create an API key at cloro.dev. No installation or self-hosting is required — the server is hosted, and every request is billed to your own cloro account.

Key features of cloro MCP Server

• Six AI answer engines: ChatGPT, Google Gemini, Perplexity, Microsoft Copilot, Grok, Google AI Mode
• Cited sources returned alongside every AI answer, so you can see what each engine referenced
• Google Search and Google News, with optional AI Overview and People Also Ask extraction
• Country-level geo-targeting on every request, with state-level targeting where supported
• Device emulation (desktop/mobile) and multi-page results on the Google tools
• Reference tools that report which countries and states each engine supports, so agents can self-correct before calling
• All tools read-only and annotated, with per-call credit usage returned in the response

Use cases of cloro MCP Server

• Brand monitoring — track how AI engines describe your brand, and whether they cite you
• Competitive research — compare how different engines answer the same commercial query
• GEO / AI-search optimisation — check whether your content is being retrieved and cited by AI answers
• Market comparison — run the same prompt from multiple countries and see how the answer changes
• SERP analysis — pull organic Google results and AI Overviews as structured data for an agent to reason over

FAQ

How does authentication work? Two methods: header-based (Authorization: Bearer YOUR_CLORO_API_KEY) or path-based (include the key in the URL: /YOUR_CLORO_API_KEY/mcp). Each request carries the caller's own key, so authentication, rate limiting, credits, and concurrency are enforced by the cloro API.

What languages or runtimes are required? None. The server is hosted, so you only need an MCP client and an API key.

Where does the data come from? Every result is scraped live from the named engine at request time — there is no cache or stored index. Answers reflect what the engine returned for your prompt, from the country you targeted.

How is usage billed? Calls are billed to your own cloro account against your plan's credits. Each response reports the credits charged and remaining.

What are the known limits or error cases? Common cases are a missing or malformed API key (401), insufficient credits (402), and validation errors on the request body (400). Some engines do not support every country — call list_countries with the model name to check before scraping.

Which transports are supported? Streamable HTTP at https://mcp.cloro.dev/mcp.