Over MCP
Add the hosted endpoint to Claude Code, Codex, ChatGPT, or any MCP client and the team shows up as tools your AI can call.
What the team can do
Sixteen capabilities. Six specialists. One account.
Every one of them is listed here, with who owns it and whether it runs on its own.
Reach them over MCP from Claude, Codex, or any MCP client, or over the REST API from your own code. Research, scoring, and drafting can run without you. Sending never does.
Runs on its owna Zevari worker triggers itOn your AI's callyour AI asks for it, the result is saved to the lead
Research and enrich5
Everything the team learns about a person or a company before anyone writes a word.
Company intelligence
Runs on its ownRuns when a lead is enrolled. Cached 90 days.
Prospecting
agents_company_intelligencePerson research
On your AI's callProfile, posts, comments, education, skills.
Prospecting
agents_research_personBehavioral profile
On your AI's callHow they engage and what they respond to.
Prospecting
agents_behavioral_profileCommunication blueprint
On your AI's callHow to write to this person specifically.
Voice Writer
agents_communication_blueprintLead enrichment
On your AI's callVerified email for the lead, or a phone number when explicitly asked.
Prospecting
agents_enrich_lead
Score and classify5
Sorting the list by what actually closed, and reading what comes back.
ICP scoring
Runs on its ownScores new leads against your criteria, with reasons. Learns from your reviews.
ICP Scoring
agents_icp_scoreSignal scoring
Runs on its ownRanks the reasons to reach out as the scanner finds them.
Signals
agents_score_signalsSignal classification
Runs on its ownSorts signals by kind so the right specialist picks them up.
Signals
agents_classify_signalsInbox radar
On your AI's callReads a thread for intent and fit.
Reply Qualifier
agents_inbox_radarSearch from plain English
On your AI's callTurns a sentence into a LinkedIn search.
Prospecting
agents_extract_search_params
Write4
Every draft in your voice, and every one of them staged for your approval.
Message generation
Runs on its ownDrafts each step when a lead is enrolled. Also on your AI's call.
Voice Writer
agents_generate_messagesConnection notes
On your AI's callThe note that goes with the request.
Voice Writer
agents_generate_connection_noteWarming comments
On your AI's callA real comment on their post before the ask.
Voice Writer
agents_generate_warming_commentPersonalization pass
On your AI's callRewrites a draft against the research.
Voice Writer
agents_personalize
Two ways in
Your AI, or your code.
Same sixteen capabilities, same account, same approval gate. Pick the door that matches how you already work.
Over REST
Call the same capabilities from your own services when you would rather not go through a chat client at all.
What does "runs on its own" mean?
A worker Zevari owns triggers it, on a schedule or on an event like a new lead being enrolled. You do not have to ask. Everything else runs when your AI calls it, from Claude, Codex, or your own code, and the result is saved to the lead.
Which specialist owns which capability?
Each row names its owner. Prospecting and Signals fill and rank the list, ICP Scoring sorts it, Voice Writer writes, Follow-up keeps it moving, Reply Qualifier reads what comes back. The capabilities are the tools they use.
How does my AI get at these?
Over MCP for Claude Code, Codex, and any MCP client, or over the REST API from your own services. Same capabilities either way, same account, same approval gate on every write.
Does any of this send on its own?
No. Research, scoring, and drafting can run without you. Sending cannot. Every message, connection request, comment, and post waits for your approval, unless you have moved that specialist to autopilot after it has earned it.
Will this get my LinkedIn account banned?
The safety layer sits under every capability here: a session-based connection with no browser cookies, enforced weekly ceilings and daily caps, working hours and burst limits, and the approval gate. See the safety page for the numbers.