Browser MCP Agent vs Memory MCP
Side-by-side comparison built from DeepYard's structured catalog. Content updated Aug 21, 2026.
Direct Answer
Browser MCP Agent suits teams needing open-source access, browser navigation focus, and 133,530 GitHub stars in current listing data. Memory MCP suits teams needing open-source access, persistent memory focus, and 89,768 GitHub stars in current listing data. This summary reflects catalog metadata only for decision support, not independent testing.
What this comparison weighs
- Pricing and free-tier availability
- License model and deployment fit
- GitHub adoption and contributor depth
- Catalog tags, integrations, and supported workflows
| Metric | Browser MCP Agent | Memory MCP |
|---|---|---|
| GitHub Stars | 133.5K | 89.8K |
| Contributors | 95 | 426 |
| Last Commit | Aug 22, 2026 | Aug 20, 2026 |
| Open Issues | 14 | 533 |
| License | open-source | open-source |
| Pricing | open-source | open-source |
| Free Tier | Yes | Yes |
| Category | mcp-servers | mcp-servers |
| Trending | No | No |
Choose Browser MCP Agent if you need
- • Browser MCP Agent is the stronger pick when Browser Navigation matters because that capability is listed only on its profile.
- • Browser MCP Agent shows broader GitHub adoption with 133,530 stars versus 89,768 for Memory MCP.
- • Browser MCP Agent is the cleaner fit if you specifically need Mcp workflows from the catalog tags.
Choose Memory MCP if you need
- • Memory MCP is the stronger pick when Persistent Memory matters because that capability is listed only on its profile.
- • Memory MCP has a larger visible contributor base (426 vs 95).
- • Memory MCP is the cleaner fit if you specifically need Memory workflows from the catalog tags.
Meaningful differences
- • GitHub adoption: Browser MCP Agent shows 133,530 stars versus 89,768 for Memory MCP.
- • Contributor count: Browser MCP Agent lists 95 contributors and Memory MCP lists 426.
Shared capabilities
- • No shared capabilities are explicitly listed in the stored metadata.
Shared Tags
Only in Browser MCP Agent
Only in Memory MCP
Limitations and evidence
- • DeepYard compares structured public metadata; this is not an independent benchmark unless a test record is shown.
- • Signals such as stars, contributors, and last commit indicate public activity, not purchase fit or runtime quality.
- • Pricing and feature coverage reflect the stored listing snapshot and may lag vendor changes between refreshes.
Source links
About Browser MCP Agent
A Model Context Protocol agent that provides browser automation capabilities to AI assistants. It can navigate to URLs, click elements, fill forms, take screenshots, and extract structured data from web pages. Built as an MCP server, it integrates with Claude Code, Cursor, and other MCP-compatible clients to give AI models real-time web interaction abilities. Part of the awesome-llm-apps collection.
View full listingAbout Memory MCP
The official Anthropic memory MCP server gives AI assistants persistent, cross-session memory using a local knowledge graph stored as a JSON file. Claude can create entities (people, projects, concepts), record relations between them, and add observations over time — then recall that information in future sessions. Ideal for long-running projects where continuity matters: the assistant remembers your architecture decisions, team conventions, and in-progress work without you having to repeat context.
View full listing