Does Muse write the post, or Postemi?

Muse writes the copy in the coding session. Postemi schedules and handles it. Postemi has no AI writer, on purpose, so you use your own model.

Can I review the post before it is published?

Yes. Muse schedules the announcement, and you approve the copy, the platforms, and the time in the Postemi calendar before it goes out.

How does media get into the post?

You upload the media file with the posty upload command. The URL you get back goes into the -m value, right next to the -c content the media belongs to.

Can I use Postemi from a release script or CI?

Yes. posty posts:create runs from a release script and from CI, and POSTY_API_KEY can come from the environment. You install the CLI with npm install -g posty-cli; the command name is posty.

Which plans include MCP, the CLI and the REST API?

All three are available on the Pro, Creator and Team plans. Postemi handles 12 platforms, including Facebook, Instagram, TikTok, LinkedIn, X and YouTube.

Muse + Postemi: schedule social posts via MCP

First steps

The CLI in four commands

You install the CLI, sign in, fetch your integrations, then create a post. After that your release script can take over.

terminal

# Install the Postemi CLI package
$ npm install -g posty-cli
# Sign in to your Postemi account
$ posty auth:login
# Fetch your integrations
$ posty integrations:list
[{ "id": "cmf3k7…", "name": "Cafe · Instagram" }]
# Create and schedule the post
$ posty posts:create \
$   -c "New brunch menu this Saturday." \
$   -i "cmf3k7…" \
$   -s "2026-08-16 09:00" --timezone Europe/Budapest
✅ Post created successfully!
{ "id": "cmf7p2…", "state": "QUEUE" }

The CLI writes JSON to stdout, and status and errors to stderr. On failure it exits with a non-zero code.

A thread, in a single command

terminal

$ posty posts:create \
$   -c "We shipped 2.0. Three things changed. 1/3" \
$   -c "The calendar is faster. 2/3" \
$   -c "And there is a dark theme at last. 3/3" \
$   -d 5 \
$   -i "cmf3k7…" \
$   -s "2026-08-16T09:00:00+02:00"

Muse session

From code to a scheduled post

The announcement and the release are made in one place. You reach Postemi over MCP, the CLI, or the REST API.

Post from the session

Muse writes the announcement in the coding session, then schedules it through Postemi. The release and the post are made in one place.

Uploading media

You upload the media file first with the posty upload command. The URL you get back goes as the -m value after the post's -c flag.

A calendar you can read and rearrange

Muse reads the posts on the calendar, finds free slots, and rearranges the plan. That way it does not schedule the release post blindly.

CLI as another way

If you need a command instead of MCP, the published posty-cli reaches the same account. posty posts:create also runs from a release script and from CI.

Public REST API

The third way is the public REST API at api.posty.hu. You can reach the same Postemi account from your own integration or automation too.

Approval in the calendar

Muse writes and schedules the post, and you review it in the Postemi calendar. You can approve the copy and the time before it goes out.

How it connects

Four steps to Muse

You set up the accounts and the key. After that, Muse hands the scheduling to Postemi from the same session.

01

Connect your accounts

On the Postemi web app, you connect the social accounts you want to use through OAuth. You only have to do this once. After that, Muse can reach the Postemi integrations for those accounts.

OAuth on the Postemi web app

terminal

$ posty integrations:list
[
  { "id": "cmf3k7…", "name": "Cafe · Instagram" },
  { "id": "cmf3k9…", "name": "Cafe · Facebook" }
]

02

Create a key

Open Automations → Developers and create a key that starts with psty_mcp_…. You also get the full ready-made config block for Muse here.

Key and ready-made Muse block

.env

# Automations → Developers → New key
# We show the key once, when you create it.
 
# For the command line and the REST API:
POSTY_API_KEY=YOUR_API_KEY
 
# MCP clients get a separate key:
# psty_mcp_…

03

Hand it to Muse

Paste the Postemi block under the mcp_servers key in ~/.config/muse/settings.json, with streamable_http transport. Keep schema_version in the file: without it, Muse silently skips the file.

Required fields in settings.json

~/.config/muse/settings.json

