codex-web-search-mcp
Related Servers
Alternatives to codex-web-search-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server that bridges OpenAI's Agents SDK with Claude Code, enabling web search, file search, and computer use capabilities directly in your development environment.29 npm1MIT
- AlicenseNot gradedqualityAmaintenanceA dual-transport MCP server enabling anonymous free web search via Parallel (default) or Exa (backup), with no API keys or DSH dependency, for Claude Code, Codex, and any MCP client.81 npm8MIT
- AlicenseAqualityBmaintenanceEnables plain-language web search with automatic source and time-window selection, returning relevance-ranked links and summaries to MCP clients such as Claude Code and Codex. Works as an MCP server, CLI, and Claude Code plugin with zero runtime dependencies.16MIT
- AlicenseAqualityAmaintenanceMCP server that wraps Codex CLI as a subprocess, exposing code execution, web search, and structured output as Model Context Protocol tools.867 npm3MIT
- AlicenseAqualityDmaintenanceA zero-dependency MCP server that enables searching and reading local Claude Code and Codex chat sessions, supporting full-text search, grep, and knowledge indexing from chat history.1513 npmMIT
- FlicenseAqualityCmaintenanceAn MCP server that brings Parallel web search and URL extraction to Codex and other Model Context Protocol clients.220 npm-
TDQS
Scored across 2 tools
Each tool has a clear, distinct role: one performs a single web search, the other executes iterative multi-step research. Despite both involving search, the workflow difference is explicitly described, making selection unambiguous.
Both tool names follow the same pattern: codex_ + web_ + action verb (search/research). The naming is consistent and predictable.
With only two tools, the server feels thin even though the domain is narrow. The two tools cover both quick and deep research, but the count is at the borderline for minimal acceptable scope.
The tool set covers single searches and complex research workflows including opening, finding within, and clicking links. Minor gaps exist (e.g., no explicit session management), but the surface is adequate for the stated purpose.