MCP Server Stack
The MCP servers that ship in every serious agent setup — from browser to database to popup-fix patches.
What's in this pack
The Model Context Protocol (MCP) is the open standard Anthropic shipped in late 2024 for connecting AI agents to external tools. A year later, the same eight MCP servers appear in nearly every serious agent configuration. This pack collects them.
| Server | What it gives the agent | Why it ships in every stack |
|---|---|---|
| Chrome DevTools MCP | Live DOM, console, network from a real Chromium | The only browser MCP with a fix for the multi-instance lock that breaks Cursor + Claude Code in parallel |
| Playwright MCP | Headless browser automation | Stable selector engine + screenshot + accessibility tree |
| Filesystem MCP | Scoped read/write to project files | Replaces shell cat/echo for tool-call accuracy |
| Postgres MCP | Direct SQL queries against any Postgres | Schema-aware completions and result rendering |
| GitHub MCP | Read PRs, issues, file blobs | Lets the agent do code review without a clone |
| Puppeteer MCP | Lower-level browser control | Useful when Playwright's abstractions get in the way |
| Slack MCP | Read + post in workspaces | Where most ops happens day to day |
| Figma MCP | Read frames, components, variables | Design-to-code without screenshots |
Why MCP matters in 2026
Before MCP, every IDE-agent pair invented its own tool format: Cursor had its own, Claude Code had its own, Codex CLI had its own. Each integration was a custom shim. MCP killed that — a single server now serves any host that speaks the protocol. Install once, work in Claude Code, Cursor, Codex CLI, Cline, Roo Code, Windsurf, GitHub Copilot, or Gemini CLI.
That's the structural reason this pack matters. The practical reason: most production blockers in agent setups come from missing MCP servers. The agent can't see the DOM, can't query the DB, can't read GitHub — and it hallucinates instead of asking.
Install in one command
tokrepo install pack/mcp-server-stack
# Or pick the ones you need
tokrepo install chrome-devtools-mcp
tokrepo install postgres-mcp
tokrepo install github-mcp
The TokRepo CLI wires each server into your active host's config (~/.claude/mcp.json for Claude Code, ~/.cursor/mcp.json for Cursor, etc) and starts them on next session.
Watch out for
- Chrome DevTools MCP needs the patched build. The vanilla version locks Chrome to a single agent at a time, which breaks anyone running Cursor and Claude Code in parallel. The pack defaults to the patched fork.
- Postgres MCP runs read-only by default. That's the right default. Flip the flag explicitly when you want write access.
- GitHub MCP rate-limits at 5,000 req/h on classic tokens. For teams, swap in a fine-grained token with bumped quota.
- Filesystem MCP scope is path-prefix based. Always pass the project root, not your home dir, to avoid the agent reading
~/.ssh/.
When this pack alone isn't enough
If you live in the browser → also install the Browser Automation pack (Browser-Use, Skyvern, Stagehand). If you're DB-heavy → also install Postgres for AI Agents for Neon, Supabase, and DBHub MCPs.
8 assets in this pack
Frequently asked questions
What is the Model Context Protocol (MCP)?
MCP is an open standard introduced by Anthropic in late 2024 for connecting AI agents to external data sources and tools. Instead of every IDE-agent pair inventing its own tool format, MCP defines a single JSON-RPC protocol that any host (Claude Code, Cursor, Codex CLI, etc) can speak to any server (Postgres, Filesystem, Chrome DevTools, etc). Spec at modelcontextprotocol.io.
Why these 8 servers specifically?
We pulled the install lists from the most-viewed agent setup guides on TokRepo and kept the servers that appeared in 4+ of them. The result is the de-facto core stack — browser, filesystem, source control, database, chat. Other useful servers exist (Slack, Notion, Linear) but those are workflow-specific.
Will MCP servers work in Cursor and Codex CLI, or just Claude Code?
All major hosts support MCP: Claude Code, Cursor, Codex CLI, Cline, Roo Code, Windsurf, GitHub Copilot, Gemini CLI. The TokRepo CLI writes to the right config file for whichever host is active. The same server binary serves all hosts.
Do MCP servers need API keys?
Some yes (GitHub MCP needs a personal access token, Slack MCP needs a workspace token, Figma MCP needs a personal token). Filesystem and Chrome DevTools MCPs run with no keys. The pack ships an .env.example listing each server's required keys.
What's the difference vs the Browser Automation pack?
MCP servers are how the agent sees state (DOM tree, network log, console). Browser Automation tools (Browser-Use, Skyvern, Stagehand) are how the agent acts on a page (click, fill, navigate) at higher abstraction. Most production setups install both.
12 packs · 80+ hand-picked assets
Browse every curated bundle on the home page
Back to all packs