ITQAN LAB

MIT · verified 2026-08-11

catalog / Productivity / skill

zernio-ops

Run several Zernio workspaces from one MCP server, so the agent can post, schedule and read analytics across every social account at once. Zernio ties each API key to one workspace, and an MCP entry sends one key, so a normal setup sees one workspace at a time. This plugin ships one MCP server that holds every key and sends each call to the workspace that owns the account. Keys stay in one local file and never pass through the conversation. Works on macOS, Windows and Linux.

version
1.0.0
updated
2026-11-13
works in
every conformant agent
needs
node
cost
free · uses your own account
license
MIT

Say this you do not type commands, you ask

  • “connect my Zernio”
  • “add a Zernio workspace”
  • “which Zernio accounts are connected”
  • “is my Zernio key working”
  • “post this through Zernio”
  • “set up the zernio hub”
  • “zernio”

Once it is installed, that is the whole interface. Your agent picks the skill up on its own and runs whatever it needs to. The commands further down are there for anyone who would rather drive it themselves.

Install pick your agent

Changelog what changed, newest first

1.0.0

Added

  • One MCP server, zernio, in front of every Zernio workspace. It exposes Zernio's tools once, adds an optional workspace argument to each, and finds the workspace from account_id when it is left out. accounts_list with no workspace lists them all.
  • The workspaces are the ZERNIO_KEY_<NAME> lines in the toolkit's credential store. There is no fixed count, and a name can be a letter or a word. A new workspace is one new line and a restart.
  • scripts/setup.mjs adds a key line for the person to fill in, checks each key against Zernio without printing it, and records the working workspaces in state/setup.json.

An agent that has this installed reads CHANGELOG.md in the skill folder. The same history is at changelog.json, and every tool's releases are at /updates.json.

Just ask

Once the plugin is installed, say what you want in your own words:

"connect my Zernio" "add a second Zernio workspace" "which accounts are connected?" "schedule this video on my TikTok for tomorrow at 6pm"

The agent sets up the keys and checks them. The one thing you do by hand is paste each API key into a file. That way the key never goes through a chat window.

Why one server

Zernio ties each API key to one workspace. An MCP entry sends one key, so it sees one workspace. With three workspaces you would need three MCP entries and three copies of every tool.

This plugin runs one server, zernio, that holds every key, however many there are. Each tool takes an optional workspace name, and a call with an account_id goes to the workspace that owns that account by itself.

Keys

One file, one line per workspace. The name after ZERNIO_KEY_ is yours to pick:

ZERNIO_KEY_A=...
ZERNIO_KEY_BRAND=...

The file is ~/.itqan-agent-toolkit/credentials/zernio.env, or under AGENT_TOOLKIT_HOME when that is set. It is the same credential store every toolkit skill uses.

node scripts/setup.mjs add brand   # adds an empty ZERNIO_KEY_BRAND= line for you to fill in
node scripts/setup.mjs status      # each workspace: does the key work, which accounts it sees

Restart the agent after adding a key. The server reads the file when it starts.

Without the plugin

Any MCP client can run the server directly:

claude mcp add zernio -s user -- node /path/to/zernio-ops/skills/zernio-ops/scripts/zernio-hub.mjs

Requirements

Node 18 or newer. sh scripts/setup-deps.sh checks for it and offers to install it.

Source on GitHub ↗

Itqan Lab

Built at Itqan Lab, a design and technology studio.

إتقان — itqan, the Arabic word for mastery: doing a thing precisely, and completely.

Open source under MIT · agent paths re-verified 2026-08-11 · this site is generated from the repository on every push.