Customerly MCP Server for Claude DesktopGive Claude Desktop instant access to 8 tools to Add Tag, Create Update Lead, Create Update User, and more
Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.
Ask AI about this App Connector for Claude Desktop
The Customerly app connector for Claude Desktop is a standout in the Marketing category — giving your AI agent 8 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Customerly and 3,400+ MCP Servers from a single visual interface.
{
"mcpServers": {
"customerly": {
// Your Vinkius token. get it at cloud.vinkius.com
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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
About 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.
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.
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
The Customerly MCP Server exposes 8 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 8 Customerly tools available for Claude Desktop
When Claude Desktop connects to Customerly through Vinkius, your AI agent gets direct access to every tool listed below — spanning customerly, customer-success-api, live-chat-automation, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
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
Connect Customerly to Claude Desktop via MCP
Follow these steps to wire Customerly into Claude Desktop. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Open Claude Desktop Settings
claude_desktop_config.jsonAdd the MCP Server
mcpServers sectionRestart Claude Desktop
Start using Customerly
Why Use Claude Desktop with the Customerly MCP Server
Claude Desktop by Anthropic provides unique advantages when paired with Customerly through the Model Context Protocol.
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 + Claude Desktop Use Cases
Practical scenarios where Claude Desktop combined with the Customerly MCP Server delivers measurable value.
Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation
Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language
Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary
Learning and training: new team members can explore API capabilities conversationally without needing to read documentation
Example Prompts for Customerly in Claude Desktop
Ready-to-use prompts you can give your Claude Desktop agent to start working with Customerly immediately.
"List all active users in my Customerly account."
"Create a new lead for 'Jane Smith' at 'jane@example.com'."
"Show me the transcript for conversation ID 'conv_456'."
Troubleshooting Customerly MCP Server with Claude Desktop
Common issues when connecting Customerly to Claude Desktop through the Vinkius, and how to resolve them.
Server not appearing after restart
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).Authentication error
Tools not showing in chat
Customerly + Claude Desktop FAQ
Common questions about integrating Customerly MCP Server with Claude Desktop.
How does Claude Desktop discover MCP tools?
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?
Can I connect multiple MCP servers simultaneously?
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.