Bring Churn Reduction
to VS Code Copilot
Learn how to connect Upzelo to VS Code Copilot and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Upzelo MCP Server?
Connect your Upzelo churn management account to any AI agent and simplify how you retain customers and manage subscription lifecycles through natural conversation.
What you can do
- Customer Management — List and search customer records, and update profile data for better segmentation and targeting.
- Retention Flows — List available flows and manually trigger retention sequences for customers at risk of cancelling.
- Subscription Tracking — Query all tracked subscriptions and update statuses or trial details programmatically.
- Flow Monitoring — Check the real-time status and outcomes of active flow sessions to verify retention success.
- External ID Sync — Link your internal system identifiers to Upzelo customer records for seamless integration.
How it works
1. Subscribe to this server
2. Enter your Upzelo App ID and API Key (found in your developer settings)
3. Start managing your retention strategy from Claude, Cursor, or any MCP client
Who is this for?
- Customer Success Managers — quickly trigger retention flows and check customer health via simple AI commands.
- Product Operations — monitor subscription statuses and sync customer data directly from the workspace.
- Business Growth Teams — get instant insights into flow performance and active retention sessions.
Built-in capabilities (10)
Get details for a specific customer
Get details for a specific flow
Check the status of a flow session
Get details for a specific subscription
List all customers in Upzelo
List all retention flows
List all subscriptions
Used for segmentation and targeting. Create or update a customer record
Initialize a flow for a customer
Update subscription attributes
Why VS Code Copilot?
GitHub Copilot Agent mode brings Upzelo data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 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
Upzelo in VS Code Copilot
Upzelo and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Upzelo 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 Upzelo in VS Code Copilot
The Upzelo 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 10 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
Upzelo for VS Code Copilot
Every tool call from VS Code Copilot to the Upzelo MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I manually start a retention flow for a customer via AI?
Yes! Use the start_flow tool and provide the Flow ID, Customer ID, and Subscription ID. This will initialize the retention experience for that user immediately.
How do I see if a customer successfully stayed after a flow?
Run the get_flow_session query with the specific Session ID. It will return the outcome and status of the retention attempt.
Is it possible to update a subscription's status via AI?
Absolutely. Use the update_subscription tool by providing the Subscription ID and the new status to synchronize data between your systems and Upzelo.
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.