oto.cx
cloro

cloro

cloro.

Ask an AI search engine and capture its answer + sources/citations

ajouter à otoauth : —prefix : cloro_*

setup & usage

⚠ cloro api key

create an API key in Cloro, then paste it into oto.

  • members consume a platform quota if no personal/org key is set
    • ▸ ai-search monitoring + google serp as json

    queries the AI engines (ChatGPT, Gemini, Perplexity, Copilot, Grok, Google AI Mode) and captures their answers + sources — "AI SEO" brand monitoring — plus Google SERP/News as clean JSON. (AI engine calls take ~30-45 s.)

  • "what does ChatGPT say about brand X?" (answer + citations)
  • "compare what Gemini and Perplexity say about this product"
  • "Google SERP for best CRM with the AI Overview"
  • "Google News on this company"
    • · project perimeter (#605, 2026-08-29)

    under a project with excluded_url_prefixes, cloro_google (serp, news) and cloro_ask (sources/citations) drop the matching results and say so (excluded_by_perimeter). an AI engine's answer is prose: not filtered. details: docs/projects.md.

    ⚙ multiple comptes

    this connector accepts multiple comptes: each stored credential becomes a named account (one name per compte), at your level, your team's or your org's.

  • the first one doesn't need a name; from the second on, each one carries its own (the first then takes the name "principal", renamable)
  • without specification, the agent takes the only stored compte, otherwise the one marked as default; otherwise the call is refused, naming the available comptes — never a random choice
  • target a compte for a call: _account="<name>" on the tool; list them: oto_identity(op='list', connector='cloro') (scope='org' or scope='group' for the org's or team's)
  • set the default: oto_identity(op='set', connector='cloro', identity_id='<name>'); rename: op='rename' with new_name
  • ⚠️ no tool walks through the comptes on its own: a total across several comptes is obtained by calling each one (_account) and adding up

    • outils

    chargement…

    utilisation

    claude code — installe le plugin oto — claude plugin marketplace add otomata-tech/oto-plugin — mcp + skill configurés.
    claude.ai — branche mcp.oto.cx/mcp en connecteur custom (guide)
    cli — pipx install oto-cli puis oto cloro …
    ← tous les connecteurscatalogue mcp →