Muse Code

Muse Code is Meta’s coding agent for the terminal and CI, built on Muse Spark. Add PostQueen to its settings file and Muse Code can list your channels, draft and schedule posts from your repo, and report how published posts did.

Before you start

Plans: pay as you go per token, or the Everyday, High and Power subscriptions. You need a Meta account, and availability varies by region.
Platforms: the terminal and CI on macOS, Linux and Windows.
A PostQueen API key. A workspace admin copies it, or the ready-made address, from Connections.

Where the API key is: in the app, open Connections > API Keys. Only a workspace Admin or Super Admin can reveal or rotate it; other members see it masked. A workspace has one key, and each agent card on Connections shows your MCP address with the key already filled in.

Connect Muse Code

Muse Code has no mcp add command. You add PostQueen by editing its settings file.

Open the settings file

Open ~/.config/muse/settings.json, or create it.

Add PostQueen

Add the postqueen entry under mcp_servers, with your key in place of YOUR_API_KEY. Keep "schema_version": 1 at the top of the file.

~/.config/muse/settings.json

{
  "schema_version": 1,
  "mcp_servers": {
    "postqueen": {
      "transport": "streamable_http",
      "url": "https://api.postqueen.ai/mcp/YOUR_API_KEY",
      "mode": "optional"
    }
  }
}

Restart Muse Code

Restart Muse Code, then type /mcp to see the PostQueen tools.

Check that it works

Ask Muse Code: “List my PostQueen channels.” It answers with the channels you connected in PostQueen. If /mcp does not list PostQueen, check the settings file against the example above.

Good to know

"schema_version": 1 is required. Without it every command fails with a malformed settings file error.
Keep "mode": "optional". Servers are required by default, and a required server that fails stops the run.
The file holds your key when you use the key address. Keep it private, or use the header form below.
Ask for drafts when you want to check first. A draft waits on your PostQueen calendar, and nothing publishes until you schedule it.
What it cannot do over MCP: delete a post, or change a post’s text or time. Do that on the calendar in the app. The MCP tools lists what it can do.

Other ways to connect

Way	Address	Status
The key in the address	`https://api.postqueen.ai/mcp/YOUR_API_KEY`	From Meta’s docs. The route above
The Bearer header	`https://api.postqueen.ai/mcp`	From Meta’s docs
Sign in with PostQueen	`https://api.postqueen.ai/mcp-oauth-dynamic`	Not tested yet

Bearer header
Sign in (not tested yet)

~/.config/muse/settings.json

{
  "schema_version": 1,
  "mcp_servers": {
    "postqueen": {
      "transport": "streamable_http",
      "url": "https://api.postqueen.ai/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" },
      "mode": "optional"
    }
  }
}

Set "url" to https://api.postqueen.ai/mcp-oauth-dynamic with no headers, then run:

muse mcp login postqueen

Muse Code registers itself and opens the PostQueen sign-in, which a workspace admin approves. The sign-in address has 20 tools, all but ask_postqueen. Revoke access in PostQueen under Connections > Approved Apps.

Try this first

Read the last five commits and write a short Bluesky post about what changed. Save it in PostQueen as a draft for tomorrow at 10am.

The draft appears on your PostQueen calendar, ready for you to check and schedule. Prompts to try has more.

Troubleshooting

Symptom	Fix
Every command fails with a malformed settings file error	Add `"schema_version": 1` at the top of `settings.json`.
A run stops when PostQueen cannot be reached	Set `"mode": "optional"` on the `postqueen` entry.
`/mcp` does not list PostQueen	Restart Muse Code after saving, and check the JSON is valid.
The key is refused	Copy it again from Connections > API Keys. Only a workspace Admin or Super Admin can reveal it.

More fixes are on Troubleshooting agents.

Is it the same as Muse?

No. Meta ships two agents with the Muse name, and they connect to PostQueen in different ways:

Product	What it is	How it connects
Muse Code (this page)	Meta’s coding agent for the terminal and CI	PostQueen’s MCP address in its settings file
Muse	Meta’s personal agent in the Muse app, on muse.ai and in WhatsApp	Not by address yet

Next steps

Every agent

Which agents can post to PostQueen, how each one connects, and what PostQueen has tested.

The MCP tools

What each of the 21 tools does, and what an agent cannot do.

Prompts and tool calls

The order an agent calls the tools in, with prompts that work.

Troubleshooting agents

What to do when a connection or a command fails.

Start here

Assistants and bots

Coding agents

Editors and more

MCP reference

CLI reference

Troubleshooting

Before you start

Connect Muse Code

Check that it works

Good to know

Other ways to connect

Try this first

Troubleshooting

Is it the same as Muse?

Next steps

Every agent

The MCP tools

Prompts and tool calls

Troubleshooting agents

​Before you start

​Connect Muse Code

​Check that it works

​Good to know

​Other ways to connect

​Try this first

​Troubleshooting

​Is it the same as Muse?

​Next steps

Every agent

The MCP tools

Prompts and tool calls

Troubleshooting agents

Before you start

Connect Muse Code

Check that it works

Good to know

Other ways to connect

Try this first

Troubleshooting

Is it the same as Muse?

Next steps