Bring Cloud Pbx
to Claude Desktop
Learn how to connect Callpicker to Claude Desktop and start using 9 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Callpicker MCP Server?
Connect your Callpicker account to any AI agent and take full control of your cloud-based business telephony and virtual PBX workflows through natural conversation.
What you can do
- Call Orchestration — Programmatically initiate high-fidelity phone calls from your virtual PBX numbers to any destination worldwide directly through your agent
- Communication Intelligence — Monitor real-time incoming and outgoing call history and retrieve detailed logs and high-fidelity Call Detail Records (CDR)
- Recording Management — Access and retrieve secure download URLs for call recordings to maintain high-fidelity oversight of customer interactions
- PBX & Extension Architecture — Access your complete directory of virtual phone numbers and PBX extensions to coordinate your internal communication structure
- Operational Monitoring — Check real-time system status and generate performance reports over specific date ranges directly through your agent
How it works
1. Subscribe to this server
2. Retrieve your Client ID and Client Secret from the Callpicker Portal (Configuration > API)
3. Start managing your business voice pipeline from Claude, Cursor, or any MCP client
No more manual logging of phone results or digging through complex PBX portals. Your AI acts as your dedicated telephony engineer and voice coordinator.
Who is this for?
- Sales & Support Teams — instantly initiate calls to leads and retrieve conversation recordings using natural language commands
- Operations Managers — monitor PBX system health and automate call log analysis without leaving your workspace
- Developers — integrate high-speed virtual calling and CDR data into custom workflows through simple AI queries
Built-in capabilities (9)
Get details for a specific call
Get Call Detail Records (CDR)
Check PBX system status
Get the download URL for a recording
List recent call logs
List available call recordings
List PBX extensions
List virtual phone numbers
Initiate a phone call
Why Claude Desktop?
Claude Desktop is the definitive way to connect Callpicker to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 9 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
Callpicker in Claude Desktop
Callpicker and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Callpicker 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 Callpicker in Claude Desktop
The Callpicker 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 9 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
Callpicker for Claude Desktop
Every tool call from Claude Desktop to the Callpicker 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 Callpicker Client ID and Secret?
Log in to the Callpicker Portal, navigate to Configuration > API, and generate your credentials.
Can I retrieve call recordings via AI?
Yes! The get_recording_url tool provides a temporary secure link to play or download any recorded interaction in your account.
How do I check my virtual numbers?
Use the list_virtual_numbers tool to retrieve your complete directory of active virtual phone numbers programmatically.
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.