MCP Setup Playbook for Web Developers: Claude Code, Cursor & VS Code Configs, Server Recipes & Security Checklist
by CoreCodify
$24
Give your AI coding agent the right tools, without leaking a token
Every MCP server README is written for a different app. Claude Code wants mcpServers and ${VAR}, VS Code wants servers and ${input:...}, Codex wants TOML, and a config copied from one app quietly breaks in another. This playbook puts it all in one place: copy-paste setup for 5 AI clients, 20 server recipes for web work, and a security routine you can run on client projects.
Commands, file names, config keys and variable syntax were checked against the MCP specification (2026-07-28) and each vendor's official docs on 3 Nov 2026, with sources on every page.
What's inside
25-page PDF playbook: MCP in plain English, one page per client (Claude Code, Cursor, VS Code / GitHub Copilot, Claude Desktop, Codex) and a five-clients comparison table
20 server recipes: GitHub, Playwright, Chrome DevTools, Context7, Figma, Supabase, Sentry, Next.js DevTools, Vercel, Netlify, Cloudflare, Stripe, Shopify Dev, WordPress MCP Adapter, Linear, Notion, Neon, DBHub, Filesystem and Fetch, each with a Claude Code command, a JSON entry, auth and a safety note
The one-repo team pattern: commit shared configs with placeholders, keep tokens in each developer's environment
Config pack: ready .mcp.json, .cursor/mcp.json, .vscode/mcp.json, claude_desktop_config.json, Codex config.toml and .env.example
30-point security checklist and 8 MCP risks in plain English (prompt injection, tool poisoning, token passthrough and more)
16 common problems with fixes, plus a 5-minute test routine with MCP Inspector
6 starter stacks by project type and 6 workflows for client work (Figma to component, pre-launch browser QA, Sentry bug to PR...)
7-tab MCP Stack Planner (Excel / Google Sheets): pick servers and the mcpServers JSON builds itself; security review dates, a secrets inventory with rotation flags (names only, never values) and a troubleshooting log
Client AI & MCP Access Agreement and a Team Onboarding & Offboarding SOP (Word / Google Docs)
8 prompts to pick a stack, review or convert a config, audit tool descriptions and respond to a leaked token
Who it's for
Freelance web developers and small agencies using AI coding tools on client projects
Teams where people use different AI clients on the same repo
Anyone who's copied an MCP config from a README and watched it fail
Files
PDF guide + Quick-Start PDF, XLSX planner (Excel, Google Sheets, LibreOffice), 6 config files, 2 DOCX templates and a TXT prompt pack, in one ZIP. No coding course: it's a setup and security reference.
Good to know
Starter stacks, the checklist wording, workflows, prompts and safety notes are CoreCodify recommendations; vendor facts are labelled and sourced.
MCP tools change quickly. If a vendor's current docs differ, theirs win. Free v1.x updates.
The example client "Juniper Bakery" is fictional. No setup can make a server fully secure; you stay in control of what you connect and approve.
Licence: use it for your own and your clients' projects; don't resell or share the files.
Claude is a trademark of Anthropic, Cursor of Anysphere, VS Code and GitHub Copilot of Microsoft, Codex of OpenAI. CoreCodify is not affiliated with or endorsed by any of them.