Muse.ai
Ask Muse to build a secure RepoHop connector in its cloud VM.
Muse does not have a normal MCP settings screen. It can build and run a custom connector in its secure VM. This setup creates code in that VM. Review what Muse builds before you approve access.
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 build the connector
Send Muse this prompt:
Build a reusable RepoHop connector in your secure VM with an official MCP client SDK. Connect to https://repohop.app/api/mcp over Streamable HTTP. Follow the server's OAuth discovery and register the public client through the advertised registration_endpoint. Register exactly https://agent.meta.ai/api/hatch/oauth/callback as redirect_uri; do not use localhost or 127.0.0.1 because my browser cannot reach a loopback listener inside your VM. Then use Authorization Code with PKCE and refresh tokens. Do not reuse a hard-coded client_id such as local-agents and do not ask me to provide one. Pause so I can approve access in the browser. Store the client registration and tokens only in Muse's protected credential storage. Never print or save credentials in project files or logs. Request only projects:read and offline_access first. After connecting, list the available tools and verify the connection with project_catalog or project_status. Do not enable writes, command execution, commits or pushes until I ask.Muse should 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
- Take over the browser when Muse asks.
- Sign in to RepoHop.
- Check the client name and select the repository.
- Approve Read access only.
- 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
Turn on Write in both the repository and the RepoHop connection. Tell Muse to read each file before changing it. Review every change locally. Add Execute, Commit or Push only when the task needs it.
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.