---
title: "OpenAI Responses API mcp tool — MCP compatibility"
description: "A bearer-token relay rather than an OAuth client, and the one client here that accepts the legacy HTTP+SSE transport without calling it deprecated."
canonicalUrl: "https://zuplo.com/learn/mcp/compatibility/clients/openai-responses-api"
pageType: "mcp-client"
kind: "API"
verified: "2026-07-31"
---

# OpenAI Responses API mcp tool

> A bearer-token relay rather than an OAuth client, and the one client here that accepts the legacy HTTP+SSE transport without calling it deprecated.

_API. Protocol revision: Not published._

## Support

- **stdio** — No
- **Streamable HTTP** — Yes
- **Legacy HTTP+SSE** — Yes
- **Protocol revision** — Not published
- **Runs the OAuth flow** — No
- **Registration (RFC 7591)** — No
- **Metadata document** — No
- **Pre-registered client ID** — No
- **Sends resource (RFC 8707)** — No
- **Validates iss (RFC 9207)** — No
- **Custom headers** — No

**Protocol revision.** Not published. The guide states the accepted transports rather than a revision.

## Caveats and sources

Each one names the column it qualifies and cites the page it comes from, which is often not the page in the row's primary source.

### Runs the OAuth flow

You pass an OAuth access token in the `authorization` field, and registration and authorization are your application's job. The value isn't persisted either: you send it on every Responses API request.

[Source](https://developers.openai.com/api/docs/guides/tools-connectors-mcp)

### stdio

Local servers reach it through a tunnel identifier rather than a subprocess.

[Source](https://developers.openai.com/api/docs/guides/tools-connectors-mcp)

[Primary source](https://developers.openai.com/api/docs/guides/tools-connectors-mcp)

_This row was last verified 2026-07-31 against the 2026-07-28 revision._

- **Clients** — [every client in the matrix](/learn/mcp/compatibility/clients)