Zernio MCP Server
Official, hosted MCP server from Zernio: control posts, inboxes, analytics, and ad campaigns across 16 social platforms and 7 ad networks behind a single endpoint.
- Skill Road
- Zernio MCP Server
Categories
Description
The Zernio MCP Server implements the Model Context Protocol on top of Zernio's own API and opens up social media and messaging accounts to external AI systems. Instead of building a separate OAuth integration and API client for every platform, an MCP client connects to exactly one endpoint and gets access to all connected accounts through it. Technical documentation lives at docs.zernio.com/mcp; the service is operated by the Zernio organization (GitHub org zernio-dev).
Tool architecture
Per official documentation, a core group of 20 tools covers the most common flows, including creating, scheduling, and drafting posts, managing connected accounts, retrieving analytics and engagement data, creating ad campaigns, controlling the publishing queue, and validating and checking the health of connected accounts. Beyond that, the server automatically generates one tool per endpoint of its OpenAPI specification. To keep this large tool catalog from overwhelming every conversation's context, additional tools can be found via search_tools and loaded on demand via call_tool, rather than being fully present in the language model's context from the start.
Supported platforms and ad networks
According to the homepage, the server covers 16 social and messaging platforms, including Instagram, TikTok, YouTube, X/Twitter, LinkedIn, Facebook, Threads, Pinterest, Reddit, Bluesky, WhatsApp, Telegram, Discord, Snapchat, and Google Business Profile. In addition, ad campaigns can be managed on seven networks: Meta Ads, Google Ads, TikTok Ads, LinkedIn Ads, Pinterest Ads, X Ads, and OpenAI Ads (ChatGPT Ads). This breadth makes the server particularly interesting for teams running multiple channels in parallel that previously had to maintain several separate integrations.
Setup and authentication
The server is available exclusively as a hosted remote service at https://mcp.zernio.com/mcp via Streamable HTTP; per the documentation, there is no local installation path or open-source repository for the server code itself. Two authentication paths are available: MCP clients with OAuth support use OAuth 2.1 with PKCE and need only the server URL; clients without OAuth support and autonomous agents instead authenticate via an API key sent as an Authorization: Bearer header. For Claude Code, the documentation lists two setup commands: claude mcp add --transport http zernio https://mcp.zernio.com/mcp followed by claude /mcp to sign in. Per the provider, Cursor, Codex, ChatGPT, Windsurf, VS Code, and other standard MCP clients are also supported.
Open-source companion projects on the same API
In the zernio-dev GitHub organization, Zernio publishes several open-source tools built on the same underlying API, including the social media scheduler Latewiz, the visual chatbot builder Zernflow, a cross-platform unified inbox, an ads reporting dashboard, and an official Node.js SDK and CLI tool. These projects are distinct from the hosted MCP server described here: the MCP server itself remains a proprietary, hosted-only service with no public source code of its own.
Pricing model
Per the provider, the first two connected social media accounts are permanently free to use, including a monthly inbox message allowance, unlimited posts, analytics, and full API access. Beyond that, a usage-based, tiered pricing model applies per additional connected account, where the per-account rate decreases as more accounts are connected; metered costs also apply for inbox messages beyond the free allowance, for managed ad spend beyond a free allowance, and optionally for phone numbers, calls, SMS, and WhatsApp usage. No fixed plans or seat-based pricing, and no credit card is required for the free tier. Current amounts are available at zernio.com/pricing.
Security and write access
The tool catalog includes far-reaching write permissions: posts can be published and scheduled, inbox messages replied to, and ad campaigns with real budgets created, across multiple platforms simultaneously. This reach calls for deliberate permission handling: API keys should be stored securely like any other secret, OAuth consent should be granted only for accounts actually needed, and automated ad spending should be capped before an agent launches campaigns on its own. Since inbox content and comments from external users can feed into the connected language model's responses, agent output should be reviewed before any production publishing.
Who the server is a good fit for
The Zernio MCP Server is particularly useful for marketing teams, agencies, and solopreneurs running multiple social media and messaging channels in parallel who want to use an AI agent instead of juggling individual platform dashboards. Compared to single-platform servers such as the already-listed X API MCP Server, Zernio covers not just one but 16 social channels plus ad networks through the same endpoint, making it best suited for cross-channel automation rather than the depth of a single platform's API.
Requirements
A Zernio account with at least one connected social media or messaging platform, an MCP client with streamable HTTP/remote support, and either OAuth 2.1 consent or a Zernio API key.
Installation instructions
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.
Step 1: 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 /mcp
Other clients with native remote/OAuth support, such as Cursor or Codex, also only need this server URL.
Step 2: 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.
Step 3: 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.
claude mcp add --transport http zernio https://mcp.zernio.com/mcp
Authentication
OAuth 2.1 with PKCE for clients with native OAuth support (only the server URL is needed), or a Zernio API key sent as an Authorization: Bearer header for clients without OAuth support and for autonomous agents.
Required access permissions
Access scope depends on the connected Zernio account: via OAuth or API key, the client gets access to all social media and messaging platforms connected to that account, along with their posts, inboxes, analytics, and ad campaigns.
Transmitted or stored data
Requests go through the Zernio-hosted endpoint mcp.zernio.com via Streamable HTTP. Responses can include post, inbox, analytics, and ad campaign data from connected social media accounts and are returned to the MCP client and its language model.
Security risks
The server offers far-reaching write access: posts can be published and scheduled, inbox messages replied to, and ad campaigns with real budgets created across multiple platforms. API keys should be stored securely like any other secret, OAuth consent should be limited to accounts actually needed, and ad spending should be capped. Manipulated inbox or comment content from external users could theoretically carry prompt injection attempts against the connected AI model; review agent output before production publishing and campaign launches.
License and costs
- License
- Not recorded yet.
- Cost
- free
Per the provider, the first two connected social media accounts are permanently free to use, including full API access, unlimited posts and analytics, and a monthly inbox message allowance, with no credit card required. Beyond that, a usage-based, tiered pricing model applies per additional connected account, plus metered extra costs for inbox messages, ad spend, and optional phone/messaging features beyond the free allowances. Current amounts are available at zernio.com/pricing.
Alternatives
Not recorded yet.
At a glance
- Provider
- Zernio
- Status
- Official server
- Deployment
- Remote
- Current version
- Not recorded yet.
- Last reviewed
- 28.09.2026
Repository and documentation
Categories
Supported clients
Related guides
Guides and background related to this entry.
No related guides yet.