How to Use the Adversus MCP in Claude Code

Pipe Adversus sales data directly into your terminal with Claude Code to automate lead routing and campaign reporting from the CLI.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Adversus MCP to Claude Code

Create your Vinkius account to connect Adversus to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Adversus with Claude Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Headless Adversus MCP Server Scripts

Terminal users do not need a graphical interface to manage sales pipelines. You drop this integration into your shell, and your agent can immediately start pulling metrics. Running a quick `list_active_leads` command lets you check the outbound queue without ever opening a browser. This gets powerful when you tie it to cron jobs. Set up a script that checks `get_campaign_details` every morning and pipes the output into a Slack webhook. Your call center managers get their daily dialer stats automatically.

Automate Lead Ingestion with Claude Code

Migrating contacts from a legacy CRM into your active dialing campaigns is usually a massive headache. You can tell your CLI agent to read a local CSV file, parse the rows, and fire `add_contact_to_campaign` for every valid entry. The agent handles the rate limiting and retries on its own. It uses `list_campaign_contacts` to verify the migration succeeded, logging any failed imports to a text file for your review.

Audit Team Workloads from the Shell

Figuring out which sales reps are assigned to which projects takes too many clicks in the web UI. Just ask your terminal agent to map it out. It grabs the user list via `list_account_users` and matches them against active initiatives. To get the full picture, it chains `list_crm_projects` and `list_campaigns`. You get a clean, formatted table printed straight to your standard output showing exactly who is dialing what.

Setup guide

Set up Adversus MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see adversus-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Adversus transactions." It will automatically discover and invoke the available Adversus tools.

Terminal

claude mcp add --transport http adversus-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Adversus MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

{
  "mcpServers": {
    "adversus-mcp": {
      "type": "url",
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Adversus. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Adversus now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Adversus MCP in Claude Code

Run claude mcp add --transport http adversus -- . Make sure you put the flags before the server name. Use claude mcp list to check the connection.

Absolutely. You can inject this MCP Server into a GitHub Action to verify campaign configurations before deploying new sales automation scripts.

Your endpoint token is probably missing or expired. Update the configuration file located at ~/.claude.json with your fresh Vinkius credentials.

While stdio is supported by the client, Vinkius remote servers require the HTTP or SSE transport flags to communicate properly with the isolated environment.

We route your outbound prospect numbers and sales rep identities through a strict zero-trust boundary. Vinkius handles the request in a temporary sandbox that destroys itself immediately after returning the payload to your terminal.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript