Skip to content
Back to search

cello-mcp

The official Model Context Protocol (MCP) server for Cello, the referral and affiliate platform for SaaS companies.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/getcello--cello-mcp/badge.svg)](/listings/getcello--cello-mcp)

HTML

<a href="/listings/getcello--cello-mcp"><img src="/api/listings/getcello--cello-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 133 lines
  1. # Cello MCP Server
  2. The official [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) server for [Cello](https://cello.so), the referral and affiliate platform for SaaS companies.
  3. Connect your AI coding agent or assistant (GitHub Copilot, Claude, Cursor, ChatGPT and any other MCP client) to your Cello account to set up and verify a referral program integration, and to ask about program performance in natural language, grounded in live Cello data.
  4. This is a hosted remote server. This repository holds its documentation and registry metadata (`server.json`); there is nothing to install or run locally.
  5. - **Server URL**: `https://mcp.cello.so/mcp`
  6. - **Transport**: Streamable HTTP
  7. - **Authentication**: OAuth (sign in to Cello in the browser window your client opens; no token to generate or paste)
  8. - **Registry name**: `so.cello/mcp`
  9. - **Docs**: https://docs.cello.so/mcp/introduction
  10. ## What it does
  11. **For developers**
  12. - Search the Cello docs, code examples and API references while you build
  13. - Check the health of the four integration components: referral widget, attribution widget, signup tracking and purchase tracking
  14. - Inspect recent webhook and API events with per-field validation (ucc, productUserId, email, customerId)
  15. **For growth and partner managers**
  16. - Program metrics, trends and industry benchmarks
  17. - Find and rank referrers by revenue, signups, purchases or activity
  18. - Prioritized best-practice recommendations for activation, sharing and conversion
  19. ## Tools
  20. | Tool | Purpose |
  21. |---|---|
  22. | `cello_get_program_metrics` | Program metrics, trends and benchmarks in one call |
  23. | `cello_get_referrers` | Find and sort referrers by engagement or performance |
  24. | `cello_get_top_referrers` | Top referrers by net new ARR |
  25. | `cello_get_integration_status` | Health of the four integration components |
  26. | `cello_get_events` | Latest events feed with per-field validation |
  27. | `cello_get_recommendations` | Prioritized best-practice recommendations |
  28. | `search_cello` | Search the Cello knowledge base |
  29. | `query_docs_filesystem_cello` | Read full doc pages and OpenAPI specs |
  30. All tools are read-only. Which tools you see depends on your Cello role. Full reference: https://docs.cello.so/mcp/tools
  31. ## Prerequisites
  32. 1. A Cello account.
  33. 2. MCP enabled for your account: an admin turns it on in the [Cello Portal](https://app.cello.so/mcp) under **My account -> MCP Server**.
  34. ## Configuration
  35. ### GitHub Copilot in VS Code
  36. Install Cello from the MCP server gallery in VS Code, or add it to `.vscode/mcp.json` in your workspace (or run **MCP: Add Server** from the Command Palette):
  37. ```json
  38. {
  39. "servers": {
  40. "Cello": {
  41. "type": "http",
  42. "url": "https://mcp.cello.so/mcp"
  43. }
  44. }
  45. }
  46. ```
  47. Start the server. VS Code opens a browser window to sign in to Cello and authorize access. Then open Copilot Chat in **Agent** mode and the Cello tools are available.
  48. ### Copilot coding agent
  49. In your repository go to **Settings -> Copilot -> Coding agent -> MCP configuration** and add:
  50. ```json
  51. {
  52. "mcpServers": {
  53. "cello": {
  54. "type": "http",
  55. "url": "https://mcp.cello.so/mcp",
  56. "tools": ["*"]
  57. }
  58. }
  59. }
  60. ```
  61. ### Claude Code
  62. ```bash
  63. claude mcp add --transport http Cello https://mcp.cello.so/mcp
  64. ```
  65. Then run `/mcp`, select **Cello** and choose **Authenticate**.
  66. ### Cursor
  67. Click **Cursor** on the MCP Server page in the Cello Portal, or add this to `~/.cursor/mcp.json`:
  68. ```json
  69. {
  70. "mcpServers": {
  71. "Cello": {
  72. "url": "https://mcp.cello.so/mcp"
  73. }
  74. }
  75. }
  76. ```
  77. ### Other MCP clients
  78. Add a remote (Streamable HTTP) server with the URL `https://mcp.cello.so/mcp` and OAuth authentication. Setup guides for Claude, ChatGPT, Windsurf, Lovable, Replit and more: https://docs.cello.so/mcp/connect
  79. ## Usage
  80. Example prompts:
  81. - "Use Cello to check my integration status."
  82. - "Add Cello referral tracking to this app."
  83. - "Why are my signups not being attributed to referrers?"
  84. - "Show me the latest events Cello received and flag any missing fields."
  85. - "How is our referral program doing compared to industry benchmarks?"
  86. - "Who are our top 10 referrers by net new ARR?"
  87. - "What should we improve to get more referrers sharing?"
  88. ## Troubleshooting
  89. | Issue | Solution |
  90. |---|---|
  91. | Tools return authentication errors | Disconnect and reconnect the server. Check that MCP is enabled under **My account -> MCP Server** in the portal. |
  92. | You don't see the tools you expect | Available tools depend on your Cello role. Contact your Customer Success Manager. |
  93. | `cello_get_integration_status` shows `notConnected` | Follow the integration guide for that component; ask `search_cello` for the setup docs. |
  94. ## Support
  95. - Documentation: https://docs.cello.so
  96. - Email: [support@cello.so](mailto:support@cello.so)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.