Bring Dialer
to Claude Desktop
Learn how to connect Adversus to Claude Desktop and start using 7 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Adversus MCP Server?
Connect your Adversus account to any AI agent and take full control of your outbound sales operations, telemarketing, and CRM orchestration through natural conversation.
What you can do
- Campaign Orchestration — List all telemarketing and outreach campaigns programmatically, retrieving detailed status, high-fidelity metadata, and performance metrics in real-time
- Lead Execution Intelligence — Programmatically add new contacts and leads to specific campaigns to coordinate your automated dialer and outreach strategy
- Contact Database Management — Access complete directories of leads and contacts assigned to campaigns, retrieving high-fidelity profile metadata and relationship history
- Project & Team Visibility — Access configured CRM projects and associated campaigns to maintain a perfectly coordinated sales pipeline
- Operational Monitoring — Access high-fidelity metadata for account agents and verify API connectivity directly through your agent for instant operational reporting
How it works
1. Subscribe to this server
2. Retrieve your API Key from your Adversus dashboard (Account Settings > API)
3. Start orchestrating your outbound sales pipeline from Claude, Cursor, or any MCP client
No more manual toggling between dialer tabs or digging through complex lead tables. Your AI acts as your dedicated sales operations coordinator and lead architect.
Who is this for?
- Sales Operations Leads — instantly retrieve campaign performance recaps and manage lead distribution using natural language commands
- Telemarketing Managers — coordinate agent assignments and monitor campaign health without leaving your workspace
- Business Developers — automate the ingestion of new leads into specialized outreach campaigns through simple AI queries
Built-in capabilities (7)
Add a new contact to a campaign
Get details for a specific campaign
List team users
List global leads
List contacts in a campaign
List Adversus campaigns
List projects
Why Claude Desktop?
Claude Desktop is the definitive way to connect Adversus to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 7 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
Adversus in Claude Desktop
Adversus and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Adversus 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 Adversus in Claude Desktop
The Adversus 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 7 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
Adversus for Claude Desktop
Every tool call from Claude Desktop to the Adversus 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 Adversus API Key?
Log in to your account, navigate to Account Settings > API, and generate or copy your unique API Key.
Can I add a contact to a specific campaign via AI?
Yes! The add_contact_to_campaign tool allows your agent to register new leads programmatically by providing the campaign ID and phone number.
How do I check my global leads?
Use the list_active_leads tool to retrieve a comprehensive directory of all contacts across your entire Adversus account.
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.