Connect Claude to your data (MCP)
Connect Claude, Claude Code or Cursor to your CrazyLeads project via MCP and ask questions about leads, sales and campaigns in plain language — with SQL, dashboards and experiments created in the conversation.
CrazyLeads ships an MCP (Model Context Protocol) server — the open standard that lets AI assistants use external tools. Connected, Claude sees your project’s tables, runs real SQL, opens a lead’s timeline, creates publishable dashboards and even configures A/B experiments. You ask in plain language; it measures before it answers.
Server address: https://mcp.crazyleads.com.br/mcp — OAuth authentication with your CrazyLeads account. Nobody touches any data without logging in, and access respects the projects you are a member of.
Connect in Claude (claude.ai)
- 01On claude.ai, open Settings → Connectors.
- 02Click "Add custom connector" and paste https://mcp.crazyleads.com.br/mcp.
- 03Authorize with your CrazyLeads account on the OAuth screen.
- 04In a new conversation, enable the connector and ask: "what projects do I have?".
Connect in Claude Code
claude mcp add --transport http crazyleads https://mcp.crazyleads.com.br/mcpOn the first call, Claude Code opens the browser for OAuth. Cursor and other HTTP MCP clients follow the same path: server address + OAuth. Per-client walkthroughs live in the integrations technical reference.
What you can do once connected
| You ask | What happens |
|---|---|
| "How many approved sales this month, by product?" | Claude discovers the tables, writes the SQL, runs it and answers with the real number |
| "Show me the journey of lead jane@company.com" | Finds the lead and reads the timeline: ads, pages, forms, purchases |
| "Create a funnel dashboard for campaign X" | Creates a living, hosted artifact with a shareable link |
| "Set up a Purchase delivery to Meta" | Builds the conversion, filter and CAPI mapping — validated against real events before creating |
| "Run an A/B test changing the sales page headline" | Creates the experiment; the pixel serves the variants and measures the winner, including server-side purchases |
Good practices
- Start by asking for the map: "what tables and sources does this project have?" — Claude explores before asserting.
- Ask for numbers with the criterion: "approved sales" means status APPROVED and COMPLETE — the MCP server already teaches the model this.
- Working with more than one project? Say which one is active ("use project X") — tools always operate on your token’s active project.
- Reconnected the connector? Check the active project again: reconnection resets it to the default.
The same server works with ChatGPT (through MCP-compatible connectors) and any agent that speaks the protocol — the full tool list and examples live in the MCP reference.