Open Agent Search

One self-hostable search and content layer for AI agents and applications.

What is OAS? · Quick start · Capabilities · Architecture · API surface · Contributing

What is Open Agent Search?

Open Agent Search (OAS) is an independent retrieval layer for AI agents and applications. It provides one consistent search and content surface across local and deployed integrations.

OAS replaces separate adapters for every search vertical with one consistent tool surface. Run it locally for a single coding agent or deploy the HTTP service for shared agent and application workloads.

Search sources, transports, and client integrations can evolve without changing the repository's core goal: give agents and applications a dependable retrieval boundary they can control.

Try it in 30 seconds

Add search to Claude Code

claude mcp add oas -- uvx --from open-agent-search oas-mcp

Restart Claude Code, then ask it to search the web, news, images, videos, or books. The same uvx command works with Cursor, VS Code, Windsurf, OpenClaw, and other MCP clients.

{
  "mcpServers": {
    "open-agent-search": {
      "command": "uvx",
      "args": ["--from", "open-agent-search", "oas-mcp"]
    }
  }
}

Run the HTTP API

uv pip install open-agent-search
open-agent-search

Make a first search:

curl "http://localhost:8000/api/search/text?q=python+programming&max_results=5"

The server exposes REST endpoints at http://localhost:8000, interactive API docs at /docs, and streamable HTTP MCP at /ai/mcp.

Capabilities

• One search layer, multiple transports. Use stdio MCP locally or serve REST and MCP over HTTP.
• No provider API key required. Search is powered by the ddgs library.
• Self-hostable. Run locally, in Docker, or deploy the HTTP service to Vercel.
• Framework-independent. The protocol surface works across major MCP clients and agent stacks.
• Production-minded defaults. Typed FastAPI routes, rate limiting, health checks, tests, and deployment guides are included.

Architecture

The local MCP command and the HTTP service share the same search and content capabilities. Choose the connection path that matches where the consuming agent or application runs.

Two deployment paths

Search surface

See the API reference and MCP tool reference for parameters and response shapes.

Privacy model

OAS does not require an OAS account or a search-provider API key, and it can run on infrastructure you control. Search queries still have to reach upstream search providers through DDGS, so this project should not be treated as an anonymity network. Review your deployment logs, network policy, and upstream-provider terms for sensitive workloads.

Install and deploy

From source

git clone https://github.com/jayanth-mkv/open-agent-search.git
cd open-agent-search
uv sync
uv run open-agent-search

Docker

docker compose up -d

Deploy with Vercel

Deployment details: Docker · Vercel

Documentation

• Installation
• Quick start
• MCP integrations
• API endpoints
• Contributing

Development

uv sync --group dev
uv run pytest
uv run ruff check .

Open Agent Search is currently beta software. Bug reports and focused pull requests are welcome; see CONTRIBUTING.md.

License

MIT