Skip to content

Integrations

Connect a GGX instance to Codex, Claude Code, Gemini CLI, OpenCode, VS Code, or Zed through the Model Context Protocol (MCP).

Connect your AI coding client to GGX through the Model Context Protocol (MCP). The client can then use your GGX permissions to find platform objects, consult GGX documentation, author assets, run agents, and start simulations.

You need a GGX account and an instance URL that your coding client can reach. The MCP endpoint is your GGX instance URL followed by /mcp.

https://YOUR-GGX-INSTANCE/mcp

When you first use the server, your client opens a browser window so you can sign in to GGX and approve access. The server only exposes data and actions that your GGX account is authorized to use.

Add GGX from the project where you use Codex:

Terminal window
codex mcp add ggx --url https://YOUR-GGX-INSTANCE/mcp

If the browser sign-in flow does not open automatically, run codex mcp login ggx. Confirm the server is available with codex mcp list.

The Codex CLI and IDE extension share this MCP configuration.

After connecting, ask your client a read-only question first:

List the GGX projects and agents I can access.

For guidance on GGX concepts or configuration, ask the client to search GGX documentation before making changes. Before any authoring action, it should inspect the object schema and current object details. Review any proposed create, update, delete, agent-run, or simulation action before you approve it.

  • Verify that the endpoint ends in /mcp and that the client can reach your GGX instance over the network.
  • Complete the browser sign-in with the GGX account that has access to the target instance.
  • Check the client’s MCP status view or command: codex mcp list, claude mcp list, gemini mcp list, opencode mcp list, MCP: List Servers in VS Code, or the MCP Servers settings page in Zed.
  • If you use a self-hosted GGX instance behind a proxy, allow the client to reach the instance and preserve the OAuth redirect flow.