Setting up the Zernio MCP Server
Connect the Zernio MCP Server via OAuth or an API key, link social accounts, and deliberately safeguard write access to posts, inboxes, and ad campaigns.
- Skill Road
- Setting up the Zernio MCP Server
Published on 28.09.2026
The Zernio MCP Server exposes posts, inboxes, analytics, and ad campaigns from multiple social media accounts to external AI clients. This guide covers setup from client configuration to the first safe request.
Prepare your Zernio account
Before MCP setup, create a Zernio account and connect at least one social media or messaging platform through it, such as Instagram or LinkedIn. Per the provider, the first two connected accounts are permanently free to use, so the server can be tried without a credit card.
Establish the connection
The endpoint is the same in every MCP client: https://mcp.zernio.com/mcp. In Claude Code, two commands are enough:
claude mcp add --transport http zernio https://mcp.zernio.com/mcp
claude /mcpOther clients with native remote/OAuth support, such as Cursor or Codex, also only need this server URL.
Choose authentication
For interactive clients with OAuth support, a browser consent screen opens on first connection (OAuth 2.1 with PKCE). For clients without OAuth support, or for autonomous, non-interactive agents, a Zernio API key can be set as an Authorization: Bearer header instead.
Explore the tool catalog
The 20 core tools cover the most common flows, such as creating and scheduling posts or retrieving analytics. For more specialized tools generated from the OpenAPI specification, it's worth calling search_tools first to find the right tool before using it via call_tool — this keeps context usage small.
Limit permissions and ad spend
When granting OAuth consent or creating an API key, connect only the accounts actually needed. Anyone using the ad campaign tools should set a spending limit in the Zernio account beforehand, before an agent creates campaigns with real budget on its own.
Test the first request
After setup, try a harmless read operation first, such as retrieving current analytics for a connected account. This verifies the connection before write tools for posts, inbox replies, or ad campaigns are used in production.
Source: docs.zernio.com/mcp, checked on 2026-09-28.
Frequently asked questions
Is the Zernio MCP Server free to use?
Yes, permanently for the first two connected social media accounts, including full API access and a monthly inbox message allowance. Additional accounts follow a usage-based, tiered pricing model — see zernio.com/pricing.
Do I have to host the server myself?
No. The server runs exclusively as a Zernio-hosted remote service at mcp.zernio.com; there is no local installation or repository of its own for the server code.
Which platforms does the server support?
Per the provider, 16 social and messaging platforms, including Instagram, LinkedIn, X, TikTok, WhatsApp, and Telegram, plus seven ad networks such as Meta Ads and Google Ads.
How does Zernio differ from a single-platform server like the X API MCP Server?
The X API MCP Server covers only X (Twitter). Zernio bundles 16 platforms plus ad networks behind a single endpoint, making it better suited to cross-channel automation than to the full depth of a single platform API.
Can an agent spend ad budget on its own through the server?
Yes, provided the relevant tools are granted. Before production use, it is recommended to set a spending limit in the Zernio account beforehand and review agent output before any campaign launch.
What do the search_tools and call_tool tools do?
They dynamically load additional tools generated from the OpenAPI specification on demand, instead of loading the entire tool catalog into the language model's context from the start.