MCP integration

Transport

Node.js 22 or later runs tools/developer-platform/mcp/server.mjs. The adapter opens no inbound port. It reads live tools and schemas from the authenticated API, forwards each call and retains no process store.

Environment

Set FORGE_INSTANCE_URL to an approved HTTPS instance and FORGE_ACCESS_TOKEN in your private process environment. No token belongs in a prompt, AGENTS.md or Git. Local qualification alone permits explicit loopback HTTP.

Codex configuration

[mcp_servers.forge]
command = "node"
args = ["/absolute/path/to/forge/tools/developer-platform/mcp/server.mjs"]
env_vars = ["FORGE_INSTANCE_URL", "FORGE_ACCESS_TOKEN"]
startup_timeout_sec = 30
tool_timeout_sec = 30

Verify your connection

Set those two environment variables privately in the parent process, then run codex mcp list. This preview uses a pre-authorized token; codex mcp login is not implemented for the stdio adapter. Managed remote OAuth remains a security release gate. Use the sample AGENTS.md linked below; fetch the current catalog rather than copying stale block definitions.

Protocol and tools

Initialization, ping, tools/list and tools/call are supported; this preview does not implement MCP resources, prompts, remote OAuth login or a public Streamable HTTP listener. Tool definitions are version checked and include side-effect hints.

Agent safety

Read current context and capabilities before editing. Validate the final revision. Ask for the existing human review workflow when a capability is missing. Tool approval in an AI client does not replace FORGE authorization.