Agent Web Search MCP Server

What this does

Agent Web Search exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

AGENT_WEB_SEARCH_PROVIDERS
ARK_API_KEY
GEMINI_API_KEY
XAI_API_KEY
DEEPSEEK_API_KEY
AGENT_WEB_SEARCH_RESPONSES_API_KEY
AGENT_WEB_SEARCH_RESPONSES_BASE_URL
AGENT_WEB_SEARCH_MESSAGES_API_KEY
AGENT_WEB_SEARCH_MESSAGES_BASE_URL
TAVILY_API_KEY
BRAVE_SEARCH_API_KEY
PERPLEXITY_API_KEY
YDC_API_KEY
EXA_API_KEY
PARALLEL_API_KEY
ZHIPU_WEB_SEARCH_API_KEY
ZHIPU_CHAT_SEARCH_API_KEY

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install Agent Web Search?

Run the Claude Code command in the install section to add Agent Web Search to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with Agent Web Search?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to Agent Web Search as well.

Does Agent Web Search need an API key?

Yes. Before it can run, set these environment variables: AGENT_WEB_SEARCH_PROVIDERS, ARK_API_KEY, GEMINI_API_KEY, XAI_API_KEY, DEEPSEEK_API_KEY, AGENT_WEB_SEARCH_RESPONSES_API_KEY, AGENT_WEB_SEARCH_RESPONSES_BASE_URL, AGENT_WEB_SEARCH_MESSAGES_API_KEY, AGENT_WEB_SEARCH_MESSAGES_BASE_URL, TAVILY_API_KEY, BRAVE_SEARCH_API_KEY, PERPLEXITY_API_KEY, YDC_API_KEY, EXA_API_KEY, PARALLEL_API_KEY, ZHIPU_WEB_SEARCH_API_KEY, ZHIPU_CHAT_SEARCH_API_KEY. They go in the env block of your MCP config.