chatgpt
Allows the MCP agent to interact with the ChatGPT desktop application using the signed-in account, enabling prompted queries, management of conversational history, and real-time web searches via the integrated Codex CLI.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@chatgpt ask ChatGPT to explain the latest AI news with web search"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ChatGPT MCP (Windows)
Windows port of syedazharmbnr1/claude-chatgpt-mcp. The original drives the macOS ChatGPT app with AppleScript (keystrokes + clipboard). This version instead runs the Codex CLI that ships inside the ChatGPT desktop app, signed in with your ChatGPT plan, so it:
costs nothing beyond your ChatGPT plan (no API key, no API billing; uses plan usage limits)
runs in the background: no window focus, no keystrokes, no clipboard
keeps follow-ups in one conversation via
conversation_id
Tool
chatgpt with operation:
ask:prompt(required), optionalconversation_id,web_search(bool),model,reasoning_effort(low|medium|high|xhigh),images(file paths),timeout_secondsget_conversations: conversations started through this tool (data/conversations.json)
Related MCP server: Codex MCP Server
Safety
Codex runs with --ignore-user-config, a read-only sandbox, in the empty folder data/workspace,
and with these features off: ChatGPT connected apps (Outlook, Teams, GitHub, Drive...), plugins,
computer use, browser, shell, sub-agents, hooks, image generation. Code-mode is only on when
web_search is true (it is what runs web search). ChatGPT therefore cannot read your files or act
in other apps; paste any text it needs into the prompt.
Install
Requires Windows 11, Node.js 18+, and the ChatGPT desktop app signed in with your ChatGPT plan.
git clone https://github.com/1502OB/chatgpt-mcp-win11.git
cd chatgpt-mcp-win11
npm install
claude mcp add --scope user chatgpt -- node "$PWD\index.mjs"Setup / maintenance
Needs the ChatGPT desktop app (package
OpenAI.Codex) signed in; check withcodex.exe login status(the exe path is found automatically after app updates).Override with env vars:
CODEX_PATH,CHATGPT_MODEL(defaultgpt-6.2-sol),CHATGPT_REASONING_EFFORT(defaultmedium),CHATGPT_TIMEOUT_SECONDS(default 600).Test:
npm testConversation index and the empty Codex workspace live in
data/(override withCHATGPT_MCP_DATA).Remove:
claude mcp remove chatgpt -s user
Available Tools
1 toolchatgptA
Ask ChatGPT a question (runs in the background through the Codex CLI signed in with the user's ChatGPT plan; no API cost, does not touch the screen). Operations: 'ask' sends a prompt and returns ChatGPT's reply plus a conversation_id you can pass back to continue the same conversation; 'get_conversations' lists conversations started through this tool. ChatGPT here has no access to files, email, or other apps; include any text it needs in the prompt.
Inputs: operation (required), model, images, prompt, +4 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool there is no cross-tool ambiguity, so selection is trivial. The only friction is that 'ask' and 'get_conversations' are two distinct operations multiplexed behind a single tool name via an operations parameter, which the description does explain.
A single tool cannot be internally inconsistent, so there is no convention clash. However, the name 'chatgpt' is a product/service noun rather than a verb_noun action name like 'ask_chatgpt' or 'list_conversations', so it does not establish a predictable pattern.
One tool is borderline thin; splitting 'ask' and 'get_conversations' into two tools would be more discoverable. The narrow purpose (relaying a prompt to ChatGPT) does justify a minimal surface, so it is not a severe mismatch.
The stated purpose — ask ChatGPT and continue a conversation — is covered via prompt/response plus conversation_id, and listing conversations exists. Minor gaps remain (no delete/rename conversation, no model or parameter selection), but these are workaroundable or out of scope.
Maintenance
Related MCP Connectors
Use your Mac, Windows or Linux computer from ChatGPT, Claude or Codex: files, commands, documents.
Your AI apps as one team: hand work to Codex or Claude Code on your Mac, with a shared logbook.
Connect AI assistants to your approved computer for files, commands, browser and desktop tasks.
Shared memory and context across ChatGPT, Claude, Claude Code, Codex, Cursor and 20+ AI tools
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables AI coding assistants to interact with OpenAI's Codex AI through the official CLI. Provides direct integration for code analysis, file review, and batch processing with zero API costs.3120MIT
- AlicenseCqualityDmaintenanceConnects AI assistants like Claude to the Codex CLI for code analysis, editing, and execution. Supports file references with @ syntax, sandboxed code execution with approval workflows, and structured code changes for automated refactoring and documentation.8131 npm176MIT
- AlicenseAqualityBmaintenanceEnables any LLM to drive your local Codex CLI in a sandboxed workspace, running coding tasks and generating images without needing an API key.4MIT
- AlicenseNot gradedqualityAmaintenanceEnables web-based AI chat clients such as Claude, ChatGPT, and Grok to read, edit, and run things on your own machine — files, shell commands, search, Git, SQLite, browser automation, DevTools, background tasks, localhost APIs, clipboard, and Postman — through a single OAuth-gated endpoint. Access is governed by a strict command whitelist and folder-scoped permissions rather than unrestricted shell access.MIT