MCP server for Plasmate - the browser engine for AI agents. Use with Claude Code, Claude Desktop, Cursor, Windsurf.
Plasmate MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Plasmate MCP directly instead of describing what you should do. MCP server for Plasmate - the browser engine for AI agents. Use with Claude Code, Claude Desktop, Cursor, Windsurf.
Installation goes through your MCP client rather than a global install: point it at plasmate-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Once Plasmate MCP is connected, these are the calls the assistant has available:
fetch_page — Fetch a URL and get the Semantic Object Model (SOM)extract_text — Get clean readable text from any URLopen_page — Open a persistent browser sessionclick — Click elements by SOM IDevaluate — Execute JavaScript in the pageclose_page — Close a browser sessionAmong the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Plasmate MCP's toolset — fetch_page, extract_text, open_page and 3 more — is a fair guide to whether it matches your workflow. It is maintained by plasmate-labs; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| fetch_page | Fetch a URL and get the Semantic Object Model (SOM) |
| extract_text | Get clean readable text from any URL |
| open_page | Open a persistent browser session |
| click | Click elements by SOM ID |
| evaluate | Execute JavaScript in the page |
| close_page | Close a browser session |
{
"mcpServers": {
"plasmate": {
"command": "npx",
"args": ["-y", "plasmate-mcp"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.