Your tools.
A new creative outlet.
Find an image or video model, inspect its options and get a quote from the place you already work.
Hosted assistant
Add the gateway’s MCP address in your client. Sign in and choose the workspace that pays. There’s no local installer.
Local agent
Use the client’s MCP OAuth support, or OpenGen’s source CLI with browser login and a private local profile.
Your application
Create a separate expiring API key in your workspace. Keep its read/generate permissions limited to the job.
Reviewed 2026-11-03. OpenGen’s authorization and CLI have local protocol fixtures. Third-party client versions have not been verified end to end. Hosted sign-in and generation need a configured deployment; a guide is not a claim that the public service is ready.
See the support matrix ↓Where do you want to create?
Choose your setupChatGPT
Add a custom MCP plugin and authorize a paying workspace in your browser.
Client verification pendingClaude
Use a remote connector, with no local installer or provider credentials.
Client verification pendingClaude Code
Register an HTTP MCP server, then use the client’s browser authorization.
Client verification pendingCursor
Preview a URL-only MCP configuration and authorize through Cursor.
Client verification pendingCodex
Add a Streamable HTTP server and use OAuth login with read/generate scopes.
Client verification pendingOpenClaw
Use the client’s MCP settings and browser authorization; verify the connection separately.
Client verification pendingHermes Agent
Use the documented remote OAuth configuration and a browser sign-in.
Client verification pendingOpenCode
Configure a remote MCP server and complete the client’s OAuth flow.
Client verification pendingpi
Use the portable OpenGen CLI; native MCP is not assumed.
Client verification pendingGrok Bot
A documented custom MCP path, pending OpenGen-specific verification.
Client verification pendingCLI & API
Use the portable CLI with browser login, or create one scoped workspace API key.
Local protocol fixturesWhat has actually been checked?
Documentation reviewed 2026-11-03. “Protocol fixtures” means synthetic requests against local code, without a real client, identity provider or generation charge.
| Client | Setup path | Documentation | Tested client / version / date |
|---|---|---|---|
| ChatGPT | Hosted MCP with OAuth | Official OpenAI documentation ↗ | None recorded — unverified |
| Claude | Remote connector with OAuth | Claude custom connector guide ↗ | None recorded — unverified |
| Claude Code | Remote HTTP MCP or OpenGen CLI | Claude Code MCP documentation ↗ | None recorded — unverified |
| Cursor | Streamable HTTP MCP or OpenGen CLI | Cursor MCP documentation ↗ | None recorded — unverified |
| Codex | Native MCP OAuth or OpenGen CLI | Official OpenAI command reference ↗ | None recorded — unverified |
| OpenClaw | Streamable HTTP MCP or OpenGen CLI | OpenClaw MCP documentation ↗ | None recorded — unverified |
| Hermes Agent | HTTP MCP with OAuth or OpenGen CLI | Hermes MCP documentation ↗ | None recorded — unverified |
| OpenCode | Remote MCP OAuth or OpenGen CLI | OpenCode MCP documentation ↗ | None recorded — unverified |
| pi | CLI through the agent’s shell | pi project documentation ↗ | None recorded — unverified |
| Grok Bot | Custom remote MCP, unverified | Grok Bot app documentation ↗ | None recorded — unverified |
| CLI & API | OpenGen browser PKCE login / scoped API key | OpenGen CLI guide ↗ | Local fixtures only; deployed login unverified |
The OpenGen protocol fixtures cover PKCE/state, workspace consent, permission boundaries, token rotation/revocation and private profiles. They do not certify any third-party client. pi’s documented core has no native MCP; its CLI path is unverified.