Crisper MCP

One command. Then click Allow.

Add Crisper to Claude Code, Codex or Cursor, then ask your agent to set up your client's website. You approve billing and ad accounts in your browser.

For Claude Code, Codex, Cursor and other MCP agents. Sign-in and tool discovery tested with Claude Code, Codex and the Cursor CLI.

Terminal
  1. claude mcp add --transport http crisper https://crisper.io/api/mcp
  2. Added crisper
  3. Claude Code
  4. Set up my website in Crisper.
  5. Opening Crisper sign-in. Click Allow in your browser.
  6. Connected. You're in Northwind Agency, 3 sites.
  7. Added clinic.example · WordPress
  8. Pick a plan on the billing page I opened. I'll wait.

01Run one command to add Crisper to your agent.

Choose your agent.

One command adds Crisper to your agent. The first time your agent needs Crisper, it opens sign-in; you click Allow.

Connect Claude Code

claude mcp add --transport http crisper https://crisper.io/api/mcp
  1. Run this once in your project's terminal.
  2. Start Claude Code and ask it to set up your website in Crisper. It opens Crisper sign-in; click Allow.

Saved for this project only. Claude asks you to sign in the first time it needs Crisper; the tools load right after you click Allow. Claude Code documentation

Prefer to paste a prompt into your agent?

Your agent saves the connection and a skill file (.claude/skills/crisper/SKILL.md). Most agents then need a new session before Crisper sign-in opens.

Read the setup prompt
Please connect yourself to Crisper and set up my website now. These are my instructions, not a document to summarize. Do them in order:

1. If the Crisper tools (get_connection and the others) are available, skip to step 4. If a crisper MCP server is configured but needs sign-in, start that sign-in yourself if your client allows it (Claude Code does), tell me "Click Allow in the browser tab that just opened," then go to step 4.
2. Otherwise, if you can run terminal commands, download https://crisper.io/mcp/install.mjs, read it, and run it in this project, allowing up to 10 minutes because it may wait for my sign-in: node install.mjs --client codex|claude|cursor|antigravity|replit (pick the one you are). It saves the Crisper connection and instructions. Then tell me the next step it prints, word for word; usually that is to start a new session and paste this prompt again. If it reports a different existing Crisper connection, stop and show me; never overwrite it.
3. If you cannot run commands, give me the steps for this client from https://crisper.io/mcp, one at a time.
4. Call get_connection. If I have no organization, ask for my business name and call create_organization. If I have several, ask which to use.
5. Ask for my website's domain and platform, confirm them with me, then call create_site.
6. Open the link from start_billing_checkout so I can choose a plan, then the link from start_integration_connection so I can connect my ad accounts. Check get_site_setup before you say setup is done.

Never ask for passwords, payment details or provider tokens in chat. Start now with step 1.

Your agent does the setup. You keep the approvals.

Your agent can

  • See the organizations and websites you belong to
  • Add a website after you confirm the domain
  • Check setup, billing status and site health
  • Open billing, ad-account and install pages for you

Only you can

  • Choose a plan and approve checkout
  • Copy the Pixel ID, token or conversion IDs from each ad platform
  • Paste them into the integration page

Billing and the integration page open in your browser. Your agent waits, then checks the result.

Never in the chat

Card details, ad-platform tokens and visitor data.

The tools return site status and links, nothing else.

Access follows your organization.

One sign-in

Your agent reaches the organizations you belong to, and asks which one to use.

Team changes

Remove someone from the organization and their agent loses access on its next request.

Right workspace

Links from your agent open the site's organization in your browser.

Same tracking

MCP connects your agent to Crisper. Your website still uses its normal tracking installation.

Open the dashboard

Run the installer yourself.

It is the same script the prompt runs. It saves the connection and a skill file that helps your agent resume setup, then opens Crisper sign-in.

It stores no credentials and never overwrites a different existing connection or skill.

curl --fail --proto =https --tlsv1.2 https://crisper.io/mcp/install.mjs -o crisper-install.mjs
# Read it first. Choose codex, claude, cursor, antigravity or replit.
# It opens Crisper sign-in when setup is saved; add --no-login to skip (Codex signs in as soon as Crisper is added).
node crisper-install.mjs --client claude

Antigravity and Replit sign in from their own MCP settings. ChatGPT uses the prompt without a skill file.

Need a hand connecting?

Most problems are a sign-in that did not finish, or a session that started before the connection existed.

Contact us
My agent cannot see the tools

Most agents load tools when a session starts. After you click Allow, start a new session. If your client cannot install skills, download the skill file and ask the agent to read it.

Sign-in failed

If Codex shows invalid_scope, run codex mcp login crisper --scopes profile,email,offline_access. If the server returns 503, MCP is paused; use the dashboard. If your client reports unsupported client registration, it is not supported yet. Never paste an access token into chat.

Removing access

Remove the connection in your agent (for example claude mcp remove crisper or codex mcp remove crisper). An organization admin can also remove a person from the organization, which stops their agent on its next request. To revoke a sign-in itself, contact us.

The wrong organization is selected

Tell your agent which organization to use. Links from your agent open that organization automatically.

Billing is still pending

Wait for verified subscription status. Do not start a second subscription.

Endpoint: https://crisper.io/api/mcp
Sign-in and tool discovery tested with Claude Code, Codex and the Cursor CLI on October 8, 2026. Other clients follow their own MCP documentation.

Ready to set up your next site?

Run one command, click Allow, and approve each step in Crisper.

Choose your agent