> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cello.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrate with AI

> Connect the Cello MCP server to your coding tool, then let it build and verify your integration

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](https://app.cello.so/mcp), 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.

<CardGroup cols={2}>
  <Card title="MCP introduction" icon="plug" horizontal href="/mcp/introduction" />

  <Card title="Connect your client" icon="wrench" horizontal href="/mcp/connect" />
</CardGroup>

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](/mcp/developers/tools) 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.

<Accordion title="Watch the walkthrough">
  <iframe className="w-full aspect-video rounded-xl" src="https://www.loom.com/embed/70f4b664bb6e44a69510b44110a55d5c?autoplay=0" title="Cello + Cursor integration walkthrough" frameBorder="0" allow="clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowFullScreen />
</Accordion>

For the full prompt, steps, and acceptance criteria, see the [Cursor integration guide](/coding-apps/cursor-integration).

## 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).

<CardGroup cols={3}>
  <Card title="Claude Code" icon={<img src="https://mintcdn.com/cello/4C7XEZmkMsMYyA_d/coding-apps/logo_claude.svg?fit=max&auto=format&n=4C7XEZmkMsMYyA_d&q=85&s=e931d1add784376c9829b874aa3df1d2" alt="Claude logo" width={32} height={32} />} href="/coding-apps/claude-integration" />

  <Card title="Cursor" icon={<img src="https://mintcdn.com/cello/Bv25payKFf5yzL30/coding-apps/logo_cursor.svg?fit=max&auto=format&n=Bv25payKFf5yzL30&q=85&s=697c224a4f77bad448e3a1e8df401d08" alt="Cursor logo" width={32} height={32} />} href="/coding-apps/cursor-integration" />

  <Card title="Lovable" icon={<img src="https://mintcdn.com/cello/Bv25payKFf5yzL30/coding-apps/logo_lovable.svg?fit=max&auto=format&n=Bv25payKFf5yzL30&q=85&s=89d454e2520acf38fe0be845691950ca" alt="Lovable logo" width={32} height={32} />} href="/coding-apps/lovable-integration" />

  <Card title="Replit" icon={<img src="https://mintcdn.com/cello/BQTZMO-jgvpA9pM3/coding-apps/replit-color.svg?fit=max&auto=format&n=BQTZMO-jgvpA9pM3&q=85&s=3365abbe4baa2abcfe1db7ebc7d54f04" alt="Replit logo" width={32} height={32} />} href="/coding-apps/replit-integration" />

  <Card title="Bolt" icon="bolt" href="/coding-apps/bolt-integration" />

  <Card title="Codex" icon="terminal" href="/coding-apps/codex-integration" />
</CardGroup>

## 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.

<CardGroup cols={2}>
  <Card title="Pre-launch Testbook" icon="list-check" horizontal href="/guides/integration/pre-launch-testbook" />
</CardGroup>

## 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:

```
https://docs.cello.so/llms-full.txt
```

Copy/paste starter message:

```
Use the Cello documentation from this URL as the source of truth: https://docs.cello.so/llms-full.txt
Follow the docs exactly and avoid guessing common patterns.
If something is ambiguous, ask clarifying questions before coding.
```

For tools that can't fetch URLs either, open [llms-full.txt](https://docs.cello.so/llms-full.txt), select all, and paste it in as context before your questions.

<Warning>
  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.
</Warning>

## Troubleshooting

| Issue | Solution |
| - | - |
| MCP not being used | Verify MCP is enabled in the tool, confirm the server is added, and restart the tool if needed |
| MCP authentication errors | Disconnect and reconnect the server to refresh authorization, and check MCP is enabled for your account under **My account → MCP Server** |
| AI doesn't fetch URL | Paste the documentation in as context instead |
| Token limit exceeded | Connect MCP instead, or focus on specific sections of the docs |

## 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](mailto:support@cello.so).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.