{
  "schema_version": 1,
  "mcp_servers": {
    "posty": {
      "transport": "streamable_http",
      "url": "https://api.posty.hu/mcp/YOUR_API_KEY"
    }
  }
}

04

Review the schedule

Muse writes the announcement, and Postemi schedules it. Before it goes out, you review and approve the copy, the platforms, and the time in the Postemi calendar.

Review in the Postemi calendar

terminal

$ posty posts:list
[
  { "id": "cmf7p2…", "state": "QUEUE",
    "publishDate": "2026-08-16T07:00:00Z" },
  { "id": "cmf7q8…", "state": "DRAFT",
    "publishDate": "2026-08-18T06:30:00Z" }
]

In short

What is Muse?

Muse, full name Meta Muse Code, is a coding agent. You work with it in the same session where the code is written. It connects to Postemi as an MCP client, so you can write and schedule the release announcement in the same place.

You finish the release, then ask for the matching post in the same Muse session. Muse writes it, and Postemi schedules it. You do not have to switch tools, or start over in a separate UI.

Muse connects through its config file: the Postemi MCP block goes under mcp_servers, with streamable_http transport and the schema_version field. You get the ready-made block on the Automations → Developers page.

Writes next to the code

Muse writes the release post next to the code. The announcement is written in the same session as the release.

Connects over MCP

The Postemi MCP server receives the Muse request, then schedules the post to the given social account. The service URL is https://api.posty.hu/mcp.

Your own model writes

Muse writes the copy, not Postemi. Postemi has no built-in AI writer, on purpose, so you use your own model.

Built for agents

A predictable interface for Muse

Postemi responses and errors are easy to parse. You reach the same account three ways.

Machine-readable JSONCommand JSON output is easy to parse, so Muse does not have to pull data out of human-readable text.
Clear error signalsThe CLI writes status and errors to stderr, and on failure it exits with a non-zero code.
Built-in skill fileThe SKILL.md in the npm package teaches the agent how to use the CLI, with no extra training.
Flat command setA single flat command set handles posts, integrations, analytics, uploads, settings and login, with no hidden state.
Three ways inYou reach the same Postemi account over MCP, the published CLI, and the public REST API.

SKILL.md

---
name: posty
description: Posty schedules and publishes social posts
  from the command line.
homepage: https://posty.hu
---
 
# Output contract
 
Every command prints its JSON result, and nothing
else, to stdout; status lines, warnings and errors
go to stderr, and every failure exits 1.
 
# Two Hard Rules (Read First)
 
Rule 1: Authenticate before anything.
Rule 2: Every file passed to `-m` MUST first go
through `posty upload`.

SKILL.md is part of the npm package. The agent can read it directly and learn the Postemi CLI from it.

See how Postemi connects to the other agents, and pick the path that fits your workflow.

Hermes All AI integrations

Real commands

The full Postemi CLI

The posty commands cover posts, integrations, analytics, uploads, settings and auth. posty posts:create also runs from a release script or CI, if POSTY_API_KEY is in the environment.

Command

What it does

Posts

posty posts:createNew post: scheduled, as a draft, or published right away.

posty posts:listPosts in the given period. You can filter by client group too.

posty posts:delete <id>Delete a post by id.

posty posts:find-slot <id>The next free publishing time for a social account.

posty posts:status <id>Switch a post between draft and scheduled.

posty posts:missing <id>Content already on the platform for a post with a missing id.

posty posts:connect <id>Connect a post to content that is already published.

Social accounts

posty integrations:listConnected social accounts and their ids. This is what the -i flag needs.

posty integrations:groupsThe list of client groups, if you work with more than one brand.

posty integrations:settings <id>An account's settings schema, rules, length limit, and tools.

posty integrations:trigger <id> <method>Call a platform tool for extra data, for example to search for music.

Media and analytics

posty upload <file>Upload a media file. The URL you get back goes into the posts:create -m flag.

posty analytics:platform <id>A social account's stats going back the given number of days.

posty analytics:post <id>Performance of a single post.

Login and settings

posty auth:loginLog in with OAuth2 device authorization: the browser opens, you approve.

posty auth:logoutClear stored login data.

posty auth:statusShows whether you're logged in, and checks access too.

posty config:set <key> <value>Save a CLI setting, for example the default timezone.

