Skip to main content
Glama

codex-chatgpt-web-mcp

한국어 | English

Use your authenticated ChatGPT Web account as an external reasoning, coding, and review backend for Codex.

Codex keeps ownership of the repository, shell, Git, tests, and patch application. ChatGPT sees only the prompts and files Codex explicitly sends.

Install with Codex

Copy this prompt into a local Codex session:

Install codex-chatgpt-web-mcp on this machine.

Repository:
https://github.com/jiho-symply/codex-chatgpt-web-mcp

Use the normal-user install flow, not the development/source-build flow.
Do not modify files in my current project.

1. Check that Node.js >= 20 and a supported Edge/Chrome/Chromium browser are available.
2. Run:
   npx -y codex-chatgpt-web-mcp@latest login
   If ChatGPT login, CAPTCHA, or 2FA needs human interaction, stop and ask me to complete it in the opened browser.
3. Register the MCP server with:
   codex mcp add chatgpt-web -- npx -y codex-chatgpt-web-mcp@latest mcp
4. Verify registration with:
   codex mcp list
5. Do not clone/build the repository unless the documented npx path actually fails.
6. If the current Codex session cannot see the newly added MCP server, tell me to restart Codex.

If anything fails, show me the exact failing command and error instead of guessing.

Codex can perform the installation itself if it has local shell permission. You only need to handle interactive ChatGPT login/2FA/CAPTCHA, and possibly restart Codex once after registration.

Related MCP server: MCP-LinkGPT

Manual install

Requirements: Node.js 20+ and a local browser.

  • Windows: Microsoft Edge or Google Chrome

  • Linux: Google Chrome or Chromium

# One-time ChatGPT login
npx -y codex-chatgpt-web-mcp@latest login

# Register CGW with Codex
codex mcp add chatgpt-web -- npx -y codex-chatgpt-web-mcp@latest mcp

Verify with:

codex mcp list

Codex CLI, the ChatGPT/Codex desktop app, and Codex IDE integrations on the same host share the same MCP configuration. UI-only setup and platform details are in docs/installation.md.

Use cases

  • Second-opinion coding/review — send a diff, implementation, or test result to ChatGPT while Codex remains the orchestrator.

  • Long reasoning — delegate a difficult analysis and recover the same turn without resending the prompt after timeouts.

  • File/document analysis — explicitly attach source, logs, PDF, Office documents, CSV/JSON/YAML, screenshots, and images.

  • Structured outputs — receive code blocks, tables, citations, generated files/images, and other response parts as a structured manifest.

  • Workspace-isolated context — each local workspace can use its own CGW-... ChatGPT Project created with Project-only memory.

How it works

Codex ── MCP / stdio ──▶ CGW ── browser ──▶ ChatGPT Web
  │                                          │
  ├─ repo / shell / Git / tests              └─ explicit prompt/files only
  └─ validates and applies results

Key behavior:

  • one persistent authenticated browser profile, stored outside repositories;

  • Windows and Linux system-browser auto-detection;

  • CGW- prefix for newly created workspace Projects;

  • explicit input staging — no arbitrary workspace file reader;

  • async send → wait → get_reply flow with idempotent request IDs;

  • structured response extraction for text/code/files/images/tables/citations;

  • generated assets are staged privately before Codex decides what to do with them;

  • no shell, Git, patch-apply, arbitrary URL navigation, cookie export, CAPTCHA bypass, or stealth capability is exposed to ChatGPT.

Documentation

Detailed documentation is kept out of this README:

Notes

  • This is ChatGPT Web browser automation, not the official ChatGPT API.

  • Initial ChatGPT login is intentionally interactive.

  • ChatGPT Web UI changes can break selectors; ambiguous UI states fail closed.

  • Content explicitly uploaded through CGW is sent to the user's ChatGPT account and is subject to ChatGPT retention/settings.

  • ChatGPT output is untrusted; Codex should validate code and files before use.

License

MIT

Available Tools

3 tools
chatgpt_capabilitiesChatGPT Web capabilitiesA
Read-only

Inspect live model and reasoning/effort choices visible to the signed-in ChatGPT account. The web UI is the source of truth; no model list is hard-coded.

Inputs: no named parameters. Returns: modelPicker, effortPicker, flattenedPicker

chatgpt_chatChatGPT Web chatB

Send prompt text to ChatGPT Web and return the assistant response. No repository or execution capability is granted to ChatGPT. The caller is responsible for selecting minimal context and validating returned code before use.

Inputs: prompt (required), model, effort, timeout_ms, +1 more. Returns: response, truncated, responseBytes, conversationId, +2 more

chatgpt_statusChatGPT Web statusA
Read-only

Check whether the persistent ChatGPT Web session is authenticated and usable. Does not expose cookies, tokens, profile files, or workspace data.

Inputs: no named parameters. Returns: uiReady, headless, authenticated, conversationId

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: status checks authentication, capabilities inspects model options, and chat sends messages. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tools follow a consistent 'chatgpt_' prefix with clear noun suffixes (status, capabilities, chat), forming a predictable and uniform naming convention.

    Tool Count5/5

    With only 3 tools, the server is tightly scoped to its purpose of interacting with ChatGPT Web, and each tool is essential for the core workflow. This is well within the typical range.

    Completeness5/5

    The tool surface covers the essential operations: session validation, capability discovery, and message exchange. No critical gaps are apparent for the stated purpose.

    Related MCP Connectors

    Related MCP Servers