OpenGHz

Responses Web Search — Development skill for Claude Code

Development community

Local stdio MCP server: web search for Claude Code via the OpenAI Responses API web_search tool, for relays where the built-in WebSearch returns nothing.

How to install Responses Web Search

This entry records only its repository, not the path inside it, so there is no exact command to give. Open OpenGHz/responses-web-search and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Responses Web Search does

Local stdio MCP server: web search for Claude Code via the OpenAI Responses API web_search tool, for relays where the built-in WebSearch returns nothing.

Alternatives in Development

Speech — Generate spoken audio from text using OpenAI's API with built-in voices 14.6k ★
Google Ads Meta Ads MCP — Google Ads MCP server + Meta Ads MCP (Facebook Ads MCP) + GA4 + Search Console in one hosted remote MCP for Cl 3.2k ★
Obsidian MCP Server — Read, write, search, and surgically edit Obsidian vault notes, tags, and frontmatter via MCP 686 ★

README

responses-web-search: web search for Claude Code over the Responses API

English | [简体中文](README.zh-CN.md)

A local stdio MCP server that gives Claude Code a `web_search` tool. It runs real searches through the built-in `web_search` tool of the OpenAI Responses API on your relay, and returns the answer, cited links, every source consulted, and the search record.

**When to use it:** you run Claude Code through a third-party relay (`ANTHROPIC_BASE_URL`). On many relays Claude's own search doesn't work: the built-in WebSearch silently returns empty results, and Claude, taking that as "nothing found", keeps retrying with reworded queries. If the same relay also serves OpenAI's `/v1/responses`, its web_search runs real searches with a GPT model (default `gpt-6.1-sol`). The split: Claude decides when to search and reads the results; the search itself and the summary in `answer` are done by GPT.

Files

File	Purpose
`server.py`	The MCP server; Python standard library only
`helper.py`	Install and verify subcommands, one per step below; none of them prints the token
`TROUBLESHOOTING.md`	Look here when a step FAILs (简体中文)

Install

This section is written for an agent to execute: tell Claude Code to "set this up following README.md".

**Rules:**

Tokens live only where Claude Code and Codex keep them: the env block of ~/.claude/settings.json (or the environment variable of the same name) and ~/.codex/auth.json. When reading those files, look at key names only and mask every value. Keep the token out of code, config, command lines and logs; helper.py already masks it.
Back up before changing config. register and deny-websearch back up automatically and print the backup path; note it and include it in the final report.
Run the steps in order. Move on only once the current step meets its completion criterion.

**Prerequisites:**