Brave Search (official)
BraveBrave's own server, and the one to use now that the older reference implementation sits in the archived repository
Brave's own server, and the one to use now that the older reference implementation sits in the archived repository On the other side: web search built for agents rather than people: results come back with extracted content and optional answer synthesis, which removes a second fetch step
Brave when citations matter; Tavily when reading several pages quickly matters.
Brave returns search results — titles, URLs, snippets — and lets the agent decide what to fetch. Tavily returns extracted content and an optional synthesis, which removes a step and adds an opinion. For citation work Brave is more honest; for research summaries Tavily is faster.
| Option | Install | Source | Link |
|---|---|---|---|
| Brave Search (official) | npx -y @brave/brave-search-mcp-server | Official | Repository ↗ |
| Tavily MCP | npx -y tavily-mcp | Official | Repository ↗ |
The agent should cite sources a human can open and check.
The agent needs to read several pages quickly and report a conclusion.
A project going archived, or a maintainer changing the install path, flips this comparison faster than any feature release. Both entries are re-checked weekly, and the date above tells you how much to trust the details.
Brave's own server, and the one to use now that the older reference implementation sits in the archived repository
Web search built for agents rather than people: results come back with extracted content and optional answer synthesis, which removes a second fetch step
Gives an agent scoped read, write, and search access to directories you explicitly allow
Read-only access to a repository's history: status, diffs, commit logs, and blame
Drives a real browser through accessibility snapshots rather than screenshots, so an agent can click, type, and assert without a vision model
A persistent knowledge graph stored in a local JSON file, exposed through entities, relations, and observations
Talks to the Kubernetes API directly instead of shelling out to kubectl, so an agent can list contexts, read pod logs, and apply manifests without parsing command output
Reads and changes feature flags through the LaunchDarkly API, so an agent can turn a flag off during an incident instead of asking a human to open a dashboard