---
title: "Muse integration with Bolta"
description: "Connect Bolta to Muse Code, Meta's terminal agent, with a settings.json entry and muse mcp login. Drafts wait for your approval. Muse app and WhatsApp support is not confirmed."
canonical_url: "https://bolta.ai/integrations/muse"
markdown_url: "https://bolta.ai/integrations/muse.md"
last_updated: "2026-11-21"
content_type: "integration"
publisher: "Bolta"
---

# Muse integration with Bolta

Source: https://bolta.ai/integrations/muse
Last updated: 2026-11-21

Connect Bolta to Muse Code, Meta's terminal agent, with a settings.json entry and muse mcp login. Drafts wait for your approval. Muse app and WhatsApp support is not confirmed.

## Summary

Queue social posts from Muse Code, Meta's terminal agent

## Who this is for

- Developers
- Automation teams
- AI-assisted marketing teams

## Core capabilities

- Turn a release note or changelog entry into a LinkedIn or X draft without leaving the terminal
- Have Muse Code read a README or docs page in your repo and draft posts that explain it
- Draft a week of posts in your brand voice, then review them in Bolta rather than in the shell
- Ask what is waiting for approval and have each draft read back before you decide
- Pull recent post results into the terminal before you plan the next batch
- Set up a weekly routine that drafts posts for your review, then close the terminal

## Limitations and boundaries

- Confirmed in Meta's Muse Code docs: remote MCP servers over streamable\_http, an mcp\_servers block in ~/.config/muse/settings.json, and OAuth sign-in with muse mcp login.
- Not confirmed: that the Muse app (phone, desktop or WhatsApp) accepts a Bolta MCP link. Meta says the app has custom connectors, but we could not read the steps.
- Not tested end to end: nobody has run a full draft, review and schedule round trip through Muse Code with Bolta yet.
- Not confirmed: how to send an API key in the headers field, and whether the optional Bolta skill shows up in muse skills list.
- Integration availability depends on current APIs, authentication, scopes, and account permissions.
- Generated content can be incorrect and should be reviewed before publication.
- Availability depends on the current Bolta plan, connected network, account permissions, and integration coverage.
- Current prices and plan limits must be verified on the Bolta pricing page.

## Have a Bolta brand with an account connected

Create a Bolta account at bolta.ai and add at least one brand. Connect at least one social account to it, or Muse Code will only be able to draft.

## Install Muse Code

Run curl -fsSL https://dev.meta.ai/install.sh | bash, then muse --version to check it works. This is the terminal agent, not the Muse phone app.

## Open the settings file

Open ~/.config/muse/settings.json and create it if it is missing. It must contain "schema\_version": 1, or Muse Code stops at startup.

## Add the Bolta server

Add an mcp\_servers entry named bolta with transport streamable\_http and url https://mcp.bolta.ai/mcp. Keep any settings already in the file, then save it.

## Sign in to Bolta

Run muse mcp login bolta. A browser opens on bolta.ai. Sign in, tick the brands Muse Code may reach and approve. One connection covers one organization, and there is no key to copy.

## Check the connection

Start muse and type /mcp. You should see bolta listed with its tools. If it is missing, check the url, the transport value and the schema\_version line, then restart.

## Optional: add the Bolta skill

Run npx skills add boltaai/bolta-skills --skill bolta, then muse skills list. Muse Code reads ~/.agents/skills and ~/.claude/skills. If Bolta does not appear, skip it, because the connection works without it.

## Run a read-only check first

Ask: List my Bolta brands and the accounts connected to each. Do not change anything. Then ask for one draft and read the exact text back before you approve it in Bolta.

## The Muse Code settings block

Muse Code reads one JSON file. The Bolta entry sits next to anything already there, and the file must declare its schema version. Meta also lists optional enabled and mode fields (required or optional) for each server. We have not tested what changing them does with Bolta, so the guide leaves them out. Field: schema\_version; Value: 1; What it does: Required at the top of the file. Without it Muse Code stops at startup. | Field: mcp\_servers.bolta; Value: an object; What it does: The name you give the server. Use bolta. | Field: transport; Value: streamable\_http; What it does: Tells Muse Code this is a remote HTTP server. | Field: url; Value: https://mcp.bolta.ai/mcp; What it does: Bolta's hosted MCP address.

