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 — Filesystem MCP vs Chrome DevTools MCP vs Cline MCP Marketplace

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

## Filesystem MCP (filesystem-mcp)
- URL: https://github.com/modelcontextprotocol/servers/tree/main/src/filesystem
- Category: MCP servers & registries
- Cost: free — Free, MIT
- What it is: A maintained reference server for file operations with access controls. Tools include read_text_file, read_media_file, write_file, edit_file, directory_tree, search_files and move_file. Access is confined to directories passed at startup, or set dynamically by the client via the MCP Roots protocol.
- Why builders pick it: The way to give a chat client like Claude Desktop genuine file access, or to let an agent reach a folder outside its project — a shared assets directory, say — without handing over the whole disk.
- Trap: Largely redundant inside Claude Code or Cursor, which already have native file tools; adding it duplicates tools and bloats context for no gain. Always scope the allowed directory narrowly.
- Wiring: claude mcp add filesystem npx -y @modelcontextprotocol/server-filesystem /path/to/project
- Full dossier: /api/public/tools/filesystem-mcp

## 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

## 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

## 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=filesystem-mcp,chrome-devtools-mcp,cline-mcp-marketplace