Agent setup
Connect your agent
Forge works with the agent you already use. Add the remote Forge address https://forge-base.com/mcp in the product’s connector, plugin or MCP settings, then sign in on Forge’s own approval page. The agent acts with your Forge permissions.
Choose every surface first
List where you need to work: web or cloud, desktop app, phone, CLI or IDE. Prefer an account-level remote connection where it covers those surfaces. A local MCP configuration is different: it configures that client even when it points at a remote address. It does not prove independent cloud or phone access.
For every selected surface, confirm the right Forge account and workspace, Forge tools available, a harmless read, and a reversible write only where permitted. Read the result back elsewhere. Provider documentation is not a completed Forge device test.
ChatGPT Chat and Work
Forge is a custom remote MCP app, so set it up in ChatGPT on the web. First enable Developer mode if your plan and workspace policy permit it. OpenAI currently documents creating the app through Settings or Workspace settings → Apps → Create; enter Forge’s remote address, complete the Forge sign-in when prompted, scan the tools, then create the app. The newer Plugins connection guide documents an alternative flow: Settings → Security and login → Developer mode, then ChatGPT Plugins → + and the remote URL. Follow the route shown by your ChatGPT account rather than assuming both are available.
Custom MCP apps are web only. Do not treat a Forge connection in ChatGPT Chat or Work as desktop or mobile access. OpenAI’s Developer mode guide says full MCP, including write and modify actions, is beta for Business, Enterprise and Edu; Pro can connect a custom MCP in Developer mode with read and fetch permissions only. Business, Enterprise and Edu workspaces can also require an administrator or owner to enable Developer mode, create, approve or publish the app. Run the harmless read check below after setup and treat write access as unconfirmed until your actual plan and workspace allow it.
Codex desktop
Codex desktop is a separate product surface. Add Forge through its supported local MCP settings and complete Forge authentication. OpenAI documents that this local configuration can be shared with supported Codex CLI and IDE surfaces; verify Forge tools on each. It does not prove ChatGPT Chat, Work or mobile access.
Codex CLI and IDE
Codex CLI and the IDE extension use the same local configuration family as desktop where supported. OpenAI’s MCP guide describes that sharing, but the IDE has no ChatGPT plugin surface. Do not describe this as independent cloud or phone access.
Claude Chat and Desktop
Use Customize → Connectors to add Forge’s remote custom connector and authenticate. Anthropic documents this on Free (one custom connector), Pro, Max, Team and Enterprise; Team and Enterprise can require owner setup. The connection is cloud-brokered even when used from Desktop. Check Anthropic’s setup guide.
Claude Cowork
Claude Cowork uses Anthropic’s cloud-brokered remote connector path. Connect once through the supported flow, then verify the selected Cowork surface can read your Forge workspace. Anthropic’s surface guide lists remote connector availability across supported web, mobile, Cowork, Desktop and Claude Code surfaces; Forge use still needs the selected-surface check.
Claude Code
Claude Code can use the remote connector where the product supports it. Verify tools and workspace access in the actual Code environment; its local configuration and a Claude Chat connector are separate unless the provider shows the same account connection.
Grok Chat
Set up custom MCP at grok.com/connectors, then add Forge and authenticate. xAI documents web setup and Business/Enterprise provisioning. Grok mobile apps exist, but Forge custom-connector availability on mobile is unverified until a device test.
Grok Bot
Grok Bot is a separate product context. Do not assume a Chat connector applies to it. Use Grok Chat on the documented web route as the supported alternative until a product-specific Forge test exists.
Cursor
In Cursor, add Forge at Customize → MCPs, or use the documented local .cursor/mcp.json or ~/.cursor/mcp.json route. Cursor CLI can share the editor configuration and supports its own MCP login. A managed team can instead provision a Team MCP Server for the Agent Window, IDE and CLI. These are local or managed-client routes, not proof of phone or PWA access; no Cursor mobile Forge route is verified here.
Other MCP
Use a client with OAuth-capable remote MCP support. Add https://forge-base.com/mcp, sign in, then run the check below. If the client only has local configuration, set it up on each required client.
Check each selected surface
Do these checks in every browser, desktop app, phone, CLI or IDE you selected:
- Complete the sign-in or local configuration.
- Confirm the expected account and workspace are visible.
- Confirm Forge tools are available in that surface.
- Do one safe read of a task you can access.
- Make one permitted reversible test write there, then read the result back there and on each other selected surface. If you only have read access, stop after the read check.
Check it worked
List the Forge workspaces I can access. Do not change anything.