Chrome DevTools MCP vs Memory MCP
Side-by-side comparison with live GitHub signals. Last updated May 26, 2026.
| Metric | Chrome DevTools MCP | Memory MCP |
|---|---|---|
| GitHub Stars | 41.8K | 86.2K |
| Contributors | 89 | 430 |
| Last Commit | May 26, 2026 | May 21, 2026 |
| Open Issues | 89 | 522 |
| License | open-source | open-source |
| Pricing | open-source | open-source |
| Free Tier | Yes | Yes |
| Category | mcp-servers | mcp-servers |
| Trending | No | No |
Shared Tags
Only in Chrome DevTools MCP
Only in Memory MCP
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