posty config:get [key]Print the saved settings.

Flag

What it means

posts:create flags

-c, --contentThe post text. Repeat it to make a thread: the first is the post, the rest are comments.

-m, --mediaMedia for the -c that comes before it. The URL has to come from posty upload.

-i, --integrationsIds of the target social accounts, comma-separated.

--date, -sWhen to publish. Either with an explicit offset, or together with the --timezone flag.

--timezoneIANA timezone name, for example Europe/Budapest. Only pass a date with no offset together with this.

-t, --typeschedule (default), draft, or now.

-d, --delayDelay in MINUTES between items in the thread.

--jsonThe full post description from a JSON file, when the flags are not enough.

--settingsPlatform-specific settings as JSON. The schema comes from integrations:settings.

The CLI writes JSON to stdout, and status and errors to stderr. On failure it exits with a non-zero code.

Supported platforms

One account, every channel

Connect your accounts in a few clicks, then post to every channel from Postemi.

TikTok

Instagram

Facebook

Threads

LinkedIn

YouTube

X

Pinterest

beta

Bluesky

Google Business

coming soon

Discord

Telegram

Slack

…and more to come

Pricing

Fair pricing, no hidden costs

Every plan starts with a 7-day free trial. We bill in US dollars and issue a VAT invoice.

2 months free

Prices in US dollars. In Europe you pay the same amount in euros, in Switzerland in Swiss francs.

Basic

For solo creators new to scheduling

$13/mo

7-day free trial

$0 due today · Cancel anytime

5 social accounts
100 X posts a month
1 workspace
One user
Not included: Advanced image editor
Not included: Viral video + UGC templates
Not included: Automations
Not included: API access
Not included: Posting with an AI agent

Unlimited posts
Multiple accounts per platform
Scheduling
Calendar view
Repeated posts
Post delays
Studio access
Analytics (beta)
Post comments
Dark & light mode

Pro

Creator

For teams with several brands, plus image and video editors

$49/mo

7-day free trial

$0 due today · Cancel anytime

30 social accounts
400 X posts a month
5 workspaces
15 users
Advanced image editor
Viral video + UGC templates
Automations
API access
Posting with an AI agent

Unlimited posts
Multiple accounts per platform
Scheduling
Calendar view
Repeated posts
Post delays
Studio access
Analytics (beta)
Post comments
Dark & light mode

Team

Highest limits

For agencies managing many channels

$99/mo

7-day free trial

$0 due today · Cancel anytime

100 social accounts
800 X posts a month
Unlimited workspaces
Unlimited users
Advanced image editor
Viral video + UGC templates
Automations
API access
Posting with an AI agent

Unlimited posts
Multiple accounts per platform
Scheduling
Calendar view
Repeated posts
Post delays
Studio access
Analytics (beta)
Post comments
Dark & light mode

Post to

TikTok
Instagram
Facebook
Threads
LinkedIn
YouTube
X
Pinterest · beta
Bluesky
Google Business · coming soon
Discord
Telegram
Slack

FAQ

Common questions

Check that the Postemi block is under the mcp_servers key in ~/.config/muse/settings.json, and that transport is set to streamable_http. Keep the schema_version field too. Without it, Muse silently skips the file.

Muse schedules where the code is written

The CLI in four commands

A thread, in a single command

From code to a scheduled post

Post from the session

Uploading media

A calendar you can read and rearrange

CLI as another way

Public REST API

Approval in the calendar

Four steps to Muse

Connect your accounts

Create a key

Hand it to Muse

Review the schedule

What is Muse?

Writes next to the code

Connects over MCP

Your own model writes

A predictable interface for Muse

The full Postemi CLI

One account, every channel

TikTok

Instagram

Facebook

Threads

LinkedIn

YouTube

X

Pinterest

Bluesky

Google Business

Discord

Telegram

Slack

Fair pricing, no hidden costs

Basic

Pro

Creator

Team

Common questions

Why does Muse not see the Postemi MCP server?

Does Muse write the post, or Postemi?

Can I review the post before it is published?

How does media get into the post?

Can I use Postemi from a release script or CI?

Which plans include MCP, the CLI and the REST API?

Write it whereyou ship it.