Bring B2b Support
to Claude Desktop
Learn how to connect Pylon to Claude Desktop 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 Claude Desktop?
Claude Desktop is the definitive way to connect Pylon to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 11 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Pylon in Claude Desktop
Pylon and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Pylon to Claude Desktop 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 Claude Desktop
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 Claude Desktop 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 Claude Desktop
Every tool call from Claude Desktop 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.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.