Adversus MCP Server for Mastra AIGive Mastra AI instant access to 7 tools to Add Contact To Campaign, Get Campaign Details, List Account Users, and more
Mastra AI is a TypeScript-native agent framework built for modern web stacks. Connect Adversus through Vinkius and Mastra agents discover all tools automatically. type-safe, streaming-ready, and deployable anywhere Node.js runs.
Ask AI about this App Connector for Mastra AI
The Adversus app connector for Mastra AI is a standout in the Sales Automation category — giving your AI agent 7 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
import { Agent } from "@mastra/core/agent";
import { createMCPClient } from "@mastra/mcp";
import { openai } from "@ai-sdk/openai";
async function main() {
// Your Vinkius token. get it at cloud.vinkius.com
const mcpClient = await createMCPClient({
servers: {
"adversus": {
url: "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
},
},
});
const tools = await mcpClient.getTools();
const agent = new Agent({
name: "Adversus Agent",
instructions:
"You help users interact with Adversus " +
"using 7 tools.",
model: openai("gpt-4o"),
tools,
});
const result = await agent.generate(
"What can I do with Adversus?"
);
console.log(result.text);
}
main();
* 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 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.
Mastra's agent abstraction provides a clean separation between LLM logic and Adversus tool infrastructure. Connect 7 tools through Vinkius and use Mastra's built-in workflow engine to chain tool calls with conditional logic, retries, and parallel execution. deployable to any Node.js host in one command.
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
The Adversus MCP Server exposes 7 tools through the Vinkius. Connect it to Mastra AI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 7 Adversus tools available for Mastra AI
When Mastra AI connects to Adversus through Vinkius, your AI agent gets direct access to every tool listed below — spanning dialer, telemarketing, outbound-sales, 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.
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
Connect Adversus to Mastra AI via MCP
Follow these steps to wire Adversus into Mastra AI. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Install dependencies
npm install @mastra/core @mastra/mcp @ai-sdk/openaiReplace the token
[YOUR_TOKEN_HERE] with your Vinkius tokenRun the agent
agent.ts and run with npx tsx agent.tsExplore tools
Why Use Mastra AI with the Adversus MCP Server
Mastra AI provides unique advantages when paired with Adversus through the Model Context Protocol.
Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure. add Adversus without touching business code
Built-in workflow engine chains MCP tool calls with conditional logic, retries, and parallel execution for complex automation
TypeScript-native: full type inference for every Adversus tool response with IDE autocomplete and compile-time checks
One-command deployment to any Node.js host. Vercel, Railway, Fly.io, or your own infrastructure
Adversus + Mastra AI Use Cases
Practical scenarios where Mastra AI combined with the Adversus MCP Server delivers measurable value.
Automated workflows: build multi-step agents that query Adversus, process results, and trigger downstream actions in a typed pipeline
SaaS integrations: embed Adversus as a first-class tool in your product's AI features with Mastra's clean agent API
Background jobs: schedule Mastra agents to query Adversus on a cron and store results in your database automatically
Multi-agent systems: create specialist agents that collaborate using Adversus tools alongside other MCP servers
Example Prompts for Adversus in Mastra AI
Ready-to-use prompts you can give your Mastra AI agent to start working with Adversus immediately.
"List all active campaigns and their performance in Adversus."
"Add 'John Doe' (+15550123) to the 'New Business' campaign (ID: 'camp_456')."
"Show the last 5 leads captured across all my campaigns."
Troubleshooting Adversus MCP Server with Mastra AI
Common issues when connecting Adversus to Mastra AI through the Vinkius, and how to resolve them.
createMCPClient not exported
npm install @mastra/mcpAdversus + Mastra AI FAQ
Common questions about integrating Adversus MCP Server with Mastra AI.
How does Mastra AI connect to MCP servers?
MCPClient with the server URL and pass it to your agent. Mastra discovers all tools and makes them available with full TypeScript types.