## Muse Code does not sandbox MCP tools

Meta's documentation says MCP tools in Muse Code are not sandboxed. A server you connect can do whatever its tools allow, so connect only servers you trust. Bolta narrows what it can do from its side. You tick which brands the connection reaches, your role in each brand still applies, and a post cannot be approved, scheduled or published until you say yes to that exact text. Pick only the brands you need on the permission screen. Ask for drafts only, and give your yes yourself in Bolta after reading the exact text. Read the draft text back before you say yes. A preview is not proof it went out.

## What we know about the Muse app

Meta says the Muse app works with custom connectors for services it does not list. The Help Center article that explains how could not be read, so we do not know whether the app takes a remote MCP URL, OAuth or a header. We have not confirmed that Muse can run Bolta from WhatsApp or the phone apps. Some third-party posts describe pasting a link into chat. That is not Meta's statement, so we do not repeat it here. Meta's launch articles name the United States and Canada for the app, with a later one adding Australia. Check Meta's pages for where you can use it today.

## Where Muse Code looks for skills

The connection gives Muse Code access to Bolta. A skill is optional guidance on using it well. Run npx skills add boltaai/bolta-skills --skill bolta and then muse skills list. We have not run this against Muse Code, so if Bolta does not appear, skip the skill and use the connection alone. ~/.agents/skills and ~/.config/muse/skills for your own machine. ~/.claude/skills, which Muse Code also looks in by default, so a skill you installed for Claude Code can be seen. .agents/skills or .claude/skills inside a repo, for project-level skills.

## Signing in on a machine without a browser

Meta's docs say you can sign in in the browser or headless but do not say how headless works. If no browser window opens, run muse mcp login bolta again, or try the Bearer key route, which is also unconfirmed. Meta lists a headers field for streamable\_http servers, and Bolta accepts a Bearer bolta\_sk\_ API key, so a header may work for a headless machine. We have not confirmed the exact format Muse Code expects, so check Meta's configuration page before you rely on it.

## muse mcp login, logout and the mode field

Sign-in has two commands you will use, and a third setting Meta documents that we have left alone. Meta also lists an OAuth dynamic client registration flag. Whether it works against Bolta's server has not been tested, so if login fails at that step, tell us. Item: muse mcp login bolta; What Meta documents: Signs a server in with OAuth 2.1; What we know with Bolta: Opens bolta.ai, where you tick brands and approve. One connection covers one organization. | Item: muse mcp logout bolta; What Meta documents: Signs the server out; What we know with Bolta: Use it before logging in again when Bolta says Invalid or expired. | Item: mode; What Meta documents: Each server can be required or optional; What we know with Bolta: Not tested. We do not know how a required server behaves when Bolta is unreachable. | Item: enabled; What Meta documents: Each server has an on or off flag; What we know with Bolta: Not tested. The guide leaves it out.

## When a terminal is the right place to queue posts

Muse Code suits people who already keep a repo open. The release notes, the docs and the commit history are one folder away, so a draft can start from the thing you just shipped instead of a blank box. It suits less well when the person approving is not technical. Reviewing happens in Bolta, so a marketer or client can read and approve there without opening a shell. Good: developer-led posts, launch notes, changelog threads, docs highlights. Good: asking what is in review and having it read back. Less good: image-heavy campaigns, where the work happens in Bolta's library and calendar.

## What to check on your own machine

Meta's pages describe the settings and sign-in. Nobody has run the whole loop with Bolta, so confirm each step yourself. /mcp lists bolta and its tools after muse starts. A read-only question about your brands answers with the brands you ticked and nothing else. A saved draft appears in Bolta's review queue with the text you saw in the terminal. A request to publish is refused or held until you give your yes.

## Is Muse the same as Muse Code?

No. Muse is Meta's personal agent app on phones, desktop and WhatsApp. Muse Code is a separate terminal agent with its own settings file. This page covers Muse Code, because that is where Meta documents remote MCP servers.

## Can I add Bolta in the Muse app or WhatsApp?

We have not confirmed it. Meta says the app has custom connectors, but we could not read the steps and found nothing showing that it takes a Bolta MCP link. Try the Muse Code path first.

