Skip to main content
Use Zernio’s MCP server to let Notis trigger social media publishing actions while Notis stays responsible for content creation, review, and approval.

​
What this setup does

In this setup, Notis handles the AI work: generating post ideas, drafting captions, creating images, reviewing outputs, validating captions, and checking whether content is ready to publish. Zernio handles the publishing actions through MCP: listing connected social accounts, creating or scheduling posts, cross-posting, and other platform actions exposed by its API.
That split is important: Notis is your creation and validation layer, while Zernio is your execution layer for social publishing.

​
Prerequisites

​
Zernio MCP connection options

Zernio offers a hosted MCP endpoint, so there is nothing to install. You authenticate with your Zernio API key as a Bearer token. Zernio also documents a local MCP option using uvx and the zernio-sdk[mcp] package if you want to run the server yourself. For most Notis users, the hosted SSE endpoint is the simplest setup.

​
Step 1: Get your Zernio API key

Open the Zernio API key page and create or copy an API key you want Notis to use. Keep this key secure. Notis will use it to authenticate against Zernio’s MCP server.

​
Step 2: Add Zernio as a custom MCP in Notis

Add an MCP server with these values:
  • Display Name: Zernio (or any name you’ll recognize)
  • Description: a few words on what it does. For example: “Schedules, publishes, and cross-posts social media content to connected accounts. Zernio handles LinkedIn, Twitter/X, Instagram, Facebook, TikTok, and other platforms.”
  • Server URL: https://mcp.zernio.com/sse
  • Authentication: Headers, with the name Authorization and the value Bearer YOUR_ZERNIO_API_KEY (your key from Step 1)

​
Step 3: Verify the connection

Zernio’s MCP server exposes 280+ tools generated from its OpenAPI specification. Useful first checks include listing connected accounts, reviewing available publishing actions, and confirming that the platforms you want to post to are already connected in Zernio. The Zernio docs show example MCP use cases such as:
  • Scheduling a LinkedIn post
  • Cross-posting content
  • Posting an image to Instagram
  • Showing connected accounts
  • Fetching inbox conversations
  • Working with ad campaigns
  • Building comment automations

​
Example workflow: let Notis create, let Zernio publish

A strong workflow is to use Notis for the creative and quality-control steps, then let Zernio execute the actual social publishing.
  1. Create the image in Notis — Have Notis generate the visual based on your campaign brief, audience, and brand voice.
  2. Validate the image in Notis — Ask Notis to check for quality, brand consistency, legibility, and platform fit.
  3. Draft and validate the caption in Notis — Have Notis write the caption, verify clarity and tone, and confirm hashtags, mentions, and CTA quality.
  4. Send the approved asset to Zernio MCP — Once the image and caption are approved, use Zernio’s publishing tools through MCP.
  5. Schedule the post with Zernio — Zernio handles the final scheduling or publishing action to the selected account.
  6. Let Zernio publish automatically — At the scheduled time, Zernio posts to the connected social platform.
This pattern works especially well when you want reliable approvals before anything goes live.

​
Example prompts

  • “Create a LinkedIn post image for our product launch, then review it for readability and brand fit.”
  • “Write three caption options for this post and validate which one is most aligned with our tone.”
  • “Once approved, use Zernio to schedule this post for next Tuesday at 9:00 AM on our LinkedIn company page.”
  • “Cross-post this campaign to LinkedIn and Instagram once the final caption is approved.”

​
Troubleshooting

  • Authentication fails: Confirm you pasted a valid Zernio API key and that Notis is sending it as a Bearer token.
  • No publishing actions appear: Verify the MCP server URL is exactly https://mcp.zernio.com/sse.
  • Posting fails: Confirm the destination social account is already connected inside Zernio.
  • You want more control over the creative review: Keep generation and validation steps inside Notis, and call Zernio only after approval.

​
Summary

Zernio gives you a hosted MCP endpoint that Notis can connect to with a Bearer-authenticated API key. That lets you use Notis to create and validate social content while Zernio handles the actual scheduling and publishing actions across your connected social channels.