Grok Bot

Grok supports public custom MCP connectors. RepoHop is already public, so you do not need a tunneling service.

Before you connect

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

Add RepoHop

1. Open Grok Connectors.
2. Choose New Connector, then Custom.
3. Name it RepoHop.
4. Enter the RepoHop MCP URL:

https://repohop.app/api/mcp

Grok should discover OAuth and register itself automatically. Do not enter or invent a client_id; RepoHop does not issue users a shared static value.

5. Continue to RepoHop when the browser opens.
6. Check the client name, select the repository and approve Read access.
7. Open Grok Bot. Go to Settings → Plugins and make sure RepoHop is enabled.

For a managed team, an admin may need to add RepoHop under Grok Business → Connectors first. See Grok's connector guide.

Test the connection

Ask Grok Bot:

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 repository, branch and README match your local checkout.

Allow changes

Turn on Write in both the repository and the RepoHop connection. Ask Grok Bot to read a file before changing it. Review every change in your editor and with 'git diff'. Add Execute, Commit or Push only when the task needs it.

Remove RepoHop

Revoke the connection in RepoHop first. Then open Grok's connector settings and remove RepoHop. If a team admin added it, the admin controls whether it remains available to members.

If the plugin is missing, check your team's connector policy or ask an admin. For other problems, use Troubleshooting.