About Plasmate Mcp Server
Plasmate Mcp Server connects MCP clients to Plasmate for web browsing. Its tools fetch readable page text and structured page data, interact with pages, and manage persistent browser sessions.
Key features
- 01Fetch structured page data
- 02Extract readable text from URLs
- 03Open and close browser sessions
- 04Click elements by SOM ID
- 05Run JavaScript on a page
Use cases
- 01Browse web pages from an MCP client
- 02Extract text and structured data from URLs
- 03Interact with pages in a persistent session
MCP support
The MCP server exposes Plasmate browser tools to MCP clients, including page fetching, text extraction, interaction, JavaScript execution, and session management.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEplasmate-mcp
MCP server for Plasmate - the browser engine for AI agents.
Gives Claude Code, Claude Desktop, Cursor, Windsurf, and any MCP client the ability to browse the web through Plasmate instead of Chrome.
Install
# Install the MCP wrapper
npm install -g plasmate-mcp
# Install the Plasmate engine (pick one)
pip install plasmate
# or: cargo install plasmate
# or: brew tap plasmate-labs/plasmate && brew install plasmate
Use with Claude Code
claude mcp add plasmate -- npx plasmate-mcp
Or manually add to ~/.claude/settings.json:
{
"mcpServers": {
"plasmate": {
"command": "npx",
"args": ["-y", "plasmate-mcp"]
}
}
}
Use with Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"plasmate": {
"command": "npx",
"args": ["-y", "plasmate-mcp"]
}
}
}
Use with Cursor
Add to Cursor's MCP settings:
{
"mcpServers": {
"plasmate": {
"command": "npx",
"args": ["-y", "plasmate-mcp"]
}
}
}
This repo is also a Cursor plugin (.cursor-plugin/plugin.json + mcp.json). Test locally by copying it to ~/.cursor/plugins/local/plasmate. Submit the public repo at cursor.com/marketplace/publish.
Available Tools
Once connected, your AI gets these tools:
| Tool | Description |
|---|---|
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 |
Why Plasmate instead of Chrome?
- 16.6x fewer tokens - SOM is dramatically smaller than DOM dumps
- 50x faster - No rendering engine overhead
- 30MB memory - vs Chrome's 300MB+
- Structured output - Clean JSON, not raw HTML
Links
Part of the Plasmate Ecosystem
| Engine | plasmate - The browser engine for agents |
| MCP | plasmate-mcp - Claude Code, Cursor, Windsurf |
| Extension | plasmate-extension - Chrome cookie export |
| SDKs | Python / Node.js / Go / Rust |
| Frameworks | LangChain / CrewAI / AutoGen / Smolagents |
| Tools | Scrapy / Audit / A11y / GitHub Action |
| Resources | Awesome Plasmate / Notebooks / Benchmarks |
| Docs | docs.plasmate.app |
| W3C | Web Content Browser for AI Agents |
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.