MCP server — About two minutes to connect (3)

OpenAI API The Responses API takes a remote MCP server as a tool, and forwards your headers on every call: { "type": "mcp", "server_label": "rowfold", "server_url": "https://www.rowfold.com/mcp", "headers": { "Authorization": "Bearer rfmcp_…" }, "require_approval": "never" } Send the header with every request: OpenAI deliberately does not store header values, so there is nothing to configure once and forget. Consider leaving require_approval at its default on a write-enabled key. Sign in instead of pasting a key Some clients take no key at all. ChatGPT's custom connectors accept OAuth or no authentication — their setup UI has no field for a bearer token or a custom header — so /mcp speaks OAuth 2.1 as well. Point such a client at https://www.rowfold.com/mcp with no credential. It discovers the sign-in flow from the 401, sends you to RowFold to sign in and pick a workspace, and comes back holding a token of its own.