Cromanion

**You can start right now, alone.** No API key to fetch, no human to wake, no consent screen in a browser. The first call — `cromanion_open_claim` — takes no credential and creates nothing: no account, no key, no charge. It hands you a challenge to publish on the site you manage, and that proof is what mints your key. Your human only has to appear if they later want a paid plan, and you can never spend their money. ## What it does once it is running Cromanion is a conversion agent that runs itself. The site pastes one tag; an AI that has read the site watches every session live, predicts the visitor's next move, and intervenes at the right moment to push toward conversion. Then it is **your** job, not a dashboard theirs to babysit. You rule on what may be rewritten, define what counts as a conversion, set what the agent may say, seed the crawl, and take the site live — as far as your human allowed, which `cromanion_grants` tells you *before* you try rather than after you fail. ## What you get to report back `cromanion_impact` returns lift measured against a **permanent 10% holdout**. What you tell your human is causal, not a correlation you would have to hedge — and it is written back into the tools they already use (GA4, Plausible) rather than into one more screen. Cromanion states no fact it cannot trace to their own pages or their own words. You will not be the reason it told a visitor something untrue. ## Why there is no API key We cannot take your word for an email address. Anybody can type any address, and if that were enough, an agent could be handed a live key inside a stranger's account. So we ask for the one thing you can prove and a stranger cannot: **that you control the site.** Publish any one of three, whichever your hosting lets you write: | Method | Where | | --- | --- | | `well_known` | `/.well-known/cromanion-challenge.txt`, containing the challenge | | `meta_tag` | `<meta name="cromanion-site-verification" content="…">` in the page `<head>` | | `dns_txt` | a TXT record on the apex reading `cromanion-site-verification=…` | The claim is redeemable for 24 hours, and opening one commits your human to nothing. ## Two things you cannot do **You cannot pay.** `cromanion_upgrade_link` returns a Stripe link and nothing else — your human opens it and enters their own card. Everything else works on the free plan meanwhile. **You cannot switch the site from `learn` to `act` on your own initiative.** A new site watches real sessions and shows visitors nothing; letting an AI speak to visitors in your human's name is their decision. They can delegate it to you explicitly, and then you may. ## The order to call things in 1. `cromanion_open_claim` — keep the secret; it is shown once and authenticates every later call in the `Authorization` header, never in a tool argument. 2. Publish one of the three proofs it lists. Each comes back with the exact URL and the exact string. 3. `cromanion_verify_claim` — creates the account and the site, returns the tracking snippet. Safe to retry: a repeat gives you the same account, never a second one. 4. Install the returned snippet before `</body>` on every page. 5. `cromanion_site_status` — poll until `install.verified` is true. That is not "we gave you a snippet"; it means a beacon reached us from your human's own domain. If it stays false, `cromanion_install_check` tells you *why* — a CSP blocking the script, a consent manager holding it, the tag on some pages and not others, or beacons arriving from a host the site was not claimed under. Each with the fix. Then read `cromanion_grants` for what you may do, `cromanion_config` for what is already in force, and `cromanion_pending` for what is waiting on a decision. Read `cromanion_errors` once and you will never have to guess whether a refusal is worth retrying. Full reference: [cromanion.com/agents](https://cromanion.com/agents)

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness

Higher than 75% of peers

This listing 84 · peer median 81

Latency

Faster than 34% of peers

This listing 468 ms · peer median 326 ms

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

How to connect

https://server.smithery.ai/cromanion/cromanion/mcp

curl -X POST https://server.smithery.ai/cromanion/cromanion/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'