Skip to main content
📖 The AI Tool Bible

Brave Search MCP vs MCP Memory Server

A side-by-side look at pricing, capabilities, pros, cons, and our editorial scores.

 Brave Search MCP logo
Brave Search MCP
MCP Servers
MCP Memory Server logo
MCP Memory Server
MCP Servers
TaglineGive any MCP client web and local search powered by the Brave Search API.Persistent knowledge-graph memory for Claude and other MCP clients
CategoryMCP ServersMCP Servers
PricingFreemium· Free: $0 USD · Team: $4 USD per user/month · Enterprise: $21 USD per user/monthFree· Free and open source (MIT). Self-hosted; no vendor charges. Runs locally via npx or Docker.
Model
Editorial score
Use cases
Grounded web search inside Claude DesktopAgent fact-checking and citation lookupIDE-side research from Cursor or WindsurfLocal business and restaurant discoveryCheap RAG augmentation for small chatbotsMCP server learning and forkingPrivacy-respecting alternative to Google search in agents
Persistent Claude Desktop memory across chatsLong-lived coding-agent project memoryLightweight personal CRM of people and companiesResearch-agent scratch knowledge graphCross-session preference and style memoryTeam convention and past-bug recall for coding assistantsStructured note-taking backend for MCP clientsLocal-first alternative to hosted memory APIs
Pros
  • Two focused tools (web + local search) that are easy to reason about and stable to prompt against
  • Small, single-file TypeScript implementation that's trivial to read, fork, or self-host
  • Ships as both an npm package and a Docker image, with VS Code one-click install
  • Backed by Brave's independent index, so results don't depend on Google/Bing rate limits or ToS
  • Free tier covers 2,000 queries/month, enough for personal agents and prototyping
  • MIT-licensed reference implementation from the MCP project itself
  • Local-search fallback to web means agents rarely get an empty result set
  • Official, Anthropic-maintained reference implementation - the canonical way to add persistent memory to an MCP client
  • Zero-config install via npx or a one-line Docker command; works out of the box with Claude Desktop's claude_desktop_config.json
  • Simple, inspectable JSONL storage on disk that you can grep, diff, back up and edit by hand
  • Structured entity/relation/observation model is more queryable than a raw text scratchpad and cheaper than a vector DB
  • Nine well-scoped tools plus a live-updating knowledge-graph Resource, so agents can both read and mutate memory
  • Fully open source (MIT) and vendor-neutral - runs against any MCP-speaking model, not just Claude
  • Trivial to fork or wrap for team-specific schemas since the codebase is a single small TypeScript file
Cons
  • Repository is archived (read-only since May 29, 2025) and no longer receives fixes or new features
  • Superseded by Brave's own official server, which adds image/video/news/summarizer tools and HTTP transport
  • Free tier is capped at 1 query per second, which throttles multi-step agents
  • Local search is US-centric and quality varies sharply outside North America
  • No streaming HTTP transport in this version, stdio only, which complicates remote/multi-tenant deployments
  • Brave's index, while good, is smaller than Google's and can miss long-tail queries
  • Reference-quality, not production-grade: single-file JSONL storage with no concurrency control, indexing or replication
  • search_nodes is a plain substring match with no embeddings or semantic ranking - large graphs degrade quickly
  • No built-in multi-user, auth or per-project isolation; a shared install mixes memories from every session
  • The model still has to be prompted to actually call the memory tools - forgetful assistants forget to remember
  • No web UI, visualisation or admin surface; you inspect and clean the graph by editing the JSONL yourself
  • Only a local filesystem backend - no Postgres, SQLite or cloud sync option is shipped
Websitegithub.comgithub.com
Pick Brave Search MCP if
  • Two focused tools (web + local search) that are easy to reason about and stable to prompt against
  • Small, single-file TypeScript implementation that's trivial to read, fork, or self-host
  • Ships as both an npm package and a Docker image, with VS Code one-click install
  • Backed by Brave's independent index, so results don't depend on Google/Bing rate limits or ToS
Pick MCP Memory Server if
  • Official, Anthropic-maintained reference implementation - the canonical way to add persistent memory to an MCP client
  • Zero-config install via npx or a one-line Docker command; works out of the box with Claude Desktop's claude_desktop_config.json
  • Simple, inspectable JSONL storage on disk that you can grep, diff, back up and edit by hand
  • Structured entity/relation/observation model is more queryable than a raw text scratchpad and cheaper than a vector DB