DeepYardDeepYard

Chrome DevTools MCP vs Memory MCP

Side-by-side comparison with live GitHub signals. Last updated April 1, 2026.

C

Chrome DevTools MCP

Official Google MCP server giving coding agents full Chrome DevTools access — 28K+ stars

OSSFree
32.6Ktoday72
M

Memory MCP

Persistent knowledge graph memory across AI coding sessions

OSSFree
82.7K15.0K/w3d ago430
MetricChrome DevTools MCPMemory MCP
GitHub Stars32.6K82.7K
Contributors72430
Last CommitApr 1, 2026Mar 29, 2026
Open Issues95628
Licenseopen-sourceopen-source
Pricingopen-sourceopen-source
Free TierYesYes
Categorymcp-serversmcp-servers
TrendingNoNo

Shared Tags

No shared tags

Only in Chrome DevTools MCP

chromedevtoolsdebuggingbrowsergoogleperformanceautomation

Only in Memory MCP

memoryknowledge-graphpersistenceanthropicreference-servercontext-management

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 listing

About 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