Stop guessing which one. Put them side by side.

The grid says what these tools are. This says what builders did about it — one decision per person, changeable whenever you change your mind.

# Tool comparison — Cline MCP Marketplace vs Chrome DevTools MCP vs Figma MCP Server

Source: Kbaise, a directory of tools that work with Lovable projects.
Pick one and tell me why before writing any integration code.

## Cline MCP Marketplace (cline-mcp-marketplace)
- URL: https://github.com/cline/mcp-marketplace
- Category: MCP servers & registries
- Cost: free — Free
- What it is: A curated marketplace built into the Cline VS Code extension. Authors submit a server via GitHub issue with a repo URL and logo; reviewers weigh community adoption, developer credibility, project maturity and security, usually within a couple of days. On install, Cline handles setup and configuration autonomously.
- Why builders pick it: Removes the config-file step entirely — pick a server in the sidebar and the agent installs and wires it up. The human review gate makes it far safer than pulling from a 70,000-entry index.
- Trap: Only useful if you already use Cline, and the curated list is a tiny fraction of what Smithery or Glama index.
- Full dossier: /api/public/tools/cline-mcp-marketplace

## Chrome DevTools MCP (chrome-devtools-mcp)
- URL: https://github.com/ChromeDevTools/chrome-devtools-mcp
- Category: MCP servers & registries
- Cost: free — Free, open source
- What it is: Maintained by Google's Chrome DevTools team. It lets a coding agent control and inspect a live Chrome browser with full DevTools access: performance traces and insights, console messages with source-mapped stack traces, network request inspection, screenshots, DOM interaction, Lighthouse audits and memory debugging.
- Why builders pick it: Closes the loop where the agent writes frontend code but cannot see the result. It reads the real console error and the real network waterfall instead of asking you to paste a screenshot.
- Trap: If you attach it to an existing Chrome instance it drives your real profile and logged-in sessions — never point it at anything sensitive. Performance traces return very large payloads.
- Wiring: claude mcp add chrome-devtools --scope user npx chrome-devtools-mcp@latest
- Full dossier: /api/public/tools/chrome-devtools-mcp

## Figma MCP Server (figma-mcp-server)
- URL: https://developers.figma.com/docs/figma-mcp-server/
- Category: MCP servers & registries
- Cost: free — Free during beta · usage-based paid feature planned
- What it is: Figma's official server comes in two forms: a remote endpoint at https://mcp.figma.com/mcp available on all seats and plans, and a desktop server requiring a Dev or Full seat on a paid plan. It returns generated code, design system variables and components, layout context and Code Connect mappings.
- Why builders pick it: The agent reads the actual frame — real spacing, real tokens, real component names — instead of eyeballing a screenshot. Code Connect makes it emit your components rather than inventing new ones.
- Trap: Still beta, and Figma states it will eventually become a usage-based paid feature. Only MCP clients in Figma's approved catalog may connect; anything else joins a waitlist.
- Wiring: claude mcp add --transport http figma https://mcp.figma.com/mcp
- Full dossier: /api/public/tools/figma-mcp-server

## Rules
1. Prefer the free tier when no budget was stated, and say what the ceiling is.
2. Read the full dossier before integrating.
3. Fetch /api/public/models before writing any AI model ID.

Agents can fetch the same thing: GET /api/public/compare?slugs=cline-mcp-marketplace,chrome-devtools-mcp,figma-mcp-server