OpenClaw Integration: Connect to LinkedIn via Zevari
Give an OpenClaw agent safe LinkedIn access through Zevari - add the MCP server to ~/.openclaw/openclaw.json with an MCP access token or call the REST API, and run an approval-gated find, score, stage, approve loop.
Overview
OpenClaw is a self-hosted autonomous runtime, configured in ~/.openclaw/openclaw.json and run 24/7. Zevari is the LinkedIn execution layer it calls. Connect two ways: add the Zevari MCP server under mcp.servers in ~/.openclaw/openclaw.json, or call the bearer-token REST API. Both run the same approval gate and safety model.
Prerequisites
A Zevari account, an API key (zvr_api_..., sent as Authorization: Bearer), workspace membership, and an exact funded LinkedIn sender seat associated with that workspace. The canonical REST reference is the bring-your-own-agent page.
Connect via openclaw.json (MCP)
Add Zevari under mcp.servers in ~/.openclaw/openclaw.json: mcp: { servers: { zevari: { url: "https://mcp.zevari.ai/mcp", transport: "streamable-http", headers: { Authorization: "Bearer ${ZEVARI_MCP_TOKEN}" } } } }. ZEVARI_MCP_TOKEN is a Zevari MCP access token (zvr_mcp_...), created in Settings → Developers on the MCP access tokens tab and shown once. The agent then discovers Zevari's LinkedIn tools automatically.
Connect via REST (bearer)
For agents that prefer plain HTTP, call https://api.zevari.ai with Authorization: Bearer <key> - for example, search recent signal posts, then score, draft, and stage a campaign.
A working loop: find, score, stage, approve
Search posts or profiles, ICP-score the matches, draft in your voice, create a campaign, then stage each write with confirmations.requestAction. A human approves, and only then does the write execute. The agent runs 24/7 but never sends unattended.
Safety and approval notes
Every LinkedIn write is staged for approval. Server-side weekly ceilings (150 on Free* and Premium, 200 on Sales Navigator), working hours, and burst caps are enforced, and no browser cookies are used. The weekly figure covers connection requests sent without a note: LinkedIn caps requests that carry a note at 5 a month on a free account, and gives Premium and Sales Navigator a far larger allowance, so Premium or Sales Navigator is the practical choice for real outbound (see zevari.ai/safety).
Docs Links
- Help Center
Human-facing guide to Zevari skills, workflows, agents, videos, safety, and support.
- Workflow Guide
LinkedIn outreach, content, prospect research, audience analysis, campaign, inbox, and GTM workflows for Claude.
- Prompting Guide
Copy-ready prompts that require AI assistants to read the MCP reference before acting.
- Workspaces and Sender Seats
Human-facing setup guide for free workspaces, payer-account billing, members, funded LinkedIn seats, and sender associations.
- Safety Center
Human-facing guide to Zevari safety guardrails, warm-up, pauses, blocked actions, and recovery state.
- Warm-Up
Human-facing guide to LinkedIn sender warm-up and gradual activity ramping.
- API Playbooks
Ordered REST call flows for developers and AI agents using the Zevari API.
- MoltSets + LinkedIn Workflows
Use MoltSets verified contact data with Zevari's LinkedIn enrichment, campaign, and approval-gated execution layer.
- MCP Reference
Agent-facing tool schemas, capability contracts, examples, gotchas, and recovery guidance.
- API Reference
Public REST API reference powered by the Zevari OpenAPI document.
- MCP Reference JSON
Machine-readable MCP tool reference.
- LLMs Full
AI-readable Zevari documentation bundle.
- Support
Send bug reports, support handoffs, and feature requests.