Bring B2b Support
to Cursor
Learn how to connect Pylon to Cursor and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Pylon MCP Server?
Connect your Pylon CRM (getpylon.com) account to any AI agent and take full control of your customer support and post-sales orchestration through natural conversation. Pylon provides a specialized platform for managing B2B relationships directly within shared channels like Slack and Microsoft Teams, and this integration allows you to retrieve issue metadata, manage account profiles, and search knowledge bases directly from your chat interface.
What you can do
- Issue & Ticket Orchestration — List all managed support issues and retrieve detailed metadata, including creating new issues programmatically.
- Account & Contact Control — Access and monitor your customer accounts and retrieve profile metadata via natural language to maintain a clear overview of your client base.
- Conversation Intelligence — Retrieve and analyze message threads within specific issues to understand customer intent and provide synthesized summaries.
- Knowledge Base Integration — Access and search through your organization's knowledge bases to find relevant documentation directly from the AI interface.
- Operational Monitoring — Track organization-wide support health and manage custom field metadata using simple AI commands.
How it works
1. Subscribe to this server
2. Enter your Pylon API Token from your dashboard settings
3. Start managing your customer support from Claude, Cursor, or any MCP-compatible client
No more manual issue tracking or switching between support channels. Your AI acts as a dedicated support specialist or customer success lead.
Who is this for?
- Customer Success Managers — quickly retrieve issue summaries and monitor account health without switching apps.
- B2B Support Teams — automate the retrieval of message history and reply to issues via natural conversation.
- Operations Teams — streamline the retrieval of account metadata and monitor organizational support performance directly within the chat.
Built-in capabilities (11)
Pass data as a JSON string. Create a new issue
Get details for a specific customer account
Get details for a specific support issue
Retrieve messages for an issue
List all customer accounts
List knowledge base articles
List all Pylon issues
List all knowledge bases
List all available issue tags
Send a reply to an issue
Update a support issue
Why Cursor?
Cursor's Agent mode turns Pylon into an in-editor superpower. Ask Cursor to generate code using live data from Pylon and it fetches, processes, and writes. all in a single agentic loop. 11 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
Pylon in Cursor
Pylon and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Pylon 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 Pylon in Cursor
The Pylon 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 11 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
Pylon for Cursor
Every tool call from Cursor to the Pylon MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my AI automatically find the latest messages for a specific support issue?
Yes! Use the get_issue_messages tool with the Issue ID. Your agent will respond with the complete metadata for the conversation thread, including sender details and timestamps in seconds.
How do I find my Pylon API Token?
Log in to your Pylon dashboard, navigate to Settings > API (or app.getpylon.com/settings/api), and you will find or generate your unique secret token there.
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.