KreatorMesh

KreatorMesh Agent Mode

Give your AI agent the ability to draft, check and schedule social posts — and, more usefully, to find out what has actually worked on your audience before it writes anything.

Supports: TikTok, Instagram, YouTube, X (Twitter), LinkedIn, Facebook, Threads, Pinterest, Bluesky, Google Business Profile.

Built on KreatorMesh.

Two skills, and one of them is free

The first is free and standalone on purpose. Most hook advice is an average taken across audiences that are not yours, and the fix is measurement rather than better advice. That skill explains how to do it by hand. It is genuinely useful without paying anyone.

Install

As skills (Claude Code, Cursor, Windsurf, Codex and others)

npx skills add orkuma-alex/kreatormesh-agent-mode

Install just one:

npx skills add orkuma-alex/kreatormesh-agent-mode --skill hook-testing-method

As an agent plugin

The repo root is a portable Agent Plugin (spec 1.0.0): plugin.json + mcp.json + skills/. Claude Code additionally reads .claude-plugin/. Both layouts sit side by side, so the same repo works either way.

CLI only

npx kreatormesh-cli setup --key km_live_...

npx kreatormesh-cli accounts

Node 18+. No dependencies.

Connecting

You need a KreatorMesh account on the Creator plan or above. The MCP server is https://api.kreatormesh.com/api/mcp. There are two ways to sign in to it.

Connect (OAuth) — for Claude, ChatGPT and other apps with a connector screen. Add a custom connector with the URL above and click Connect. You are sent to a KreatorMesh page that names the app and what it will be able to do; click Allow. No key to copy. Disconnect it any time under Connected apps on https://kreatormesh.com/api-keys.

• claude.ai / Claude Desktop: Settings → Connectors → Add custom connector.
• Claude Code: claude mcp add --transport http kreatormesh https://api.kreatormesh.com/api/mcp, then run /mcp and choose KreatorMesh to sign in.

API key — for scripts, CI and clients without a sign-in flow. Create one at https://kreatormesh.com/api-keys (shown once) and send it as Authorization: Bearer km_live_…, or set KREATORMESH_API_KEY and use the bundled mcp.json.

CLI — npx kreatormesh-cli setup --key km_live_..., or set KREATORMESH_API_KEY in the environment (preferred in CI and agent sandboxes, since it leaves nothing on disk).

Tools

The ordering is the point. check_draft between writing and scheduling is what makes this different from a cross-poster: it tells you which of your *measured* rules a draft breaks, and by how much.

Known limits, stated up front

• Media is attached by URL. schedule_post takes public https links to images or video, and the platform fetches them when the post publishes, so the link must still work then. Instagram, TikTok, YouTube and Pinterest need at least one; X, LinkedIn, Facebook, Threads, Bluesky and Google Business accept text alone.
• Captions are checked against each platform's limit (X 280, Bluesky 300, Threads and Pinterest 500, Instagram and TikTok 2,200 and so on) when they are saved, and refused if too long rather than cut short.
• `update_post` edits instead of cancel-and-recreate. Only what you pass changes. It refuses a failed post, because some platforms may have published it and re-sending could post twice.
• `cancel_post` only stops posts that have not gone out. A published post is already live on the platform; deleting KreatorMesh's record would not take it down, so the tool refuses and says so.
• `check_draft` returns nothing until a hook test has completed in the app. An empty result means "no rules learned yet", not "the draft is fine". The free hook-testing-method skill explains the method meanwhile.
• Hook tests need a platform that reports views: X, YouTube, Instagram, Facebook, Threads, Pinterest and TikTok. Bluesky and LinkedIn report likes and comments only, so tests are refused there.
• API keys cannot manage API keys. Listing, creating and revoking need a signed-in session, so a leaked key cannot mint more or revoke the one you are using to investigate it.
• A key acts as its owner. Anything these tools can do, that person could do.

Security

Keys are stored hashed server-side — the plaintext is shown once and cannot be retrieved, so a lost key is replaced rather than recovered. Revoke at https://kreatormesh.com/api-keys; revocation takes effect on the next request.

The CLI saves a key to ~/.kreatormesh/config.json with owner-only permissions where the platform supports it. KREATORMESH_API_KEY takes precedence and writes nothing to disk.

Registry listing

server.json is the official MCP Registry entry; see PUBLISHING.md.

Licence

MIT. See LICENSE.