Chrome DevTools MCP vs Figma Context 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. Figma Context MCP suits teams needing open-source access, design reading focus, and 15,701 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 | Figma Context MCP |
|---|---|---|
| GitHub Stars | 49.6K | 15.7K |
| Contributors | 118 | 30 |
| Last Commit | Aug 21, 2026 | Aug 7, 2026 |
| Open Issues | 90 | 24 |
| 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 shows broader GitHub adoption with 49,556 stars versus 15,701 for Figma Context MCP.
- • Chrome DevTools MCP has a larger visible contributor base (118 vs 30).
Choose Figma Context MCP if you need
- • Figma Context MCP is the stronger pick when Design Reading matters because that capability is listed only on its profile.
- • Figma Context MCP is the cleaner fit if you specifically need Figma workflows from the catalog tags.
Meaningful differences
- • GitHub adoption: Chrome DevTools MCP shows 49,556 stars versus 15,701 for Figma Context MCP.
- • Contributor count: Chrome DevTools MCP lists 118 contributors and Figma Context MCP lists 30.
Shared capabilities
- • No shared capabilities are explicitly listed in the stored metadata.
Shared Tags
Only in Chrome DevTools MCP
Only in Figma Context 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 Figma Context MCP
An MCP server that gives AI coding agents direct access to Figma design files. Translates Figma designs into structured layout and style data that LLMs can understand, enabling accurate design-to-code workflows. Agents can read component hierarchies, extract colors, spacing, typography, and generate pixel-perfect implementations.
View full listing