Overview
The ClientSuccess MCP server gives Claude read-only access to your ClientSuccess data — customer health (Pulse sentiment + SuccessScore), contracts + renewals, NPS feedback, CSM tasks + interactions, and portfolio/CSM performance.
It cannot create, update, or delete anything. It's for querying + reporting only.
Before you start
You'll need:
MCP enabled for your tenant. A ClientSuccess employee turns this on — reach out to your CSM if you're not sure whether it's active.
A Claude account on a plan that supports custom connectors (Free, Pro, Max, Team, or Enterprise).
The ClientSuccess MCP server URL:
https://mcp.clientsuccess.com/api/mcpYour ClientSuccess login credentials (username + password), used to authorize the connector.
On Team + Enterprise plans: only a workspace owner can complete steps 1–3 below. Once the connector is added, it appears for everyone in the workspace, and each person completes steps 4–5 themselves.
Setup steps
In Claude, go to Settings → Customize → Connectors.
Click the + button and choose Add custom connector.
Paste in the ClientSuccess MCP server URL, name it ClientSuccess MCP, and save.
Find ClientSuccess MCP in your Connectors list and click Connect. You'll be redirected to a login page — enter your ClientSuccess username + password to authorize it.
Enable it in your chat: in any conversation, click the + button (bottom left) → Connectors, and toggle ClientSuccess MCP on.
Test the connection
Once you're connected, authorized, and toggled on, ask a natural-language question — for example:
"Which customers have a declining SuccessScore this quarter?"
"Show renewals coming up in the next 30 days."
"Give me the health summary for [customer name]."
If you get a data-backed answer instead of an error, the connection is working.
If Claude answers without hitting ClientSuccess, type "Use ClientSuccess mcp" in the chat to explicitly point it at the connector.
Good to know
It's read-only. There's no risk of the connector modifying your ClientSuccess data.
Connectors are enabled per conversation, not globally. You'll need to toggle it on in each new chat where you want it.
Private network? If your environment restricts outbound connections, Anthropic's IPs may need to be allowlisted. Check with your IT team if the connection fails.