Skip to main content
Your AI coding tool can do most of a Cello integration for you. Connect the Cello MCP server first: it gives your tool live access to your integration’s health and your incoming events, plus the ability to search Cello’s documentation - including the pre-launch testbook - so it knows both what to build and whether what it built is working.

​
Connect the Cello MCP server

Open My account → MCP Server in the Cello Portal, turn the server on, and use the one-click connect for your tool - or the generic option if it doesn’t have its own card yet. There is no token to generate or paste.

MCP introduction

Connect your client

Once connected, your tool can search the docs, check your integration status, and inspect individual events without you pasting anything into the chat. See the developer tools reference for what it can do.

​
See it in action: Cursor + Cello

Watch a walkthrough of adding user referrals to your app with Cursor - from referral widget and attribution to signup tracking and Stripe conversion.
For the full prompt, steps, and acceptance criteria, see the Cursor integration guide.

​
Pick your tool guide

Each guide covers the same end-to-end integration for a specific tool: referral widget, public attribution, signup tracking and Stripe conversion tracking, with acceptance criteria and the known gotchas (JWT claims, script URLs, event payload shape, Stripe metadata).

Claude Code

Cursor

Lovable

Replit

Bolt

Codex

​
Verify what your tool built

Ask your coding tool for your integration status as you go, and work through the pre-launch testbook before you launch. The testbook covers the manual, front-end checks that neither Cello nor your AI tool can see for you.

Pre-launch Testbook

​
If your tool doesn’t support MCP

Some tools can’t connect to an MCP server. In that case, give your AI the documentation as plain context instead:
Copy/paste starter message:
For tools that can’t fetch URLs either, open llms-full.txt, select all, and paste it in as context before your questions.
This is a documentation snapshot, not a live connection. Your AI gets the guides, but no integration status, no event inspection, and no testbook, so you will need to verify your integration yourself in the portal. The file is also large (~73,000 tokens), so it needs a tool with a big context window.

​
Troubleshooting

​
Need Help?

AI sometimes makes mistakes. If you get stuck, reach out to your Customer Success Manager or our support team at support@cello.so.