Integrations
Connect GGX with MCP
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.
Before you begin
Section titled “Before you begin”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/mcpWhen 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.
Connect your client
Section titled “Connect your client”Add GGX from the project where you use Codex:
codex mcp add ggx --url https://YOUR-GGX-INSTANCE/mcpIf 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.
Choose where to save the server configuration:
claude mcp add --transport http ggx https://YOUR-GGX-INSTANCE/mcpclaude mcp add --transport http --scope user ggx https://YOUR-GGX-INSTANCE/mcpRun claude mcp list to verify the server. In Claude Code, run /mcp and complete the browser sign-in if prompted.
Choose where to save the server configuration:
gemini mcp add --transport http ggx https://YOUR-GGX-INSTANCE/mcpgemini mcp add --scope user --transport http ggx https://YOUR-GGX-INSTANCE/mcpRun gemini mcp list to verify the server. If sign-in is required, open Gemini CLI and run /mcp auth ggx.
Choose where to save the server configuration:
opencode mcp add ggx --url https://YOUR-GGX-INSTANCE/mcpopencode mcp add ggx --global --url https://YOUR-GGX-INSTANCE/mcpRun opencode mcp auth ggx to complete sign-in, then confirm the connection with opencode mcp list. You can also manage the server from the /mcps view.
Open the Command Palette and run MCP: Add Server. Choose HTTP, enter https://YOUR-GGX-INSTANCE/mcp, name the server ggx, and select either workspace or user-profile storage.
Create .vscode/mcp.json in the project root:
{ "servers": { "ggx": { "type": "http", "url": "https://YOUR-GGX-INSTANCE/mcp" } }}Open Copilot Chat in Agent mode and enable GGX in the tools picker. Complete the GGX browser sign-in when prompted. Use MCP: List Servers to check the connection or view its output log.
Open Settings → AI → MCP Servers, select Add Server, then select Add Remote Server. Name the server ggx and enter https://YOUR-GGX-INSTANCE/mcp.
Add the GGX server to your Zed settings file:
{ "context_servers": { "ggx": { "url": "https://YOUR-GGX-INSTANCE/mcp" } }}Complete the GGX browser sign-in when Zed prompts you. Return to Settings → AI → MCP Servers and confirm that GGX has a green active status, then enable its tools in an Agent Panel thread.
Verify the connection
Section titled “Verify the connection”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.
Troubleshooting
Section titled “Troubleshooting”- Verify that the endpoint ends in
/mcpand 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.