Bring Customer Success
to Cursor
Learn how to connect Custify to Cursor and start using 8 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Custify MCP Server?
Connect your Custify customer success account to any AI agent and simplify how you manage your product users, track account health, and monitor churn risk through natural conversation.
What you can do
- User & Company Oversight — List all managed people and organizations and retrieve detailed metadata and health scores.
- Health Monitoring — Query health score metrics and values to identify at-risk customers and churn signals instantly.
- Event Tracking — Record custom user actions and events programmatically to feed your success analytics.
- Segment Analysis — List and query defined customer segments to understand your user distribution.
- CRM Control — Create new person records and update profile data directly via AI commands.
- Engagement Insights — Fetch engagement history and metadata for individual accounts directly from the agent.
How it works
1. Subscribe to this server
2. Enter your Custify API Key (found in your account settings)
3. Start managing your customer success lifecycle from Claude, Cursor, or any MCP client
Who is this for?
- Customer Success Managers (CSMs) — quickly check account health and track recent user events via simple AI queries.
- Success Operations — monitor segment distributions and verify company metadata directly from the workspace.
- Product Teams — track custom feature adoption events and monitor user profile quality via the AI assistant.
Built-in capabilities (8)
Create a new person record
Get details for a specific company
Get details for a specific person
List customer companies
List customer health scores
List product users (people)
List user segments
Track a custom event
Why Cursor?
Cursor's Agent mode turns Custify into an in-editor superpower. Ask Cursor to generate code using live data from Custify and it fetches, processes, and writes. all in a single agentic loop. 8 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
Custify in Cursor
Custify and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Custify 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 Custify in Cursor
The Custify 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 8 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
Custify for Cursor
Every tool call from Cursor to the Custify 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 the health score of a company via AI?
Yes! Use the get_company_details tool and provide the Company ID. Your agent will retrieve the current health score, risk status, and account metadata.
How do I track a custom user event using the agent?
Use the track_user_event action. Provide the User ID and the Event Name. You can also pass a JSON object with additional attributes for the action.
Is it possible to see my defined customer segments via AI?
Absolutely. Use the list_user_segments query. The agent will retrieve the complete list of segments configured in your Custify account.
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.