Connect an agent

RepoHop is a remote MCP server. It lets an agent work with repositories you approved through RepoHop Local. Your repository stays in its current folder on your computer.

Every agent uses this public endpoint:

https://repohop.app/api/mcp

RepoHop supports OAuth client discovery and dynamic registration. Compatible agents register themselves from the advertised registration_endpoint. RepoHop does not give users a shared static client_id; if an agent asks you for one, update its connector or follow the client-specific guide instead of inventing a value.

RepoHop Local must stay online while an agent works. You do not need to open a local port or create another tunnel.

Set up RepoHop first

1. Install and pair RepoHop Local.
2. Approve at least one repository.
3. Keep Write, Execute, Commit and Push off until the read-only test works.

Choose your agent

• Grok Bot: Add RepoHop as a custom connector and enable its plugin.
• Muse.ai: Ask Muse to build an OAuth-capable MCP connector in its secure VM.
• Vellum: Add and authenticate RepoHop with Vellum's MCP commands.
• Gemini Spark: Add RepoHop as a custom Connected App.
• Letta: Add RepoHop through a host application that manages OAuth.

Each guide covers setup, approval, a read-only test, added permissions and removal.

How access works

You approve each connection in RepoHop. Select only the repositories and permissions that agent needs. A connection cannot see repositories you did not select.

Start with Read. Add Write, Execute, Commit or Push only when a task needs them. Execute runs commands as the local user who runs RepoHop Local. Push allows fast-forward pushes only.

You can stop access at any time from Connections → Revoke. For an immediate local stop, run:

repohop freeze

If setup fails, use Troubleshooting.