Bring Customer Success
to VS Code Copilot
Learn how to connect ClientSuccess to VS Code Copilot 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 VS Code Copilot?
GitHub Copilot Agent mode brings ClientSuccess data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 6 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
ClientSuccess in VS Code Copilot
ClientSuccess and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect ClientSuccess to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
