Mav MCP. Automate Candidate Screening Via SMS Campaigns
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Mav connects your AI client directly to a full recruiting pipeline, letting you manage candidates and qualify leads via SMS conversation.
Use automated playbooks to send human-like outreach, track replies, and schedule appointments without touching an inbox.
What your AI agents can do
Create lead
Creates a new candidate record and immediately starts an automated screening playbook for them.
Get lead
Retrieves all current details, including qualification score and status, for one specific lead ID.
Get playbook
Pulls the full structure and ruleset of a specific automated screening playbook.
The server starts a new lead record and triggers an automated playbook conversation flow with a target prospect.
It pulls all current details for a specific candidate, including their status and history.
You can launch and track large-scale recruiting outreach campaigns targeting lists of candidates.
The agent stops or pauses a running qualification playbook on a lead, allowing manual intervention before restarting it later.
It lists recent events across all campaigns—like replies received or playbooks that finished—giving you an audit trail.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 CompatibleWaiting for input…
Mav MCP Server: 9 Tools for Lead Management & Playbooks
Use these nine tools to manage the full recruiting lifecycle—from creating initial lead records to stopping complex automated playbooks.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Mav on Vinkius019dd120create lead
Creates a new candidate record and immediately starts an automated screening playbook for them.
019dd120get lead
Retrieves all current details, including qualification score and status, for one specific lead ID.
019dd120get playbook
Pulls the full structure and ruleset of a specific automated screening playbook.
019dd120list activities
Retrieves a chronological list of all recent events, such as replies or campaign launches, across your account.
019dd120list leads
Lists every candidate in the system and provides basic metrics like their current qualification status.
019dd120list playbooks
Displays all screening playbooks you have created, allowing you to see what workflows are available.
019dd120opt out lead
Manually removes a lead from all future communications and campaigns.
019dd120stop playbook
Stops an ongoing automated screening process for a specific lead, usually because the candidate needs to be manually reviewed first.
019dd120update lead
Changes specific data points (like salary expectation or availability) on an existing lead record.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Mav, then connect any of our 4,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Mav. 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.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 9 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Tracking candidate status shouldn't take three different dashboard clicks.
Right now, you check Dashboard A for campaign volume. Then you click over to CRM Tab B to see which leads are marked 'Qualified.' Finally, you open the separate Activity Log C just to find out who replied yesterday. It’s a terrible flow—a mix of copy-pasting and cross-referencing that loses time and context.
With this MCP server, your agent runs one simple command: `list_leads`. You get a single, unified view that shows the qualification status, the total activity count, *and* the last recorded interaction date. It pulls everything into one data stream.
The Mav MCP Server makes managing lead status effortless.
Before this server, if a candidate changed their salary expectations or got a new job title, you had to manually find them in the system and update multiple fields across three separate tabs just to keep the record clean. It was tedious, slow, and prone to human error.
Now, calling `update_lead` is enough. You pass the required data points—the salary change, the new title—and the server writes it directly to the canonical lead record. The system stays current without you lifting a finger.
What you can do with this MCP connector
Mav connects your AI client straight into a recruiting pipeline, letting you handle candidate screening and lead qualification using SMS conversations. You don't have to touch an inbox; your agent manages it all for you.
To get started, you can use create_lead. Running this tool both creates the new candidate record in the system and immediately kicks off an automated screening playbook designed just for them.
When you need to check up on a specific person, you've got get_lead. It pulls every current detail for a single lead ID, giving you their qualification score and full status report. You can also use list_leads; this shows you every candidate in the entire system, along with basic metrics like what stage they're at right now.
Want to see exactly what kind of automated workflows are available? Use list_playbooks to display all the screening playbooks Mav has built out. If you need to know how a specific playbook works, you run get_playbook. This pulls the full structure and ruleset for any given automation.
For keeping track of everything that's happening—the replies received or when a campaign finishes—you use list_activities. It gives you a chronological list of every recent event across your entire account. You can also check what campaigns are running by using the playbook tools to manage outbound SMS outreach, letting you launch and monitor large-scale recruiting efforts targeting lists of candidates.
Managing an active lead means controlling the automation. You can use update_lead to change specific data points on an existing record, like their salary expectations or when they're available for interviews. If a candidate needs manual eyes on them before the playbook continues, you run stop_playbook. This stops any ongoing automated screening process for that lead so you can step in.
Sometimes a lead isn't ready for outreach. You can use opt_out_lead to manually remove a candidate from all future SMS communications and campaigns, keeping the pipeline clean. The system also gives you direct control over playbooks; besides stopping them, your agent handles the whole sequence of automated conversations.
Here's how it works: Your AI client talks directly to these tools. By calling create_lead, you initiate an automatic screening conversation flow with a target prospect. If you need deep background data on one candidate, calling get_lead pulls all current details, including their history and status. You use the list functions—list_leads, list_playbooks, and list_activities—to audit your entire operation.
To manage the content of those conversations, you can update lead data with update_lead. When a playbook needs to pause for human review, you run stop_playbook. You're never stuck in an inbox because every action—from creating the initial record via create_lead to opting someone out using opt_out_lead—is handled through these specific tools.
019dd120-99cf-70fb-8401-7eeedc0a65f0 How Mav MCP Works
- 1 First, subscribe to the Mav server and input your unique API Key into your AI client.
- 2 Second, tell your agent exactly what to do (e.g., 'List all leads that haven't replied in 7 days') by calling a tool like
list_leads. - 3 Third, the agent runs the function, pulling structured data back that you can then use for follow-up actions or reporting.
The bottom line is: your AI client acts as an intermediary, using Mav's tools to perform complex recruiting tasks without needing direct API access.
Who Is Mav MCP For?
Recruiters and Talent Acquisition managers who spend too much time manually updating CRM records or launching campaigns through a separate web dashboard. If your job involves high-volume outreach and tracking candidate responses, this saves hours.
Uses get_lead to pull deep candidate profiles quickly; needs to know if the lead is qualified before sending a follow-up message.
Runs bulk campaigns using the API, then uses list_activities to generate weekly reports on campaign performance and drop-offs.
Monitors compliance by calling opt_out_lead, ensuring that candidates who request removal are immediately handled in the system.
What Changes When You Connect
- Stop relying on manual status updates. Use
list_leadsto instantly see every candidate's current qualification status, letting you filter out cold contacts immediately. - Don't write follow-up scripts from scratch. Calling
get_playbookshows the exact ruleset used for screening, helping your agent execute multi-step conversations flawlessly. - Manage compliance and risk with one call: use
opt_out_leadto instantly remove a candidate from all mailing lists when they request it—no dashboard clicks required. - Keep your outreach running even if you're offline. Use
create_leadto start an automated campaign right away, triggering the playbook without constant supervision. - Get the full picture of what happened last week by calling
list_activities, giving you a comprehensive audit trail of every interaction and metric. - Correctly pause workflows when needed. If a candidate needs a manual review, use
stop_playbookto halt the automated sequence, ensuring no messages are sent prematurely.
Real-World Use Cases
The weekly status report dump
A Talent Acquisition Manager needs to know which campaigns hit their goal this week. Instead of downloading 10 CSVs and manually counting replies, they run list_activities through the agent. The agent compiles a clean summary: 'Total screened today: 45; Qualified: 12.' Problem solved in seconds.
The urgent manual fix
A recruiter finds a promising lead, but the automated playbook is running an irrelevant sequence. They use stop_playbook to halt the conversation and then use update_lead to manually input new data points (like 'Budget: High') before resuming it.
High-volume cold outreach launch
The HR Ops team has a list of 500 candidates who fit a niche role. Instead of emailing them, they use create_lead with the entire batch and specify the 'Niche Tech Playbook.' The agent handles the initial SMS flow for all 500 leads automatically.
Checking compliance status
A candidate texts back requesting to be removed from marketing outreach. Instead of forwarding it to a compliance officer, the agent detects the request and calls opt_out_lead immediately, logging the action and protecting the company.
The Tradeoffs
Over-relying on spreadsheets
Manually tracking 100+ candidate statuses in Excel. You spend hours updating cells, only to find out three candidates were actually qualified yesterday but you forgot to manually change their status from 'Active' to 'Qualified'.
→
Use list_leads and then get_lead on specific IDs to pull the live, accurate data directly into your agent. The system maintains the single source of truth; don't trust a local spreadsheet.
Running campaigns without control
Launching a major campaign and then realizing 20 leads need special handling because they work for a competitor you can't use. You have to wait until the playbook finishes, wasting time and risking bad interactions.
→
Always monitor with list_activities and be ready to call stop_playbook. This lets your agent halt the process immediately so you can manually adjust the lead profile using update_lead before restarting.
Creating leads without purpose
Simply calling a tool just to 'save' a contact. You create a lead, but never define what conversation it needs or what playbook should run next. It becomes digital dead weight.
→
Always follow create_lead with the intention of running a specific workflow. Use list_playbooks first to confirm which structured screening flow you need to attach.
When It Fits, When It Doesn't
Use this MCP server if your recruiting process is high-volume, relies heavily on SMS outreach, and requires constant status updates (e.g., Technical Recruiter, TA Ops). The key is automating the conversation flow itself.
Don't use it if:
1. Your hiring is purely internal or involves only scheduled video calls. (You just need a standard CRM).
2. You are managing very few leads per month. (The overhead of API keys and tool calling isn't worth it).
3. You need to integrate deeply with payroll or HRIS systems for salary data. (This server handles lead qualification, not final employment contracts; look into specialized HRIS integrations instead.)
When you do use it, remember the tools work in sequence: First, list_leads to find a target ID; second, get_playbook to see which flow applies; third, create_lead if they are new, or update_lead before running the playbook.
Common Questions About Mav MCP
How do I check if a candidate is already in the system using Mav MCP Server? +
You use list_leads to pull a list of existing IDs, or if you have an ID, call get_lead. This confirms their current status and ensures you aren't duplicating records before running any playbooks.
Can I start a campaign for leads that are already in the system? +
Yes. You don't need to use create_lead. Instead, first confirm their status with get_lead, and then you can proceed to run or restart the required playbook.
What is the difference between list_leads and list_activities? +
list_leads gives you a snapshot of people (the leads) and their current state. list_activities gives you an event log—it shows what happened across all campaigns over time, like 'Lead X replied to message Y'.
How do I prevent my agent from spamming candidates? +
You can use opt_out_lead immediately if a candidate asks to stop contact. This is the safest way to ensure they are permanently removed from all automated outreach.
If I use `update_lead`, what data formats does it require for different fields? +
The required format depends entirely on the field you're updating. You must check the specific API documentation to confirm if a value needs to be a string, boolean, or integer before calling update_lead.
If an automated screening conversation gets stuck, how can I use `stop_playbook`? +
You pass the lead ID and the playbook ID. This action immediately halts all communication for that specific candidate, letting you manually review the status or restart the flow.
When I first connect to Mav, what should I use `list_leads` for? +
You run list_leads to pull a full snapshot of all existing candidates into your agent's context. This lets you verify the current scope and build an initial dataset before launching any campaigns.
Are there rate limits when I use the `create_lead` tool? +
Yes, Mav enforces standard API usage limits. If your agent exceeds a threshold, it will receive an HTTP 429 error code. You'll need to build exponential backoff into your workflow.
Can I trigger AI screening conversations? +
Yes. Launch SMS or web-based screening flows and track candidate responses automatically.
How does Mav authentication work? +
Mav uses a custom API Key header against hiremav.com/api/v2.
Can I track campaign engagement metrics? +
Yes. Monitor open rates, reply rates, completion rates, and candidate drop-off points.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.