Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Agent Web Search

by JerryLiu369version 0.8.1i★ –iRuns on your computer
Registry nameio.github.JerryLiu369/agent-web-search

Install

Overview

Description from the maker (original English)

Provider-neutral web_search for AI agents. Grounding + agent search APIs, keyless defaults.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Search & AI memory
  • You need to fill in: ARK_API_KEY, GEMINI_API_KEY, XAI_API_KEY, DEEPSEEK_API_KEY, AGENT_WEB_SEARCH_RESPONSES_API_KEY, AGENT_WEB_SEARCH_MESSAGES_API_KEY, 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

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: 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

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • PyPIPython’s uv installed (for the uvx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "agent-web-search": {
      "command": "uvx",
      "args": [
        "agent-web-search-mcp"
      ],
      "env": {
        "AGENT_WEB_SEARCH_PROVIDERS": "your-value",
        "ARK_API_KEY": "your-value",
        "GEMINI_API_KEY": "your-value",
        "XAI_API_KEY": "your-value",
        "DEEPSEEK_API_KEY": "your-value",
        "AGENT_WEB_SEARCH_RESPONSES_API_KEY": "your-value",
        "AGENT_WEB_SEARCH_RESPONSES_BASE_URL": "your-value",
        "AGENT_WEB_SEARCH_MESSAGES_API_KEY": "your-value",
        "AGENT_WEB_SEARCH_MESSAGES_BASE_URL": "your-value",
        "TAVILY_API_KEY": "your-value",
        "BRAVE_SEARCH_API_KEY": "your-value",
        "PERPLEXITY_API_KEY": "your-value",
        "YDC_API_KEY": "your-value",
        "EXA_API_KEY": "your-value",
        "PARALLEL_API_KEY": "your-value",
        "ZHIPU_WEB_SEARCH_API_KEY": "your-value",
        "ZHIPU_CHAT_SEARCH_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add agent-web-search --env AGENT_WEB_SEARCH_PROVIDERS=your-value --env ARK_API_KEY=your-value --env GEMINI_API_KEY=your-value --env XAI_API_KEY=your-value --env DEEPSEEK_API_KEY=your-value --env AGENT_WEB_SEARCH_RESPONSES_API_KEY=your-value --env AGENT_WEB_SEARCH_RESPONSES_BASE_URL=your-value --env AGENT_WEB_SEARCH_MESSAGES_API_KEY=your-value --env AGENT_WEB_SEARCH_MESSAGES_BASE_URL=your-value --env TAVILY_API_KEY=your-value --env BRAVE_SEARCH_API_KEY=your-value --env PERPLEXITY_API_KEY=your-value --env YDC_API_KEY=your-value --env EXA_API_KEY=your-value --env PARALLEL_API_KEY=your-value --env ZHIPU_WEB_SEARCH_API_KEY=your-value --env ZHIPU_CHAT_SEARCH_API_KEY=your-value -- uvx agent-web-search-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "agent-web-search": {
      "command": "uvx",
      "args": [
        "agent-web-search-mcp"
      ],
      "env": {
        "AGENT_WEB_SEARCH_PROVIDERS": "your-value",
        "ARK_API_KEY": "your-value",
        "GEMINI_API_KEY": "your-value",
        "XAI_API_KEY": "your-value",
        "DEEPSEEK_API_KEY": "your-value",
        "AGENT_WEB_SEARCH_RESPONSES_API_KEY": "your-value",
        "AGENT_WEB_SEARCH_RESPONSES_BASE_URL": "your-value",
        "AGENT_WEB_SEARCH_MESSAGES_API_KEY": "your-value",
        "AGENT_WEB_SEARCH_MESSAGES_BASE_URL": "your-value",
        "TAVILY_API_KEY": "your-value",
        "BRAVE_SEARCH_API_KEY": "your-value",
        "PERPLEXITY_API_KEY": "your-value",
        "YDC_API_KEY": "your-value",
        "EXA_API_KEY": "your-value",
        "PARALLEL_API_KEY": "your-value",
        "ZHIPU_WEB_SEARCH_API_KEY": "your-value",
        "ZHIPU_CHAT_SEARCH_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "agent-web-search": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "agent-web-search-mcp"
      ],
      "env": {
        "AGENT_WEB_SEARCH_PROVIDERS": "your-value",
        "ARK_API_KEY": "your-value",
        "GEMINI_API_KEY": "your-value",
        "XAI_API_KEY": "your-value",
        "DEEPSEEK_API_KEY": "your-value",
        "AGENT_WEB_SEARCH_RESPONSES_API_KEY": "your-value",
        "AGENT_WEB_SEARCH_RESPONSES_BASE_URL": "your-value",
        "AGENT_WEB_SEARCH_MESSAGES_API_KEY": "your-value",
        "AGENT_WEB_SEARCH_MESSAGES_BASE_URL": "your-value",
        "TAVILY_API_KEY": "your-value",
        "BRAVE_SEARCH_API_KEY": "your-value",
        "PERPLEXITY_API_KEY": "your-value",
        "YDC_API_KEY": "your-value",
        "EXA_API_KEY": "your-value",
        "PARALLEL_API_KEY": "your-value",
        "ZHIPU_WEB_SEARCH_API_KEY": "your-value",
        "ZHIPU_CHAT_SEARCH_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • AGENT_WEB_SEARCH_PROVIDERS env
    Comma-separated startup-enabled provider set; defaults to ddgs,exa,parallel (all keyless)
  • ARK_API_KEY secret env
    Volcengine Ark API key for Doubao grounding
  • GEMINI_API_KEY secret env
    Google Gemini API key for Google Search grounding
  • XAI_API_KEY secret env
    xAI API key for Grok web/X search
  • DEEPSEEK_API_KEY secret env
    DeepSeek API key for native web search
  • AGENT_WEB_SEARCH_RESPONSES_API_KEY secret env
    Generic Responses API key for web search grounding (falls back to OPENAI_API_KEY)
  • AGENT_WEB_SEARCH_RESPONSES_BASE_URL env
    Generic Responses API base URL; defaults to https://api.openai.com/v1
  • AGENT_WEB_SEARCH_MESSAGES_API_KEY secret env
    Generic Anthropic Messages API key for web search grounding
  • AGENT_WEB_SEARCH_MESSAGES_BASE_URL env
    Generic Anthropic Messages API base URL; defaults to https://api.anthropic.com
  • TAVILY_API_KEY secret env
    Tavily API key for agent-oriented search
  • BRAVE_SEARCH_API_KEY secret env
    Brave Search API key
  • PERPLEXITY_API_KEY secret env
    Perplexity API key for structured search
  • YDC_API_KEY secret env
    You.com API key
  • EXA_API_KEY secret env
    Optional Exa key; free MCP fallback without it
  • PARALLEL_API_KEY secret env
    Optional Parallel key; free MCP fallback without it
  • ZHIPU_WEB_SEARCH_API_KEY secret env
    Zhipu standalone Web Search API key
  • ZHIPU_CHAT_SEARCH_API_KEY secret env
    Zhipu Chat Completions native web search key

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account JerryLiu369, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

  • More stars than 0% of the other 5676 servers in this category
  • Published to the registry more recently than 72% of the other 5676 servers in this category
  • Basic checks equal to or better than 100% of the other 5676 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Agent Web Search safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: ARK_API_KEY, GEMINI_API_KEY, XAI_API_KEY, DEEPSEEK_API_KEY, AGENT_WEB_SEARCH_RESPONSES_API_KEY, AGENT_WEB_SEARCH_MESSAGES_API_KEY, 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

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.8.1) reached the registry 16 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday
Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago
Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated 2 months ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Agent Web Search

Agent-native web search — model-native grounding and agent search APIs behind one provider-neutral contract.

English | 简体中文

One-click remote MCP

Works with Codex CLI, Claude Code, OpenCode, Hermes, DeepSeek Harness (DSH), ordinary shell scripts, Python applications, and remote Streamable HTTP MCP clients.

Quickstart · Use with an agent · Providers · Configuration

Shared interface · Other interfaces · Troubleshooting · FAQ · Architecture · Development


Agent Web Search (PyPI: agent-web-search-mcp) is an open-source, MIT-licensed web search MCP server, CLI, and Python library for AI agents. It gives an agent three ways to reach the same provider-neutral search core: a native MCP tool, a native plugin (Hermes, DeepSeek Harness), or a CLI taught through a standard Agent Skill.

If you are an AI agent: install with pipx install agent-web-search-mcp

(or try instantly with uvx --from agent-web-search-mcp agent-web-search " "),

then read skills/agent-web-search/SKILL.md —

it teaches the CLI pathway only (for MCP setups, follow Option 1

instead). llms.txt

is the machine-readable doc index.

This is not a Google/Bing/Baidu metasearch wrapper. Traditional search aggregation fans a keyword query out to conventional engines and merges their result pages. Agent Web Search instead aggregates search capabilities built for agents: model-native web grounding, agent-oriented search APIs, and context-ready sources that accept natural-language questions and return answers, citations, or structured evidence in forms an agent can use directly. DDGS is the only conventional search backend in the current provider set.

          Natural-language question

| v SearchEngine +-----------+-----------+ | | | v v v DDGS Model Agent grounding APIs (Responses, (Exa, ARK, Grok, Parallel, Gemini...) Tavily...)

Installation & Quickstart

Three steps, about a minute: try it instantly, install it once, then connect your agent. Requirements: Python 3.10+. Default providers (DDGS, Exa, Parallel) require no API key.

Try without installing

Test immediate search capabilities using uvx (no environment modification):

# Direct natural-language search with keyless defaults

uvx --from agent-web-search-mcp agent-web-search "What changed in the latest OpenAI Codex CLI?"

Inspect MCP server arguments

uvx agent-web-search-mcp --help

Install

Install once into your global user environment (recommended):

# Recommended isolated installation

pipx install agent-web-search-mcp

Or install into the active Python environment

python -m pip install agent-web-search-mcp

Verify
# 1. Verify the CLI and run a real search

agent-web-search --version agent-web-search "What changed in the latest OpenAI Codex CLI?"

2. Verify the MCP server binary

agent-web-search-mcp --help

Two commands, two roles:

- agent-web-search: Direct search CLI for terminals, shell scripts, and Agent Skills.

- agent-web-search-mcp: Stdio and Streamable HTTP MCP server for MCP clients.

Pick your agent integration
IntegrationClient / EnvironmentSetup
CLI + Skill *(Recommended)*Terminal agents (Claude Code, Codex, OpenCode, Hermes)npx skills add JerryLiu369/agent-web-search --skill agent-web-search (Details)
MCP (Stdio)Codex CLI, Claude Code, Cursor, Cline, Roo Codecodex mcp add agent-web-search -- agent-web-search-mcp (Details)
DSH PluginDeepSeek Harness (desktop & web)dsh plugin --profile desktop add github:JerryLiu369/agent-web-search (Details)
Hermes PluginHermes Agenthermes plugins install JerryLiu369/agent-web-search (Details)

[!TIP]

Why CLI + Skill is recommended for shell-capable agents: If your agent already has terminal/bash execution capabilities (like Claude Code, Codex CLI, OpenCode, or Hermes), the CLI + Skill pathway offers the lowest friction and highest reliability. No MCP JSON configuration to debug, no background transport lifecycle to manage, and clean stdout JSON output taught through a standard Skill.

Why Agent Web Search

Traditional search aggregation (Google/Bing/Baidu wrappers, scraped SERPs) sends a keyword query to conventional engines and merges result pages. Agent Web Search instead aggregates search capabilities built for agents: one tool call returns structured, citation-ready evidence — or, through model-native grounding providers, a synthesized answer with explicit citations. A measured benchmark shows the practical difference: on a natural-language Chinese query asking for official sources, conventional SERP backends returned no government-domain results in the top 5, while the grounding provider returned official figures from China's General Administration of Customs with a working citation.

  • Agent-native by design. The primary interface is a complete natural-language question, not a thin keyword fan-out to Google, Bing, or Baidu.
  • Model-native search backends. ARK, Gemini, Grok, DeepSeek, Responses, Messages, Zhipu Chat Search, and Codex Alpha can combine web retrieval with model-generated synthesis and explicit citations.
  • Agent search providers. Exa, Parallel, Brave, Perplexity, Tavily, You.com, and Zhipu Web Search expose search APIs intended to provide structured, citation-friendly, or context-ready evidence to downstream agents.
  • One provider-neutral contract. Every backend is available through the same MCP tool, CLI, Python API, and normalized results; model-backed providers may also return an answer.
  • Independent providers. Selected providers run concurrently, and one provider's failure never discards another provider's successful result.
  • DDGS remains a simple fallback. DDGS is the only conventional search backend; it requires no API key and keeps the project usable without paid provider credentials. Exa and Parallel are also keyless by default.
  • No telemetry, no shared secrets. Provider keys stay in runtime environment variables; there is no shared API-key service.

Providers

The provider list is intentionally split by the kind of search capability it provides. Only DDGS is a conventional search backend; the other two groups are built around model-native grounding or agent-facing search services.

Free, keyless defaults: DDGS, Exa, and Parallel all work without an API

key. Exa and Parallel automatically use their free MCP transports until a

paid API key is provided.

Traditional search backend
ProviderWebsiteSearch backendAPI keyEnabled by default
DDGSDuckDuckGoConventional DuckDuckGo searchFree · no key requiredYes
Model providers

These providers use a model-native search or grounding surface. Their responses can include a model-generated answer together with citations or other explicit search evidence.

ProviderWebsiteModel-native search surfaceAPI keyEnabled by default
ARKVolcengine ArkResponses API with Doubao web-search groundingARK_API_KEYNo
Codex Alpha (experimental)Alpha Search-compatible gatewayModel-backed Alpha Search surfaceAGENT_WEB_SEARCH_CODEX_ALPHA_API_KEYNo
DeepSeekDeepSeek APIAnthropic Messages API with native web searchDEEPSEEK_API_KEYNo
GeminiGoogle AIGemini Google Search groundingGEMINI_API_KEYNo
GrokxAIxAI web search and X SearchXAI_API_KEYNo
ResponsesResponses API-compatible gatewayGeneric OpenAI Responses API with web search groundingAGENT_WEB_SEARCH_RESPONSES_API_KEYNo
MessagesMessages API-compatible gatewayGeneric Anthropic Messages API with web search groundingAGENT_WEB_SEARCH_MESSAGES_API_KEYNo
Zhipu Chat SearchZhipu AIGLM Chat Completions with native web searchZHIPU_CHAT_SEARCH_API_KEYNo
Agent search providers

These providers expose search services for agent consumption: natural-language queries, structured source rows, high-signal excerpts, or citation-friendly metadata rather than a conventional search-page experience.

ProviderWebsiteAgent-facing search surfaceAPI keyEnabled by default
ExaExaSemantic Search API or free MCP fallbackFree without key · optional EXA_API_KEYYes
ParallelParallelContext-oriented search API or free MCPFree without key · optional PARALLEL_API_KEYYes
BraveBrave SearchStructured Web Search APIBRAVE_SEARCH_API_KEYNo
PerplexityPerplexity APINative structured Search APIPERPLEXITY_API_KEYNo
TavilyTavilyAgent-oriented Search APITAVILY_API_KEYNo
You.comYou.com APIUnified web and news Search APIYDC_API_KEYNo

| **Zhipu Web Sear

Only the beginning is shown; read the rest in the repo

Ask PopNx