openai-search-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Debug mode | false |
| FETCH_ENGINE | No | Default fetch engine when fetch_engine is not passed | llm |
| OPENAI_MODEL | No | Model identifier | gpt-4o |
| OPENAI_API_KEY | Yes | API key for your endpoint | |
| OPENAI_API_URL | Yes | OpenAI-compatible API endpoint (must support search) | |
| TAVILY_API_KEY | No | Tavily API key (for web_fetch with fetch_engine=tavily) | |
| TAVILY_API_URL | No | Tavily API base URL | https://api.tavily.com |
| OPENAI_LOG_LEVEL | No | Log level | INFO |
| FIRECRAWL_API_KEY | No | Firecrawl API key (when using firecrawl as default or per call) | |
| FIRECRAWL_API_URL | No | Firecrawl API base URL | https://api.firecrawl.dev/v2 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchA | Performs a third-party web search based on the given query and returns the results as a JSON string. The The The ReturnsA JSON-encoded string representing a list of search results. Each result includes at least:
|
| web_fetchA | Fetches and extracts the complete content from a specified URL and returns it as a structured Markdown document. The
ReturnsA Markdown-formatted string containing:
Notes
|
| get_config_infoA | Returns the current OpenAI Search MCP server configuration information and tests the connection. This tool is useful for:
ReturnsA JSON-encoded string containing configuration details:
Notes
|
| switch_modelA | Switches the default AI model used for search and fetch operations, and persists the setting. This tool is useful for:
Parametersmodel : str The model ID to switch to (e.g., "gpt-4o", "gpt-4o-mini") ReturnsA JSON-encoded string containing:
Notes
|
| toggle_builtin_toolsA | Toggle Claude Code's built-in WebSearch and WebFetch tools on/off. Parameters: action - "on" (block built-in), "off" (allow built-in), "status" (check) Returns: JSON with current status and deny list |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool serves a clearly distinct purpose: searching the web, fetching page content, toggling built-in tools, retrieving configuration, and switching models. There is no functional overlap or ambiguity between them.
All tool names follow a consistent snake_case verb_object pattern (e.g., web_search, get_config_info, switch_model). No mixed conventions or unpredictable naming styles.
With 5 tools, the server is well-scoped for its purpose of providing web search/fetch plus configuration management. Each tool is necessary and earns its place without excessive redundancy.
The tool set covers the essential operations: searching, fetching content, inspecting configuration, switching models, and managing built-in tool integration. There are no obvious missing capabilities for this domain.