Create with Grok Bot.
A documented custom MCP path, pending OpenGen-specific verification.
A few steps to get connected.
- Use the client’s custom MCP setup to add your configured gateway’s /mcp URL. The official guide also allows asking a Bot to add a server by URL.
- Review any configuration change, then use the client’s authentication card to sign in and choose the OpenGen workspace.
- Check tool discovery before generation. Installing an app and completing authorization are separate steps.
https://opengen.dev/mcpInstructions based on Grok Bot app documentation ↗, reviewed 2026-11-03. Client interfaces and permissions can change.
Prefer a shell workflow? Use OpenGen’s CLI and browser login →
If setup stops halfway
The browser sign-in is unavailable
Your deployment must have sign-in configured. Start at your workspace to check availability. Hosted assistants need a publicly reachable HTTPS endpoint; installing code inside their sandbox does not create a hosted connector.
I denied consent or chose the wrong workspace
Start connection again and review the paying workspace before approving. A key stays in its issued workspace. To change an agent’s workspace, revoke its old authorization and sign in again with the intended selection.
Local login expired or was interrupted
Run opengen doctor using the installed CLI. Sign in again when expired or revoked. A stale profile lock requires checking that no OpenGen process is active before removing it; never bypass token-reuse checks or share the profile.
I want to disconnect
Revoke the connected app in OpenGen’s workspace, then remove its client configuration. For OpenGen’s CLI, opengen logout revokes before deleting the private profile. If revocation fails, keep the profile and retry.