OpenAI Agents API Adds MCP Test Path for Drupal Agent Access

OpenAI's new Agents API gives Drupal's experimental external-agent stack another MCP client environment to test against. Released in public beta on 10 September 2026, the API supports connections to HTTP MCP servers and allows credentials to be supplied with those connections. Drupal's Agent Access project, whose first alpha release followed on 8 September 2026, is designed to let compatible external clients discover and invoke selected Drupal capabilities under the connected person's existing permissions. No published end-to-end test reviewed for this story confirms that OpenAI Agents API and Drupal Agent Access are working together.

OpenAI describes the Agents API as a managed agent harness based on the infrastructure behind Codex, with context management, tool use, long-running sessions and subagent coordination. Its MCP documentation allows an HTTP MCP server to be added directly to an agent's tools. The connection can originate from OpenAI's service or the agent's execution environment, and HTTP connections can include an authorization value such as a bearer token or additional headers.

Drupal's Agent Access project provides the server-side counterpart for testing that connection model. Part of the Drupal AI Initiative's Outside AI work, its experimental implementation brings together Tool API, MCP Server, Simple OAuth and related MCP authentication and tool-bridge components. Drupal says compatible external interfaces should be able to discover its capabilities without requiring a separate Drupal-specific client integration, while requests continue to run under the connected person's permissions, access rules, validation and workflows.

The current implementation remains deliberately limited. Agent Access 1.0.0-alpha1 is experimental and is not covered by Drupal's security advisory policy, while parts of its dependency stack remain at alpha or beta maturity. Drupal's project documentation describes the starter capability set as narrowly scoped and says Agent Access does not yet make every Drupal action available externally or establish production readiness.

OpenAI and Drupal therefore document the two sides of a plausible interoperability test rather than a completed integration. An OpenAI agent can be configured to reach an HTTP MCP server and present an authorization credential, while Drupal's MCP stack can expose selected tools over HTTP and apply bearer-token and Drupal permission checks. Testing the two together would still need to establish connection setup, authentication, tool discovery, permission handling, calls, results and failure behaviour before the relationship could be described as a working integration.

The broader Drupal relevance is portability rather than an OpenAI-specific connector. Agent Access is intended to expose governed Drupal capabilities through shared interfaces that compatible outside tools can use without Drupal rebuilding the same client integration for each platform. OpenAI's Agents API adds another documented MCP environment for testing that approach, but the current evidence supports protocol-level alignment and an interoperability opportunity rather than production OpenAI support for Drupal.