grab-cookie vs io.github.browserbase/mcp-server-browserbase
grab-cookie is a plugin bundle for AI coding tools published by Mike Bramm. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.browserbase/mcp-server-browserbase is an MCP server published by browserbase. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-22. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.browserbase/mcp-server-browserbase | |
|---|---|---|
| Community marketplace servosity/msp-skills | Listed Version: 0.1.0 Forks (GitHub): 13 Stars (GitHub): 62 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.1.1 Downloads/month (npm): 19 182 Downloads/week (npm): 2 969 Forks (GitHub): 371 Stars (GitHub): 3 398 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:f90cb76e34ba Forks (GitHub): 371 Pulls (Docker Hub): 38 257 Stars (Docker Hub): 1 Stars (GitHub): 3 398 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | grab-cookie | io.github.browserbase/mcp-server-browserbase |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 62 (worse) | 3 398 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 38 257 |
| Forks (GitHub) (differs) | 13 (worse) | 371 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | stdio, Streamable HTTP |
| Tools it declares (differs) | Not published | 6 |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 2 |
| Licence | Apache-2.0 | Apache-2.0 |
| Repository (differs) | github.com/servosity/msp-skills | github.com/browserbase/mcp-server-browserbase |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (40 h ago) |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
grab-cookie
Capture, store, wire, and verify a browser-session credential for sites that issue no API key and no OAuth: httpOnly session cookies, opaque localStorage bearer tokens, and custom auth headers. One DevTools Copy as cURL paste is the only human step; extraction, storage in the Windows Credential Manager or macOS Keychain, config regeneration, live verification, and expiry warning are automated. Complements connect-tool, which deliberately refuses cookie import. Markdown plus stdlib Python, no compiled binary and no MCP server.
io.github.browserbase/mcp-server-browserbase
MCP server for AI web browser automation using Browserbase and Stagehand
How to run each
grab-cookie As a Claude Code plugin
/plugin marketplace add servosity/msp-skills
/plugin install grab-cookie@msp-skillsio.github.browserbase/mcp-server-browserbase As a local MCP server: npm package
claude mcp add --env "BROWSERBASE_API_KEY=<YOUR_BROWSERBASE_API_KEY>" --env "BROWSERBASE_PROJECT_ID=<YOUR_BROWSERBASE_PROJECT_ID>" --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --transport stdio mcp-server-browserbase -- npx -y @browserbasehq/mcp-server-browserbaseRequires: BROWSERBASE_API_KEY (secret), BROWSERBASE_PROJECT_ID, GEMINI_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.browserbase/mcp-server-browserbase has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of grab-cookie publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of grab-cookie publish no settings it asks for, so we do not compare settings.
What it can do: grab-cookie · What it can do: io.github.browserbase/mcp-server-browserbase · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.