{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifrujwixia5oyyopweat7u7bj7zflef7gz63m3lsxfihxwrdansli",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mfvtvrpukif2"
  },
  "path": "/t/building-a-browser-to-codex-bridge-via-codex-mcp-server-tou-clarification-needed/1375345#post_1",
  "publishedAt": "2026-02-28T06:17:22.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "@modelcontextprotocol"
  ],
  "textContent": "Hi,\n\nI’m building an open-source developer tool called **spark-banana** (GitHub: nyosegawa/spark-banana) — a browser-based UI overlay for local development that lets you click an element in the browser, describe a fix, and route the task to Codex via its MCP server mode.\n\n**Architecture:**\n\nThe bridge server (`spark-bridge`) spawns `codex mcp-server` as a stdio child process and communicates with it via the official MCP SDK (`@modelcontextprotocol/sdk`), calling the `codex` tool through `client.callTool()`.\n\n\n    Browser (overlay) → spark-bridge (WS) → codex mcp-server (stdio/MCP) → Files updated\n\n\n\nKey details (see `packages/bridge/src/codex-mcp.ts`):\n\n  * `StdioClientTransport` with `command: 'codex', args: ['mcp-server']`\n\n  * `sandbox: 'workspace-write'`, `approval-policy: 'on-request'`\n\n  * Approval requests are forwarded to the browser UI (not auto-approved)\n\n  * Users authenticate Codex CLI themselves; spark-banana does not handle or redistribute any credentials\n\n\n\n\n**Question:**\n\nThe Terms of Use include:\n\n> You may not: “Automatically or programmatically extract data or Output.”\n\nAt the same time, the Codex documentation describes `codex mcp-server` as a supported way to “connect from any MCP client,” and `codex exec` is designed for scripted workflows.\n\nDoes the above clause apply to third-party tools that consume `codex mcp-server` on the user’s local machine using the official MCP SDK? To my knowledge there are no other third-party tools publicly doing this, so I’d appreciate any clarification before wider distribution.\n\nThanks!",
  "title": "Building a browser-to-Codex bridge via codex mcp-server — ToU clarification needed"
}