Bring Dialer
to Cursor
Learn how to connect Adversus to Cursor 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 Cursor?
Cursor's Agent mode turns Adversus into an in-editor superpower. Ask Cursor to generate code using live data from Adversus and it fetches, processes, and writes. all in a single agentic loop. 7 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Adversus in Cursor
Adversus and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Adversus to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.