MCP Setup Pack — v2

Run one command.
Get 22 MCP servers working.

The pack now ships with an automated installer and doctor script that set up your servers and verify they are actually running — not just configured. Plus the 24-page PDF guide and configs.zip.

Get the Pack — $15

One-time payment. Instant download. No subscription.

What's new in v2: installer + doctor scripts

The pack now includes install.sh / install.ps1 (macOS/Linux/Windows). Run it, pick which of the 22 servers you want, enter your tokens, and it writes claude_desktop_config.json in the right location. No JSON editing required.

If something isn't working after restart, run doctor.sh / doctor.ps1. It checks Node/npx, uv/uvx, config validity, missing env vars, and unfilled placeholders — and prints the exact fix for each problem.

The MCP setup experience is genuinely bad. Config file paths differ by OS. npx vs uvx is the single most common silent failure and almost nothing documents it. Tokens silently expire. Servers crash and Claude just says “tool unavailable.” Most devs lose 2–4 hours their first week on config problems that have known fixes.

What’s in the pack

Installer + Doctor scripts
install.sh (macOS/Linux) and install.ps1 (Windows) check your dependencies, let you choose servers, prompt for tokens/paths, back up your existing config, and write the merged config automatically.

doctor.sh / doctor.ps1 diagnoses: Node/npx present, uv/uvx present, config is valid JSON, every server command resolves in PATH, required env vars set, no unfilled path placeholders. Prints the exact fix for each problem.
📄
Quickstart PDF (24 pages)
What is included & installer-first quick start. Config file locations on Mac, Windows, Linux. The npx vs uvx decision (this alone saves an afternoon). Decision Matrix: official vs community, auth required, read vs write, local vs remote, security risk. Secrets Setup: how to obtain every credential with exact steps. Common Errors appendix: spawn ENOENT, uvx not found, Windows path escaping, token scope errors — with exact fixes. 22 server pages with working config, tools list, gotchas, security flag.
📦
configs.zip
Ready-to-paste claude_desktop_config.json with all 22 servers. Per-server config snippets. env-example.txt with every token/key you need. The installer uses this file automatically — or drop it in manually.
🗂
Notion duplicatable database
All 22 servers as a sortable, filterable Notion DB. Filter by auth required, runtime (npx/uvx), read/write, category. Useful when you’re choosing which servers to add next.

The 22 servers covered


Who it’s for

Claude Desktop usersYou've installed Claude and want to actually connect it to your tools
Cursor / Windsurf devsSame MCP protocol, same config frustrations
Devs new to MCPSkip the trial-and-error phase and get 22 servers working in a day
Teams onboarding to AIA repeatable setup that everyone can follow

$15 one-time

Get the MCP Setup Pack

Installer + doctor + PDF guide + configs.zip. Instant download via Polar.

Get the Pack — $15

Free resources

MCP Server Directory


FAQ

What exactly do I get?

Install scripts (macOS/Linux/Windows), a doctor script, a 24-page PDF quickstart guide, configs.zip with a stitched claude_desktop_config.json, per-server snippets, env-example.txt, and a duplicatable Notion database. Delivered instantly via Polar after checkout.

Does the installer actually work, or is it just docs?

The installer genuinely writes your config file. It checks Node/npx and uv/uvx (installs if missing), lets you pick servers, prompts for tokens and paths, backs up your existing config, and writes claude_desktop_config.json in the right location. The doctor script then verifies everything is correct. If any check fails, it prints the exact fix.

Does this work with Cursor and Windsurf?

Yes. The MCP protocol and config format are the same. Some paths differ slightly — the PDF covers all three.

Why $15?

Less than one hour of your time, and MCP config problems routinely take 2–4 hours. The installer alone eliminates most of that. If it doesn’t save you that time, email support@hatchloop.dev for a full refund.

I found a bug in a config or the installer — can I report it?

Yes. support@hatchloop.dev. Fixes are pushed to the download.