Muse.ai

Muse does not have a normal MCP settings screen. It can run a custom connector in its secure VM using the official RepoHop MCP client template.

Before you connect

Make sure RepoHop Local is online and at least one repository is approved. Keep all permissions except Read turned off.

Ask Muse to connect

Send Muse this prompt:

Clone the official RepoHop MCP client repository and use it to connect:

git clone https://github.com/TheSethRose/RepoHop-MCP.git
cd RepoHop-MCP
bun install

Follow AGENTS.md in that repository to connect to https://repohop.app/api/mcp.

Register https://agent.meta.ai/api/hatch/oauth/callback as redirect_uri.

Pause when you need me to approve access in the browser.

Muse should clone the template, register the client, start the OAuth flow and stop when you need to approve access. RepoHop does not provide users with a shared static client ID.

Approve access

1. Take over the browser when Muse asks.
2. Sign in to RepoHop.
3. Check the client name and select the repository.
4. Select the capabilities this connection needs. Read is selected by default. Edit, Execute and Publish require explicit approval.
5. Return control to Muse.

Review the connector code. Confirm that it uses protected credential storage and does not write tokens to files or logs. See Meta's Muse security guide for details about its VM and credentials.

Test the connection

Ask Muse:

Use RepoHop to list my approved repositories. Run project_status for the repository I choose, then read its README with project_read. Do not change files or run commands.

Check that the result matches your local checkout.

Allow changes

First turn on the matching repository permission. Then reconnect Muse and select the matching capability on the RepoHop approval screen. Existing connections never gain a new scope automatically. Tell Muse to read each file before changing it and review every change locally.

Remove RepoHop

Revoke the connection in RepoHop. Then ask Muse to stop and remove the connector and delete its stored RepoHop credentials. Confirm that the connector no longer starts.

If the build or OAuth flow fails, ask Muse to report the exact error without printing credentials. Then use Troubleshooting.