Chrome DevTools MCP
Let the agent open the page and read what actually rendered
- mcp
- browser
- chrome
Model Context Protocol servers that let an agent drive a browser, query a database, read a repository or fetch live documentation. Each entry says what the server can touch and what it cannot.
Let the agent open the page and read what actually rendered
Browser automation through the accessibility tree instead of pixels
Current library documentation, fetched instead of remembered
Issues, pull requests and code search without leaving the agent
Let the agent read your schema instead of imagining it
The canonical implementations to read before writing your own
The question this shelf answers: What can this server actually do to my systems?
| Tool | Licence | Language | Cost | Self host |
|---|---|---|---|---|
| Chrome DevTools MCP | Apache-2.0 | TypeScript | Free | Yes |
| Playwright MCP | Apache-2.0 | TypeScript | Free | Yes |
| Context7 | MIT | TypeScript | Free tier | Yes |
| GitHub MCP Server | MIT | Go | Free | Yes |
| Supabase MCP | Apache-2.0 | TypeScript | Free tier | Yes |
| Reference MCP Servers | MIT | TypeScript and Python | Free | Yes |
One channel. New entries when they are added, with the caveat included. No daily digest, no course, nothing to buy.
Join the TelegramFree. No email required.