Skip to main content
Glama
blueewhitee

agent-web-search-mcp

by blueewhitee
README.md
# agent-web-search-mcp

Standalone [Model Context Protocol](https://modelcontextprotocol.io) (MCP) server for the
[**agent-web-search**](https://github.com/blueewhitee/agent-web-search) API.

A thin stdio wrapper — it just calls the API over HTTP and formats results for any
MCP-compatible agent (Claude Desktop, Cursor, Pi, etc.).

> This package is a **client of** the `agent-web-search` engine, not the engine itself.
> You need a running instance of the engine (see below) before the MCP can do anything.

---

## Install

```bash
uv tool install git+https://github.com/blueewhitee/agent-web-search-mcp
```

## Configure your MCP client

Add this to your MCP config (e.g. `~/.pi/agent/mcp.json` for Pi,
`claude_desktop_config.json` for Claude Desktop):

```json
{
  "mcpServers": {
    "agent-web-search": {
      "command": "agent-web-search-mcp",
      "env": {
        "AGENT_WEB_SEARCH_API_URL": "http://localhost:8000"
      }
    }
  }
}
```

`AGENT_WEB_SEARCH_API_URL` defaults to `http://localhost:8000` — set it to wherever your
engine is reachable.

## What you get

A single tool, `web_search`, that:
- routes the query to the engine's intent detector (code / news / general),
- fetches + extracts + ranks results,
- returns ranked chunks with scores and source URLs.

## Requirements

- A running `agent-web-search` engine (the FastAPI service from the
  [agent-web-search](https://github.com/blueewhitee/agent-web-search) repo).
  Easiest path: clone that repo and `docker compose up`.
- Python ≥ 3.12.

## Development

```bash
git clone https://github.com/blueewhitee/agent-web-search-mcp
cd agent-web-search-mcp
uv tool install --editable .
```

The `agent-web-search-mcp` command will then reflect local changes on restart.

## License

MIT (same as the engine).

TDQS

A4.5/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is zero chance of selecting the wrong tool. The tool's purpose is clearly defined as web search.

Naming Consistency5/5

The single tool name 'web_search' follows a clear verb_noun pattern, but there are no other tools to compare consistency.

Tool Count2/5

The server has only one tool, which falls below the typical minimum for a useful server. While search can be a single operation, the rubric considers 1 tool too few.

Completeness5/5

For the stated purpose of web search, the tool provides comprehensive functionality including content fetching and ranking. There are no obvious missing operations within its scope.

Maintenance

ActivityStale
ResponsivenessNo issues