Search + targeting
Profile, company, and post search, signal scanning, ICP scoring 1-5 with reasons, lookalikes from a profile URL.
60-second quickstart
Connect Claude to LinkedIn in 60 seconds.
Run LinkedIn outbound as code - and if you don't run Claude Code or Codex, we run it for you. One command adds Zevari, OAuth in, and your agent has 60+ tools on LinkedIn: search, signals, campaigns, inbox, content. Every write is staged for your approval. No browser cookies.
Reach Zevari over MCP for Claude Code and Codex, or our REST API from your own code. Same 60+ tools. Zero ban incidents in a year of real use.
terminal
Claude Code
$ claude mcp add zevari https://mcp.zevari.ai/mcpCodex
$ codex mcp add zevari https://mcp.zevari.ai/mcpPrefer your own code? Same 60+ tools over our REST API. Works with Claude Code, Codex, and any MCP client - hosted HTTP transport, nothing to install, no Docker, no Chrome profile to babysit.
Step 1
Add the server
One line. Paste it into your terminal - Claude Code or Codex, your choice. Prefer to skip the MCP client entirely? The same 60+ tools are on our REST API, callable straight from your own code.
Claude Code or Codex
$ claude mcp add zevari https://mcp.zevari.ai/mcp$ codex mcp add zevari https://mcp.zevari.ai/mcpConfig-as-code (.mcp.json)
{
"mcpServers": {
"zevari": {
"type": "http",
"url": "https://mcp.zevari.ai/mcp"
}
}
}Drop the config into your project .mcp.json and commit it - your whole team gets the same LinkedIn execution layer on clone. The state lives on our infrastructure, not in a cookie jar on your laptop.
Step 2
Authorize over OAuth
The first Zevari tool call kicks off OAuth in your browser. Sign in, pick the organization and LinkedIn account this session runs as, and you are connected. The token is scoped to your Zevari workspace, not your Claude account.
Connection is session-based. No cookies, no password handoff, no browser extension. We connect to LinkedIn the safe way, and every write action is gated behind your approval before it ships.
Two accounts, two emails
Your Claude login email and your Zevari workspace email are separate things and do not have to match. Claude and Zevari are different accounts - the mismatch trips people up during OAuth, but it is expected, not a bug.
Workspace billing must be enabled
MCP authorization needs billing enabled on the Zevari workspace. If you hit "workspace billing required," that is the fix - add a card in the Zevari dashboard, then re-run the connect.
Step 3
Run your first three prompts
Open Claude Code or Codex. Talk to it in plain English - the agent picks the right tools. Start here.
1/ "Confirm my Zevari context - which org and LinkedIn account am I operating as?"
2/ "Find founders at seed-stage B2B SaaS companies who posted about hiring an SDR in the last 30 days. ICP-score them 1 to 5 with reasons."
3/ "Build a 3-step warm-by-default campaign for the 4s and 5s: react and comment on a recent post, then a connection note, then a value message. Stage it for my approval."
Prompt one confirms you are operating on the right account. Prompt two is signal-based targeting - posted-in-30-days intent and ICP scoring with reasons, not a static title list. Prompt three has your agent build a real multi-step campaign and stage it. Nothing sends until you say so.
A real session, end to end
Prompt, staged campaign, approval, sent
This is an actual run - no edits except trimming the target list for length.
zevari session - apollo-switchers
You › Find people posting about "switching off Apollo" or
"Apollo alternative" in the last 30 days, B2B founders
and heads of growth. Score them against my ICP and show
me the top 5 with reasons.
Claude › [linkedin_search_posts] scanning last-30-day posts for intent...
[agents_icp_score] scoring 41 authors 1-5...
Top 5 (score / reason):
5 Dana R., Head of Growth, devtools SaaS
- Posted 6 days ago: "Apollo's data decay is killing
our reply rate, what are people moving to?" Exact-fit
ICP, active buying signal, decision-maker.
5 Marcus T., Founder, 12-person RevOps agency
- Asked for "Apollo alternative with better LinkedIn"
4 days ago. Agency = multi-account expansion.
4 Priya S., VP Sales, Series A fintech
- Complained about enrichment cost; ICP-fit but
not a clean intent match on "switching."
4 Owen K., Founder, B2B data startup
- Adjacent competitor risk - flagged, you decide.
3 Lena M., SDR manager
- Right topic, wrong seniority for your offer.
You › Build a warm-by-default campaign for the two 5s. Warm
action first, then a connection note that references their
post, then a value message. Use my voice. Stage it.
Claude › [agents_communication_blueprint] loading your Voice DNA...
[campaigns_create] "Apollo-switchers - Jun" (2 targets, 3 steps)
[agents_generate_warming_comment]
[agents_generate_connection_note]
[agents_generate_messages]
[actions_request_confirmation]
Staged. Here's step 1 for Dana R.:
Warm -> React + comment on her Apollo post:
"The data decay point is real - reply rates
fall off a cliff once the records age. What's
your refresh cadence right now?"
Note -> "Saw your post on moving off Apollo - went
through the same call last quarter. Happy to
compare notes if useful."
Msg -> [drafted in your voice, sends 2 days after
the connection is accepted]
To approve in this chat, reply exactly:
approve campaign Apollo-switchers
You › approve campaign Apollo-switchers
Claude › [actions_chat_approve_confirmation] approved
[campaigns_update_status] live
Live. Warm actions queue inside your working hours and
stay under your weekly connection ceiling. I'll classify
replies with Inbox Radar and stage drafts as they come in.Voice DNA wrote the drafts on your sent-message style, so they sound like you and not a bot. The campaign respects your working hours, your weekly connection ceiling, and behavioral pacing - and because it is hosted state, the queue keeps running on schedule whether or not your session is open. That persistent scheduling is the thing Claude Code or Codex cannot do on its own.
The surface area
60+ tools, grouped by what they do
You never call these by hand - the agent does when you run Claude Code or Codex, or you call them directly over the REST API. Either way, here is what you are holding.
Research + voice
Person and company research, behavioral profiling, Voice DNA, communication blueprints.
Campaigns
Create multi-step sequences, add targets, advance steps, track progress.
LinkedIn actions
Connection requests, messages, comments, reactions, profile views, posts - all approval-gated.
Inbox Radar
Classify replies by intent, enrich senders, stage drafts, send digests.
Content
Draft, schedule, and approval-gated publishing in your voice.
Pipeline
Propose meetings, opportunities, and closed deals into a lightweight CRM view.
Safety + settings
Live safety status, connection limits, working hours, pause and resume everything.
Outbound-as-code
Bring your own CLAUDE.md
The best way to run Zevari is the way you would run any serious agent - with a constitution and your ICP as config, version-controlled in the repo. We publish the reference template so you do not start from a blank file: a LinkedIn CLAUDE.md constitution (tone rules, approval policy, do-not-contact lists) plus an icp.yaml your agent scores against.
Every existing reference architecture for this is cold-email-first. This is the LinkedIn one.
repo layout
outbound-as-code/ ├── CLAUDE.md # constitution ├── icp.yaml # ICP as config ├── .mcp.json # zevari MCP server └── do-not-contact.txt
Safety, in receipts
- Every write - message, connection, comment, post - is staged for human approval before it sends.
- Session-based connection, no browser cookies.
- Weekly connection ceilings: Free 40, Premium 80, Sales Navigator 150.
- Working hours, behavioral pacing, duplicate checks, burst caps - enforced server-side, not suggested.
- A year of refinement, zero ban incidents.
No Sales Navigator required to start - you only need it to raise the weekly limit.
FAQ
Quickstart FAQ
Do I run Zevari in Claude Code, Codex, or another MCP client?
Any of them. Reach Zevari over MCP for Claude Code and Codex, or from any other MCP client, or call our REST API straight from your own code. The hosted HTTP server works wherever MCP works. Engineers usually run it in Claude Code or Codex so they can version-control the CLAUDE.md constitution and ICP config alongside the rest of their stack.
Can I use the REST API instead of MCP?
Yes. The same 60+ tools are exposed over a direct REST API, so you can drive Zevari from your own code with no MCP client at all. Engineers who prefer to wire it into an existing service or pipeline reach us over MCP for Claude Code and Codex, or our REST API from their own code - same engine, same approval gates, same safety model either way.
What do I need open on my computer to use it?
Just an MCP client connected to Zevari, or your own code calling the REST API. There is no browser extension, no Chrome profile, and nothing to keep open in the background - the state is hosted, so scheduled actions run on our infrastructure even when your session is closed.
Do I need to use the same email for Claude and Zevari?
No. Claude and Zevari are two separate accounts. They can use different emails. The mismatch trips people up during OAuth - it is expected, not a bug.
How do I set up billing for a workspace?
MCP authorization requires billing enabled on the Zevari workspace. If you see "workspace billing required" during connect, add a card in the Zevari dashboard, then re-run the connection. That one step unblocks the whole OAuth flow.
Will this get my LinkedIn account banned?
No incidents in a year of refinement. Connection is session-based with no browser cookies, every write is approval-gated, and weekly connection ceilings, working hours, behavioral pacing, and burst caps are enforced server-side. Full mechanics on the safety model page.
Do I need LinkedIn Sales Navigator?
No. You can start on a free account. Sales Navigator only raises your weekly connection limit (Free 40, Premium 80, Sales Navigator 150).
How many tools does it have?
60+, grouped across search and targeting, research and Voice DNA, campaigns, LinkedIn actions, Inbox Radar, content, pipeline, and safety. The agent selects them when you run Claude Code or Codex - you talk to it in plain English. Over the REST API you call them directly.
How do you pronounce Zevari?
Zuh-VAR-ee.
Connect now
One command. 60+ tools on LinkedIn.
$ claude mcp add zevari https://mcp.zevari.ai/mcp$ codex mcp add zevari https://mcp.zevari.ai/mcpOperator is $87/mo, additional accounts $37 each vs the $79-99 per-account industry standard. Reach Zevari over MCP for Claude Code and Codex, or our REST API from your own code. Cancel anytime.
Want it set up with you? Launch - $1,500: we pair with you to install the constitution, wire your ICP, and ship your first live campaign together.