Bring Churn Reduction
to Cursor
Learn how to connect Upzelo to Cursor 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 Cursor?
Cursor's Agent mode turns Upzelo into an in-editor superpower. Ask Cursor to generate code using live data from Upzelo and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Upzelo in Cursor
Upzelo and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Upzelo to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.