Chrome DevTools MCP vs Memory MCP
Side-by-side comparison built from DeepYard's structured catalog. Content updated Aug 21, 2026.
Direct Answer
Chrome DevTools MCP suits teams needing open-source access, browser automation focus, and 49,556 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 | Chrome DevTools MCP | Memory MCP |
|---|---|---|
| GitHub Stars | 49.6K | 89.8K |
| Contributors | 118 | 426 |
| Last Commit | Aug 21, 2026 | Aug 20, 2026 |
| Open Issues | 90 | 533 |
| License | open-source | open-source |
| Pricing | open-source | open-source |
| Free Tier | Yes | Yes |
| Category | mcp-servers | mcp-servers |
| Trending | No | No |
Choose Chrome DevTools MCP if you need
- • Chrome DevTools MCP is the stronger pick when Browser Automation matters because that capability is listed only on its profile.
- • Chrome DevTools MCP is the cleaner fit if you specifically need Chrome 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 shows broader GitHub adoption with 89,768 stars versus 49,556 for Chrome DevTools MCP.
- • Memory MCP has a larger visible contributor base (426 vs 118).
Meaningful differences
- • GitHub adoption: Chrome DevTools MCP shows 49,556 stars versus 89,768 for Memory MCP.
- • Contributor count: Chrome DevTools MCP lists 118 contributors and Memory MCP lists 426.
Shared capabilities
- • No shared capabilities are explicitly listed in the stored metadata.
Shared Tags
Only in Chrome DevTools MCP
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 Chrome DevTools MCP
An official Google MCP server that gives AI coding agents full access to Chrome DevTools. Enables performance trace recording with actionable insights, advanced debugging (network requests, screenshots, console messages with source-mapped stack traces), and reliable Puppeteer-based browser automation with automatic result waiting. Supports headless mode for servers, isolated mode with temp user data, and WebSocket connection to existing Chrome instances.
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