<!-- Generated by scripts/generate-llms.mjs from docs/clients/muse.md. Do not edit. -->

Source: https://qbash.com/docs/clients/muse

# How to add a custom connector to Muse and an MCP server to Muse Code

To add a custom connector to Muse, ask it in a chat to add the MCP server's URL, allow it, and choose **Connect** on the card it shows. Muse Code, the coding tool, reads MCP servers from `~/.config/muse/settings.json`.

:::note[Here from Google? Hi, we make the server in the screenshots]

- qbash runs Tasks, which are Python programs with AI steps, alongside your connected accounts and shared memory folders. Muse can call all of it as tools.
- You don't need qbash to follow this guide. Any remote MCP server goes in the same chat request.

[What the qbash server does](https://qbash.com/docs-markdown/mcp-servers/official-mcp-server.md)

:::

## Muse

1. Open a new Muse chat and ask: "Can you add this MCP server to your system for use: https://mcp.qbash.com/mcp".
2. Muse asks for permission to talk to the server. You can allow it once to test, or choose **Always allow**.
3. Muse lists the access it is requesting and shows a **Qbash** connector card. Choose **Connect**.
4. Sign in to qbash and pick the organization Muse should use.

Muse then reports that qbash is connected and lists its tools. Meta doesn't review custom connectors, and Muse keeps their credentials in its Secure Credentials Store. [Connect Muse to the qbash MCP server](https://qbash.com/blog/connect-muse-to-qbash-mcp-server) shows the flow on video.

Any Muse account can create a custom connector. Meta has no admin or business settings for it. Muse is offered in the US and Canada ([Meta help](https://www.meta.com/help/artificial-intelligence/1687253048996149/), [anythingmcp](https://anythingmcp.com/guides/clients/muse)).

## Muse Code

Add qbash to the `mcp_servers` block of `~/.config/muse/settings.json`:

```json
{
  "schema_version": 1,
  "mcp_servers": {
    "qbash": {
      "transport": "streamable_http",
      "url": "https://mcp.qbash.com/mcp"
    }
  }
}
```

If the file already exists, add only the `qbash` entry.

Then sign in:

```bash
muse mcp login qbash
```

Run `/mcp` in a Muse Code session to see qbash and its tools.

For an [access token](https://qbash.com/docs-markdown/mcp-servers/official-mcp-server.md#connect) in place of the sign-in, add a `headers` entry to the qbash server:

```json
"headers": {
  "Authorization": "Bearer ${QBASH_TOKEN}"
}
```

Muse Code fills in `${QBASH_TOKEN}` from the environment.

Muse Code needs a Muse Code subscription or an API key. Its managed configuration for enterprise administrators isn't documented as restricting MCP servers.

Meta's [Muse Code extending guide](https://dev.meta.ai/docs/muse-code/extending) covers the other options.