Bring Customer Success
to Windsurf
Learn how to connect ClientSuccess to Windsurf and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the ClientSuccess MCP Server?
Connect your ClientSuccess customer success platform to any AI agent and simplify how you manage your client relationships, track account health, and monitor service contracts through natural conversation.
What you can do
- Client Oversight — List all managed clients and retrieve detailed metadata, including health scores and success status.
- Relationship Management — Manage client contacts, query individual profiles, and create new client records programmatically.
- Contract Monitoring — List active and historic service contracts to ensure your renewals and agreements are on track.
- Segmentation — Query customer segments to understand your client distribution and categorization.
- Data Insights — Fetch complete account metadata and health metrics to identify at-risk customers via AI.
- Operational Efficiency — Track your customer success ecosystem directly from Claude, Cursor, or any MCP client.
How it works
1. Subscribe to this server
2. Enter your ClientSuccess API Key (found in your account settings)
3. Start managing your client relationships from your favorite AI assistant
Who is this for?
- Customer Success Managers (CSMs) — quickly check client health scores and retrieve contact info via simple AI commands.
- Success Operations — monitor contract distributions and verify segment metadata directly from the workspace.
- Product & Leadership Teams — get instant bird's-eye views of client status and account growth via the AI assistant.
Built-in capabilities (6)
Create a new client
Get details for a specific client
List ClientSuccess clients
Optionally filter by client ID. List client contacts
List client contracts
List client segments
Why Windsurf?
Windsurf's Cascade agent chains multiple ClientSuccess tool calls autonomously. query data, analyze results, and generate code in a single agentic session. Paste Vinkius Edge URL, reload, and all 6 tools are immediately available. Real-time tool feedback appears inline, so you see API responses directly in your editor.
- —
Windsurf's Cascade agent autonomously chains multiple tool calls in sequence, solving complex multi-step tasks without manual intervention
- —
Purpose-built for agentic workflows. Cascade understands context across your entire codebase and integrates MCP tools natively
- —
JSON-based configuration means zero code changes: paste a URL, reload, and all 6 tools are immediately available
- —
Real-time tool feedback is displayed inline, so you see API responses directly in your editor without switching contexts
ClientSuccess in Windsurf
ClientSuccess and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect ClientSuccess to Windsurf through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for ClientSuccess in Windsurf
The ClientSuccess MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 6 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Windsurf only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
ClientSuccess for Windsurf
Every tool call from Windsurf to the ClientSuccess MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I check a client's health score via AI?
Yes! Use the get_client_details tool and provide the Client ID. Your agent will retrieve the current health score, success status, and metadata.
How do I list all the contracts associated with my clients?
Run the list_contracts query. The agent will retrieve a history of active and previous service contracts recorded in your ClientSuccess account.
Is it possible to see the available customer segments via AI?
Absolutely. Use the list_segments query. The agent will retrieve the complete list of customer segments used to categorize your client base.
How does Windsurf discover MCP tools?
Windsurf reads the mcp_config.json file on startup and connects to each configured server via Streamable HTTP. Tools are listed in the MCP panel and available to Cascade automatically.
Can Cascade chain multiple MCP tool calls?
Yes. Cascade is an agentic system. it can plan and execute multi-step workflows, calling several tools in sequence to accomplish complex tasks without manual prompting between steps.
Does Windsurf support multiple MCP servers?
Yes. Add as many servers as needed in mcp_config.json. Each server's tools appear in the MCP panel and Cascade can use tools from different servers in a single flow.
Server not connecting
Check Settings → MCP for the server status. Try toggling it off and on.