MCP server for your commitment ledger

The Customer Success Manager runs a Model Context Protocol server over Streamable HTTP. An MCP client such as Claude can read your commitments and create candidates for your team to confirm.

Endpoint

The endpoint is a single URL that accepts JSON-RPC 2.0 requests (initialize, tools/list and tools/call) with a bearer token.

https://thecustomersuccessmanager.com/api/mcp

Set it up in four steps

  1. Sign up or log in, and choose a plan so the workspace has access.
  2. Open Agent Setup in the app and generate a token. The token is shown once and only a hash is stored, so copy it right away.
  3. Add the server to your MCP client. For Claude Desktop, add the configuration below to claude_desktop_config.json. It uses the mcp-remote bridge, which needs Node.js.
  4. Ask a question, for example which accepted commitments for an account are still open.
{
  "mcpServers": {
    "customer-success-manager": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://thecustomersuccessmanager.com/api/mcp", "--header", "Authorization:${AUTH_HEADER}"],
      "env": { "AUTH_HEADER": "Bearer <YOUR_TOKEN>" }
    }
  }
}

Clients that support remote MCP servers with custom headers can use the endpoint URL and an Authorization header with the value Bearer followed by your token directly.

Available tools

  • list_customer_accounts Lists the accounts in the workspace, with an optional name filter and cursor pagination.
  • get_customer_commitments Returns the commitments of one account, optionally filtered by status.
  • get_commitment_detail Returns one commitment with its evidence and status history.
  • get_customer_brief Returns a compact overview of one account that separates confirmed from proposed commitments.
  • create_commitment_candidate Creates a potential commitment from a pasted note. It is never accepted automatically. A teammate must confirm it in the app.
  • prepare_commitment_followup Returns a draft reminder text and a link to the commitment. It does not send anything.

Security

Each token belongs to one workspace and can only see that workspace. You can revoke a token at any time in Agent Setup. Candidates created over MCP are marked as coming from MCP in the activity log, and only a person in the web app can accept a commitment or verify delivery. If the workspace subscription ends, the endpoint answers with HTTP 402.

Test it

This request lists the tools if your token is valid.

curl -X POST https://thecustomersuccessmanager.com/api/mcp \
  -H "Authorization: Bearer <YOUR_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Sign upLog in