Zernio MCP

Zernio provides a hosted MCP endpoint for social media management plus local Python MCP entrypoints from the zernio-sdk[mcp] package.

Hosted Remote

The hosted endpoint is https://mcp.zernio.com/mcp. It is represented in remotes[] separately from local package launches. Clients can authorize through Zernio OAuth where supported, or use an Authorization: Bearer header with a user-provided Zernio API key.

Claude Desktop's JSON config is stdio-only, so the public docs recommend connector UI setup for the hosted endpoint or an mcp-remote bridge for stdio-only clients.

Local stdio package target

The reviewed local package target is zernio-sdk[mcp] version 1.4.176, launched with:

uvx --from zernio-sdk[mcp] zernio-mcp

The stdio MCP implementation reads API credentials from ZERNIO_API_KEY first, then legacy LATE_API_KEY. It also supports MCP-specific base URL overrides ZERNIO_BASE_URL and LATE_BASE_URL; when unset, the SDK client default base URL is https://zernio.com/api. ZERNIO_API_URL is CLI configuration metadata from the Zernio CLI docs and is not included in the local MCP package transport env.

Optional HTTP package entrypoint

The same package also exposes zernio-mcp-http and legacy late-mcp-http. This optional HTTP server is intentionally included in source review evidence and package argument metadata, but it is not the default package launch. It exposes Streamable HTTP at /mcp, legacy SSE at /sse plus /messages/, /health, and OAuth protected-resource metadata. It accepts user API keys in Authorization: Bearer request headers, so it does not require an API key environment variable at server startup.

Source-backed optional HTTP settings include HOST (default 0.0.0.0), PORT (default 8080), MCP_PUBLIC_URL (default https://mcp.zernio.com), and MCP_ALLOWED_ORIGINS for DNS-rebinding origin allowlisting. The HTTP CLI exposes optional --host, --port, and --debug flags; these are recorded with includeInLaunch: false because the default package launch is stdio.

Capabilities

The MCP server exposes generated Zernio API tools plus hand-written core tools for social accounts, profiles, posts, cross-posting, retries, media upload links and upload status, documentation search, ads, WhatsApp, inbox, contacts, sequences, comment automations, broadcasts, analytics, OAuth/connect flows, webhooks, and workflows.

Limitations

Hosted remote clients need Zernio OAuth support or a bearer API key. Local stdio mode requires Python 3.10+, uvx or pip installation, and a valid Zernio API key. HTTP self-hosting requires a reachable host/port and clients must provide Authorization: Bearer per request. Multi-account users must pass account_id or profile_id to avoid ambiguous account selection. Media flows require generating an upload link, uploading the file, and then using the resulting media URL.