web-gpt
Related Servers
Alternatives to web-gpt
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables Codex to delegate deep research, PRD drafting, design thinking, and current-information lookups to ChatGPT Web/App via a local MCP connector, saving Markdown results to the filesystem.MIT
- AlicenseNot gradedqualityAmaintenanceLocal macOS MCP bridge that gives ChatGPT shell, unrestricted filesystem access, real PTY sessions, background jobs, and read-only stored Codex history. ChatGPT stays the reasoning layer; the bridge makes no model calls.51MIT
- AlicenseNot gradedqualityAmaintenanceEnables ChatGPT to read local project facts and manage Codex Desktop tasks through the official Secure MCP Tunnel.11MIT
- AlicenseNot gradedqualityAmaintenanceEnables local code execution via Codex (Luna) through MCP, using ChatGPT Web conversations as a planner. Provides file, terminal, and code execution tools while keeping long-running jobs manageable.17MIT
- AlicenseNot gradedqualityDmaintenanceLocal MCP bridge enabling ChatGPT web to access approved local files and execute tasks via local Codex.11MIT
- AlicenseNot gradedqualityAmaintenanceEnables ChatGPT to securely inspect local Codex projects, read session history, and dispatch confirmed tasks to the Codex CLI through a local MCP bridge.Apache 2.0
TDQS
Scored across 2 tools
ask_chatgpt sends tasks and awaits responses, while read_chatgpt only restores and reads previous chats without sending. Their purposes are distinct and unlikely to be confused.
Both tools follow a consistent verb_chatgpt snake_case pattern: ask_chatgpt and read_chatgpt. The naming convention is predictable and clear.
With only 2 tools, the surface feels thin even though both tools are clearly useful. The server covers a narrow scope, but the count is at the low end of the acceptable range.
The core workflow of sending a task and reading a previous chat is well covered. Minor gaps exist, such as no explicit delete or list-chats operation, but agents can work around them using session_id handling.