How to connect Hermes Agent to LinkedIn - safely (2026)
This is the engineer's guide. You will connect your Hermes Agent to LinkedIn through Zevari over MCP or a REST API bearer token, then run a real loop - find, score, draft, and stage a campaign - with every send held for your approval. No browser cookies. No bans. It takes about ten minutes.
The steps
Connect Hermes Agent to LinkedIn in four steps
- 1
Create a Zevari workspace token
Sign in to Zevari, open Settings, and create a workspace API key. This bearer token is how your Hermes Agent authenticates - no LinkedIn password, no browser cookies, no extension. Treat it like any secret and store it in your agent's environment as ZEVARI_API_KEY.
- 2
Register Zevari in your Hermes Agent config (MCP or REST)
Hermes Agent supports MCP servers natively, so add Zevari to the mcp_servers block in /opt/data/config.yaml and the agent discovers all 60+ LinkedIn tools automatically. Or call the REST API directly with the bearer token from the agent's own code. The MCP path is the cleanest; the REST path is the universal one for any runtime.
Path A - MCP server in config.yamlconfig.yaml# /opt/data/config.yaml - register Zevari as an MCP server mcp_servers: - name: zevari type: http url: https://mcp.zevari.ai/mcp auth: "Bearer ${ZEVARI_API_KEY}"Path B - bearer-token REST from the agentterminal$ curl https://api.zevari.ai/v1/search/posts \ -H "Authorization: Bearer $ZEVARI_API_KEY" \ -d '{"query":"hiring an SDR","posted_within_days":30}' - 3
Verify the connection
Confirm the agent can see Zevari before you run anything live. A read-only call - get the safety status, or search for recent signal posts - proves the token works and returns your workspace context, Voice DNA, and the enforced weekly ceilings.
terminal$ curl https://api.zevari.ai/v1/safety/status \ -H "Authorization: Bearer $ZEVARI_API_KEY" # -> { "connected": true, "weekly_ceiling": 150, "incidents": 0 } - 4
Run your first safe loop: find, score, stage, approve
Tell the agent what you want: find people who posted about a topic in the last 30 days, ICP-score them, draft in your voice, and stage a campaign. Every send is held at the approval gate - you approve from chat, Slack, or a daily digest, and the agent executes inside your ceilings and working hours. Nothing fires unattended, even with a persistent, self-improving loop.
A real loopYou: Find 15 founders who posted about hiring an SDR in the last 30 days.Hermes Agent: Searches signals, ICP-scores each 1 to 5 with reasons, returns 15.You: Draft a warm-up plus connect sequence for the 4s and 5s, in my voice.Hermes Agent: Drafts in your Voice DNA, stages the campaign, stops at the approval gate.You: Approve.Hermes Agent: Executes within your weekly ceiling, on a human-paced schedule.
That is the whole connection. For the broader picture of running Hermes Agent outbound safely, see the Hermes Agent page; for any other runtime, the LinkedIn for AI agents pillar; and for the full endpoint reference, the developer docs.
Why this connection does not get you banned
The reason most "Hermes Agent + LinkedIn" setups earn a ban is cookie-driven browser automation - LinkedIn sees the logs. This setup never touches a browser session. It is a session-based connection with no stored cookies, every write is staged for your approval, and weekly ceilings (Free 40, Premium 80, Sales Navigator 150), working hours, and burst caps are enforced server-side. A year of refinement, zero ban incidents.
FAQ
Connecting Hermes Agent to LinkedIn
How do I connect Hermes Agent to LinkedIn - MCP or REST?
Both work. Hermes Agent supports MCP servers natively, so add Zevari to the mcp_servers block in /opt/data/config.yaml and the agent discovers all 60+ LinkedIn tools automatically. Or call the REST API directly with a bearer token from the agent's own code. The MCP path is the cleanest for Hermes Agent; the REST path is the universal one. Same capabilities and the same approval gate on both.
Will connecting Hermes Agent to LinkedIn get my account banned?
Not the way Zevari does it. Most agent-to-LinkedIn tools drive a logged-in browser session with your cookies, which is the mechanism behind the 2026 bans (HeyReach in March, Apollo and Seamless before it). Zevari uses a session-based connection with no browser cookies, stages every write for your approval, and enforces weekly connection ceilings, working hours, behavioral pacing, and burst caps server-side. A year of refinement, zero ban incidents.
My Hermes Agent runs on a VPS. Does that still work?
Yes - this is exactly what the setup is for. The agent keeps running on your VPS and calls Zevari's hosted endpoint with a bearer token to do the LinkedIn work. Zevari holds the campaign schedule and the approval queue, so the sequence advances even between the agent's runs and nothing sends until you approve.
Is this Hermes Agent or the Hermes LLM?
This guide is about Hermes Agent, the open-source autonomous agent framework from Nous Research - persistent memory, a self-improving loop, VPS-hosted, configured at /opt/data/config.yaml. It is not the separately named open-weight LLM family. Zevari gives the agent framework safe, approval-gated LinkedIn access; whichever underlying model it points at does not change how the safety works.
Does the agent actually send, or just draft?
It stages every message, connection request, comment, and post, and you approve before anything sends - in chat, Slack, or a daily digest. Even a fully autonomous Hermes Agent cannot send unattended. You are always the last step before a send.
Connect Hermes Agent, keep your account
Run it as code over MCP or REST, or have us run the whole engine and approve every send from Slack.