Cello

so.celloPublished by cello.soOfficial publisherv1.0.1Updated Oct 24, 2026

Cello MCP server to launch and manage your Referral and Partner program

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Cello's remote MCP server lets an assistant launch and manage a referral and partner program through the Cello platform.

What you can do
Launch and set up a referral and partner program through Cello. Manage the program once it is running, such as partners and referral activity, using the tools the server exposes. The manifest lists no individual tools, so the exact operations available are not documented here.
When to use it
Use it when you run a referral or partner program on Cello and want an assistant to help set it up or manage it from a connected client.
Requirements
A remote MCP connection to the Cello endpoint over streamable HTTP, plus OAuth sign-in to a Cello account. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to your Cello account, and the server is intended to launch and manage a live referral and partner program, so actions may change program settings or partner data. The specific write operations are not documented in the supplied material.

Installation

In SourceWeft

  1. Open Cello in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/so.cello%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "cello": {
      "type": "http",
      "url": "https://mcp.cello.so/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.