OpenAI
OpenAI releases the Agents API in public beta on September 10, 2026, with built-in MCP server connections
OpenAI's API changelog recorded the Agents API entering public beta on September 10, 2026, describing a managed Codex harness that lets a developer "connect your own tools and MCP servers." The Agents API overview confirms agents can operate in a sandbox that connects to MCP servers, and the linked MCP connections guide documents three ways to attach a server: over HTTP hosted by OpenAI, over HTTP from the developer's own environment, or over stdio inside that environment. This is a separate product surface from the Agents SDK, which OpenAI added MCP support to in March 2025.
OpenAI's API changelog recorded the Agents API entering public beta on September 10, 2026: "Released the Agents API in public beta. Build agents with a managed Codex harness while OpenAI handles session orchestration, context compaction, and recovery. Use durable sessions to continue work across turns, stream progress, and connect your own tools and MCP servers." That is a distinct product from the Agents SDK, the surface OpenAI adopted MCP into in March 2025; the Agents API is a newer, separate offering built around a managed Codex harness rather than the earlier SDK.
The Agents API overview guide describes the same capability in more
detail: "Agents can operate in a sandbox where they can execute code,
edit files, connect to MCP servers, and produce artifacts." Its code
sample attaches a server as a tool of type mcp, naming it with a
server_label field and pointing a transport of type http at a
server_url, in the example https://developers.openai.com/mcp.
The linked MCP connections guide documents three ways to attach a
server to agent.tools. An HTTP server with connection_origin set to
"service" is reached directly by OpenAI and needs no session
environment. An HTTP server with connection_origin set to
"environment" is reached from the developer's own session
environment instead, for servers on a private network. A server can
also be started over stdio as a process inside that same session
environment. The guide notes that omitting connection_origin
defaults an HTTP connection to running through OpenAI.
Related publishers
How was this verified, and what are the sources?
Published · last verified · confidence 1.00.
- OpenAI API changelog, entry dated Sep 10 - "Released the Agents API in public beta. Build agents with a managed Codex harness while OpenAI handles session orchestration, context compaction, and recovery. Use durable sessions to continue work across turns, stream progress, and connect your own tools and MCP servers." - accessed
- Agents API overview guide - "Agents can operate in a sandbox where they can execute code, edit files, connect to MCP servers, and produce artifacts"; code sample shows a tool of type "mcp" with server_label "openai_docs" and a transport of type "http" pointed at https://developers.openai.com/mcp - accessed
- "MCP connections" guide, linked from the overview's Tools and integrations navigation - documents three connection modes: HTTP with connection_origin "service" (runs at OpenAI, no environment required), HTTP with connection_origin "environment" (runs in the developer's own session environment), and stdio (a process started inside that environment) - accessed