Best for
- MCP clients and agents that need web search
- Developers who need to configure a search engine or provider endpoint
S
39FMRS · D
This server focuses on web search operations and supports stdio, SSE, and Streamable HTTP transports. The source does not list specific tool names or client compatibility.
mcp-server-search is an MCP server in the UI-TARS-desktop repository for web search operations. It supports selecting a search engine and configuring a search provider API key and base URL.
Setup
Use the npm package @agent-infra/mcp-server-search. The stdio transport supports the engine, api-key, and base-url arguments. SSE and Streamable HTTP transports can be run with npx and additionally require a port. The default engine is google and the default port is 8089.
Fit and risk
Not for
- Users needing browser clicks, form filling, or computer control
- Users looking for file, database, collaboration, or cloud-storage tools
Required permissions
- Access to the configured search provider
- A search provider API key when required
- A configured local port for SSE or Streamable HTTP modes
Risks and side effects
- Search results depend on the selected engine and provider
- API keys are sensitive configuration and should be protected
- An incorrect base URL, engine, or port can prevent the server from connecting
Troubleshooting
- Verify the default or selected engine configuration
- If the provider requires authentication, check that api-key is valid
- Verify that base-url points to the intended search provider
- For SSE or Streamable HTTP, confirm that port 8089 is available and use the corresponding /sse or /mcp path
Use cases
Performing web searches from an MCP client
Connecting a multimodal agent to a search provider