ChatGPT MCP Server
Related Servers
Alternatives to ChatGPT MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI agents and IDEs to send prompts to an active ChatGPT web session and retrieve the completed response without needing an API key.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to check ChatGPT connection status, list live models, and run prompts using a ChatGPT Plus/Pro plan via OpenAI's official OAuth and Responses API.1Apache 2.0
- AlicenseAqualityAmaintenanceEnables MCP clients to drive ChatGPT's web interface through a built-in persistent browser, requiring only a single manual login. Prompts are sent through temporary incognito chats and the captured answer text is returned as tool results, along with live model listing, login/status probing, and optional HTTP transport.83Apache 2.0
- AlicenseAqualityBmaintenanceProvides access to OpenAI's ChatGPT API with web search capabilities for Claude and other MCP clients. Supports various GPT models with configurable parameters like reasoning effort, temperature, and streaming mode.118 npm3MIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients to ask plain-language questions and receive answers grounded only in documents the configured role is cleared to read, with the same access-controlled tools available across any client.-

apexapi-mcpofficial
AlicenseAqualityDmaintenanceEnables calling 120+ AI models and reading live web pages (scrape, crawl, structured extract) from any MCP client using one API key.960 npmMIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of confusing it with another. Its purpose (send a prompt to ChatGPT and return the answer plus sources) is unambiguous.
With a single tool there is no mixed convention to penalize. However, the name is an unwieldy prefixed, camelCase string (hasdata_chatgpt_chat_getChatgptAnswer) rather than a clean verb_noun pattern.
The narrow, single-endpoint domain means one tool covers the core capability without redundancy. Still, a one-tool surface is thin and leaves no room for related operations like continuing a conversation or fetching sources separately.
The tool covers a one-shot query with rich metadata, which fits the described use. But it explicitly has no memory, and there is no way to continue or manage a conversation, so multi-turn workflows are a notable gap.