Claude, with your workspace in reach

Sell runs an MCP server. Point Claude Code or Claude Desktop at it with an API key and Claude can read your clients, products, meetings, notes and sales documents. With a write key, it can create some of them too.

Ten tools, not a data dump

list_clients, get_client, create_client, list_products, list_sales_documents, list_meetings, list_notes, create_note, list_knowledge and create_knowledge_entry. Each one is a named, permissioned call.

Read-only unless you say otherwise

Keys carry a scope. A read-only key is refused on anything but a GET before the endpoint runs, and the tool list itself hides the tools a key cannot use, so the assistant is never offered a capability it would fail with.

We log that a tool ran, never what was in it

The dashboard records which tool was called, whether it succeeded and how long it took. It never records the arguments an agent passed or the data a tool returned.

Setup

  • Open Developers → API keys in the portal and create an MCP key with the scope you want.
  • Claude Code: `claude mcp add --transport http cousinslab <api-base>/mcp/ --header "X-API-Key: …"`
  • Claude Desktop: add the same URL and header to your MCP config file.
  • The Developers dashboard fills in as soon as the assistant introduces itself.

Limits

  • MCP calls cost credits like any other AI work: a flat 10 credits per call, itemised in your account.
  • The tools cover clients, products, meetings, notes, knowledge and sales documents. Invoices, payments and automations are reachable through the REST API but are not MCP tools yet.