Bring Customerly
to Claude Desktop
Learn how to connect Customerly to Claude Desktop 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 Customerly MCP Server?
Connect your Customerly account to any AI agent and take full control of your customer success and support workflows through natural conversation.
What you can do
- User & Lead Orchestration — Create and manage customer profiles programmatically, including synchronizing custom attributes and managing lifecycle status
- Conversation Intelligence — Access complete chat histories and retrieve detailed interaction metadata to provide high-fidelity context for support
- Engagement Tracking — Monitor active chat sessions and customer interactions in real-time to optimize your team's response strategy
- Audience Segmentation — Programmatically add or remove tags for users and leads to maintain a structured and personalized communication ecosystem
- Record Management — Securely delete user records or update contact identification to ensure your database remains perfectly coordinated and compliant
How it works
1. Subscribe to this server
2. Retrieve your API Access Token from the Customerly dashboard (Settings > API)
3. Start managing your customer relationships from Claude, Cursor, or any MCP client
No more manual ticket searching or digging through user tables in the portal. Your AI acts as your dedicated success engineer and support coordinator.
Who is this for?
- Customer Success Teams — instantly retrieve user profiles and summary interaction histories using natural language commands
- Marketing Automation Leads — automate the tagging and segmentation of new leads without leaving your workspace
- Product Managers — track user engagement and sync backend metadata through simple AI queries
Built-in capabilities (8)
Provide tag name and contact identification. Add a tag to a contact
Create or update a lead
Provide email and optionally user_id, name, and attributes. Create or update a user
Delete a user
Get details of a specific conversation
List all conversations
List all users
Remove a tag from a contact
Why Claude Desktop?
Claude Desktop is the definitive way to connect Customerly to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 8 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
Customerly in Claude Desktop
Customerly and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Customerly 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 Customerly in Claude Desktop
The Customerly 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 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
Customerly for Claude Desktop
Every tool call from Claude Desktop to the Customerly MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Customerly Access Token?
Log in to your Customerly dashboard, navigate to Settings > API, and generate or copy your Access Token.
Can I read full chat histories?
Yes! The get_conversation tool retrieves the detailed message log and interaction metadata for any specific conversation ID.
How do I add tags to a user?
Use the add_tag tool and provide the tag name along with either the user's email or their unique user_id.
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.