## Does Muse need an API key for Bolta?

Not for the normal route. muse mcp login bolta signs you in through the browser and there is no key to copy. A Bearer bolta\_sk\_ key is an option for machines with no browser, but we have not confirmed the exact headers format in Muse Code.

## Can Muse publish without my approval?

No. Bolta will not approve, schedule or publish a post until you say yes to that exact text. It refuses the request or keeps the post in review, and your role and Safe Mode still apply.

## Is it safe to connect a server to Muse Code?

Meta's documentation says MCP tools in Muse Code are not sandboxed, so connect only servers you trust. Bolta limits the brands you tick, applies your role, and needs your yes before anything goes out.

## Which countries can use Muse?

We do not know the full list. Meta's September article names the United States and Canada for the Muse app, and a later one adds Australia. Which accounts and countries can use Muse Code is set by Meta, so check dev.meta.ai.

## Does the Bolta skill work in Muse Code?

It may. Meta documents ~/.agents/skills and ~/.claude/skills as skill folders for Muse Code. We have not checked where the skills command puts Bolta, so if muse skills list does not show Bolta, skip it. The connection works without a skill.

## What do I do if /mcp does not show bolta?

Check that the entry is inside mcp\_servers, that transport is streamable\_http, that the url is exactly https://mcp.bolta.ai/mcp and that schema\_version is 1. Then close Muse Code and start it again.

## How much does Muse cost?

We could not confirm Muse or Muse Code pricing, so we will not quote one. Bolta's own plans are on the pricing page. Check Meta for what you need on its side.

## Has this been tested end to end?

No. The settings format and sign-in command come from Meta's documentation, but nobody has run a full draft, review and schedule through Muse Code with Bolta. Claude Code and Codex have their own Bolta pages if you want another terminal agent.

## Can Muse Code keep posting after I close the terminal?

Muse Code itself does not, as far as we can tell. A routine you set up through it is stored in Bolta and repeats there, and it saves switched off until you say yes to turning it on.

## Which brands can Muse Code reach?

Only the ones you ticked on the Bolta permission screen during muse mcp login. If you need another brand, sign in again and tick it. Your role in each brand still decides what is allowed.

## Muse Code stops at startup with malformed settings file

The file must contain "schema\_version": 1 and be valid JSON, with commas between entries and none at the end. Fix that and start muse again.

## bolta is missing from /mcp

Check the entry sits inside mcp\_servers, the transport is streamable\_http and the url is https://mcp.bolta.ai/mcp. Close Muse Code and reopen it.

## muse mcp login bolta opens no browser

Close any stuck window and run muse mcp login bolta again. Over SSH or on a server there is nothing to open, so sign in on a machine with a browser or see the headless section above.

## Bolta answers Invalid or expired

The saved sign-in is out of date. Run muse mcp logout bolta, then muse mcp login bolta, and sign in once more.

## Bolta asks for a workspace\_id or answers about the wrong brand

You ticked more than one brand, so every request has to name one. Say which in plain words, for example for the Acme brand. If a brand is missing, sign in again and tick it.

## A request is refused or says approval is required

Bolta will not schedule or publish until you say yes to that exact post. Ask Muse to save a draft, then approve it. A 403 can also mean your role in that brand does not allow the action.

## Muse is not Muse Code

Muse is Meta's personal agent app on iOS, Android, desktop and WhatsApp. Muse Code is a separate terminal agent with a settings file and its own sign-in. This page and the Bolta guide cover Muse Code. For the other terminal agents, see Claude Code or Codex.

## Relevant links

- [Related page: /integrations](https://bolta.ai/integrations)
- [Related page: /integrations/claude-code](https://bolta.ai/integrations/claude-code)
- [Related page: /integrations/codex](https://bolta.ai/integrations/codex)
- [Related page: /integrations/cursor](https://bolta.ai/integrations/cursor)
- [Related page: /integrations/dots](https://bolta.ai/integrations/dots)
- [Related page: /integrations/cue](https://bolta.ai/integrations/cue)
- [Bolta pricing](https://bolta.ai/pricing)

## Supporting sources

- [Muse official website](https://dev.meta.ai/)
