# Connect Muse > What Meta documents about connecting Muse to an outside service, what that means for Anectico, and how to use the Muse Code terminal agent. Canonical page: https://anectico.com/docs/agents/connect-muse/ **Implemented from the vendor's documentation dated 2026-10-09. Not yet verified with a real Muse account.** Meta's pages show no absolute date (the connector page says it was updated "4 weeks ago"); 9 October 2026 is the day we read them. This guide is shorter than the others because Meta's pages say less. The record for every host is on [MCP client compatibility](/docs/reference/mcp-compatibility). ## What Meta documents - You can ask Muse to create a **custom connector**. Meta says Muse "will guide you through the process, which can involve retrieving API information from the service", and keeps the credentials in its Secure Credentials Store. - Meta says it does not review custom connectors or how they use your information. - Meta's pages that we read **do not mention MCP servers** for the Muse app. They do not say where a remote server address is entered, which sign-in method Muse uses to register, or what its limits are. - Meta's security description says Muse blocks a public-looking name that resolves to private infrastructure, so a server has to be on the public internet. Guides written by other companies describe a path: **Settings**, **Connectors**, **Add custom connector**, paste the server address, then sign in through a window. Those guides also say Muse is offered only in the United States and Canada today. We could not confirm any of this in Meta's own pages, so we cannot say it works. ## If your Muse offers a remote server address Use these values. They are the same for every host: - Server address: `https://app.anectico.com/mcp` - Sign-in: OAuth. Anectico supports public clients with PKCE, dynamic registration and client metadata documents. Sign in, choose the workspace, uncheck any permission the agent does not need and approve. - The connection is **read-only**. Anectico never offers a write permission through sign-in. A key with write permissions is the only way to change anything, and nothing says Muse accepts one. If Muse asks for an API key header instead, create a key with the narrowest read permissions the job needs and send it as `Authorization: Bearer `. See [Scope recipes](/docs/agents/scope-recipes). If you ask Muse to build the connector itself, give it the address above and tell it to use only the tools from `tools/list`. Muse writes such a connector for one person, and Meta does not check it. ## Muse Code, the terminal agent Muse Code is a separate product from the Muse app, and Meta documents it. **Anectico's support for Muse Code is written from Meta's documentation of 10 October 2026. It has not been tested on a real Muse Code install.** The record is on [MCP client compatibility](/docs/reference/mcp-compatibility). Read it before you rely on this. Connect it with one command. `--dry-run` first shows you the exact change and makes none: ```bash anectico agent bootstrap --project --host muse --dry-run anectico agent bootstrap --project --host muse ``` The command writes one file, `~/.config/muse/settings.json`. Meta documents no other file for servers, so there is no project scope. Meta says this file must contain `"schema_version": 1`. A new file gets that line. If your file has another version, has no version, or is not valid JSON, the command stops and leaves it exactly as it is. If your file has other servers or settings, they are not changed, and a copy of the file is kept beside it as `settings.json.anectico-backup`. ```json { "schema_version": 1, "mcp_servers": { "anectico": { "transport": "streamable_http", "url": "https://app.anectico.com/mcp", "headers": { "Authorization": "Bearer ${ANECTICO_API_KEY}" }, "mode": "optional" } } } ``` - `${ANECTICO_API_KEY}` is filled by Muse Code from the shell that starts it. The key is never written into the file. Set the variable first: `eval "$(anectico agent key env --export)"`. Meta does not say what Muse Code does when the variable is not set. - `"mode": "optional"` means that if Anectico cannot be reached, Muse Code skips the server and shows a warning. Without it, Meta says a server that fails to start stops the whole run. - To sign in with a browser instead of using a key, run the command with `--auth oauth`, then run `muse mcp login anectico`. Meta says Muse Code registers itself automatically and can be told not to with `"mcp_oauth_dynamic_client_registration": false`. This connection is for read work only. - Meta says a tool that its server marks read-only runs without an approval prompt in the on-request mode. Every Anectico read tool is marked read-only. Meta also says MCP tools are not sandboxed, so connect only servers you trust. - The skills go to `~/.agents/skills`, a folder Meta lists for Muse Code. Codex reads the same folder. To check it, start `muse` from the shell where the variable is set and run `/mcp`. The `anectico` server and its tools should be listed. `anectico agent doctor --host muse` checks the file, the address and the key. It cannot start Muse Code, so it always lists what it did not check. To take the entry out, run `anectico agent remove --host muse --yes`. That leaves your other settings, your key and your skills alone. ## Limits - **Muse Code is not tested on a real install.** Nothing here has been seen working inside it. Meta's pages do not say whether `${ANECTICO_API_KEY}` is filled inside `headers`, what happens when the variable is not set, whether `XDG_CONFIG_HOME` moves the settings file, where the file is on Windows, or whether it may contain comments. The command uses the documented file and assumes no comments. - **Read-only through sign-in.** See above. - **Nothing is published** about tool counts, schema rules or the addresses Muse calls from. - **Meta's connector directory** is a separate, reviewed list. Meta's guidelines ask for each tool to be classed as Read, Write or Sensitive write, and a tool that mixes reads and writes counts as a write. We have not submitted Anectico there. ## If it does not connect | What you see | What to do | | --- | --- | | Muse cannot reach the address | The address must be public HTTPS and end in `/mcp`. Open it in a private window: you should get a `401`. | | Muse has no place to enter a server address | That is what Meta's own pages suggest for the app. Use Muse Code, or another host in [Connect an AI agent with MCP](/docs/agents/connect-mcp). | | Sign-in opens but the connection fails | Tell us the time and what Muse showed. | | `WORKSPACE_NOT_READY` on the first question | Your first workspace is still being prepared. Wait a second and ask again. | To stop Muse's access, revoke the connection under **Agents and keys** in the Console, or run `anectico auth connections revoke`. See [Revoke an agent's access](/docs/agents/revoke-agent-access).