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

# Introduction

> Let your AI code assistant learn from Cello documentation and automate your integration steps

Build with Cello faster using AI assistants that understand our entire documentation. This guide shows you how to give AI tools like **Cursor**, **Claude Code**, **Copilot**, etc complete context about Cello's APIs, SDKs, and integration patterns.

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

## Recommended: Use a tool-specific guide

Start with the detailed guide for your tool:

<CardGroup cols={4}>
  <Card title="Claude Code" icon={<img src="/coding-apps/logo_claude.svg" alt="Claude logo" width={32} height={32} />} href="/coding-apps/claude-integration" />

  <Card title="Cursor" icon={<img src="/coding-apps/logo_cursor.svg" alt="Cursor logo" width={32} height={32} />} href="/coding-apps/cursor-integration" />

  <Card title="Lovable" icon={<img src="/coding-apps/logo_lovable.svg" alt="Lovable logo" width={32} height={32} />} href="/coding-apps/lovable-integration" />

  <Card title="Replit" icon={<img src="/coding-apps/replit-color.svg" alt="Replit logo" width={32} height={32} />} href="/coding-apps/replit-integration" />
</CardGroup>

These guides are best when you want an end-to-end integration:

* Implement **referral widget** + **public attribution** + **signup tracking** + **Stripe conversion tracking**
* Follow **acceptance criteria** and known gotchas (JWT claims, script URLs, event payload shape, Stripe metadata)

After implementation, validate with the [Integration QA Checklist](/resources/integration-qa-checklist).

## Choose how to give your AI Cello context

### Option A (recommended): Cello MCP Server

Connect the **[Cello MCP Server](/mcp/introduction)** to your coding tool for the best experience. It gives your tool access to Cello's documentation, integration health checks, best-practice recommendations, and event inspection - no need to paste anything into every chat.

See [Connect your client](/mcp/connect) for setup instructions for Cursor, Lovable, VS Code, Claude Code, and other MCP clients.

### Option B: URL context

Provide this URL directly to your AI tool:

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

<Note>
  This file contains \~73,000 tokens of comprehensive Cello documentation optimized for LLM consumption.
</Note>

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

### Option C: Direct content injection

For AI tools that don't support URL fetching, you can copy the entire documentation:

1. **Download the documentation**: Open [llms-full.txt](https://docs.cello.so/llms-full.txt)
2. **Copy all content**: Select all (Ctrl/Cmd + A) and copy
3. **Paste into your AI tool**: Add as context before your questions

<Warning>
  Some AI tools have token limits. The full documentation is \~73,000 tokens, so you may need to use tools like Claude (200k context) or GPT-4 Turbo (128k context).
</Warning>

## Troubleshooting

| Issue                | Solution                                                                                       |
| -------------------- | ---------------------------------------------------------------------------------------------- |
| AI doesn't fetch URL | Use Method 2 (copy-paste) instead                                                              |
| Token limit exceeded | Focus on specific sections or use an AI with larger context window                             |
| MCP not being used   | Verify MCP is enabled in the tool, confirm the server is added, and restart the tool if needed |
| Outdated information | Always verify critical details at [docs.cello.so](https://docs.cello.so)                       |

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