OpenGen
LOCAL AGENT

Create with OpenCode.

Configure a remote MCP server and complete the client’s OAuth flow.

Open your workspace ↗Create in browser →
Remote MCP OAuth or OpenGen CLI

A few steps to get connected.

  1. Review a change to opencode.json. Merge the remote entry below into your existing mcp object.
  2. Run opencode mcp auth opengen to open authorization in your browser.
  3. Use opencode mcp list to inspect auth status and test discovery before any paid request.
Endpoint format · use your configured gateway
https://opengen.dev/mcp
Entry to merge into your existing settings
{
  "mcp": {
    "opengen": {
      "type": "remote",
      "url": "https://opengen.dev/mcp"
    }
  }
}

Instructions based on OpenCode MCP documentation ↗, reviewed 2026-11-03. Client interfaces and permissions can change.

Prefer a shell workflow? Use OpenGen’s CLI and browser login →

YOU CHOOSE THE WORKSPACE

Review consent

Check the app name, callback destination, permissions and paying workspace. Read allows discovery; generate permits billable jobs within your workspace’s rules. Denying consent grants no access.

Start with discovery

Ask for catalog search, inspect a model and request a quote. Check availability and the spending ceiling before generation. Your new personal workspace starts with zero managed credit.

Stay in control

Manage connected apps and revoke their authorizations in your workspace. Keep API keys separate for each application. Signing out of the website does not revoke an agent’s grant.

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.