Claude Code MCP Config Generator

Pick the MCP servers you use and get the exact claude mcp add commands or a ready .mcp.json block, scoped and copy-pasteable.

Step 1 of 2

Which MCP servers do you want?

Pick as many as you use. GitHub and Playwright are checked because most setups want them - uncheck anything you don't.

2 quick questions - free, no sign-up, nothing leaves your browser

FAQ

What is an MCP server in Claude Code?

A connection that gives Claude Code access to something real instead of a guess: your actual GitHub repos, your actual database, your actual production errors. Claude Code either starts it as a local process on your machine or talks to it over a remote URL, depending on the server.

Where does the generated config actually go?

Depends on the scope you pick. Project scope writes to .mcp.json in your repo root - commit it and your whole team gets the same servers. User scope has no file to edit at all; it lives in ~/.claude.json and the `claude mcp add -s user` commands manage it for you.

Do I have to create API tokens to use this?

Not upfront. GitHub, Sentry, Vercel, and PostHog use OAuth - the command opens a browser tab once and you sign in, no token to generate. Supabase needs a personal access token from your account settings, and Context7 optionally takes one for a higher rate limit. The generator flags exactly which is which per server.

Can I add an MCP server that isn't on the list?

Yes - "Add a server that isn't listed" on the first screen takes a name plus either the local command or the remote URL, and includes it in both outputs alongside the servers you checked.

Is this MCP config generator free?

Yes - free, no sign-up, and no real token or key ever leaves your browser; every output uses a placeholder you fill in yourself. ClockedCode separately sells a complete done-for-you Claude Code setup, but the generator itself is not gated.

This generator writes the config for adding MCP servers to Claude Code: check the servers you use, pick a scope, and it hands you the exact `claude mcp add` commands, or a ready .mcp.json block if you'd rather paste a file. Nothing here asks for a real API key or token - every output uses a clearly labeled placeholder instead, the same promise the settings.json generator makes.

Claude Code connects to an MCP server one of two ways: some run as a local process (stdio) that Claude Code starts itself, others live at a remote URL over HTTP and authenticate with OAuth, where a browser tab opens once, you sign in, and that's it, no token to create. Search "claude code mcp config" today and most of what comes back is a Reddit thread asking how to do this by hand, or a guide written for Claude Desktop instead of Claude Code, the wrong app entirely. This generator already knows which transport each server needs, so you never have to guess `--transport http` versus a bare command, or hunt down the right header syntax.

Eight servers are on the list, each one a checkbox: Context7 for current library docs, GitHub for repos and pull requests, Supabase for your real database, Sentry for production errors, Vercel for deploys and logs, PostHog for product analytics, Playwright for a real browser, and shadcn for pulling UI components straight from a registry. Anything else - an internal server, something niche - gets its own row through "Add a server that isn't listed," where you type the name and either the local command or the remote URL yourself.

The other decision is scope, and it changes what the commands actually do: project scope writes to .mcp.json in the repo, so committing it hands every teammate the same servers; user scope lives in ~/.claude.json on your machine and applies to every project you open, nothing to commit. The generator writes the right `-s` flag either way, and only offers the .mcp.json block when project scope is picked, since that is the only scope with a file worth pasting.

Once the servers are wired in, the settings.json generator covers the permission rules for what Claude can run without asking, and the best MCP servers writeup is where I explain which of these six I actually kept after testing over 20. Starting from nothing? Pair either with a starter from the Claude Code templates directory.

I run Claude Code daily and this generator emits the same `claude mcp add` commands my own setup uses. If you want the finished version of the whole idea - a tuned CLAUDE.md, a tuned settings.json, and the full vetted tool stack including MCP servers, installed in one paste - that is what ClockedCode is. The link is at the bottom of this page.

Neo ZinoBy Neo Zino - builder of ClockedCode

Other free tools

Config generator

Slash Command Generator

Answer 7 quick questions and get a custom Claude Code slash command with valid frontmatter, ready to drop into .claude/commands/.

Try toolConfig generator

Statusline Generator

Toggle the segments you want, watch the exact statusline render live, then copy the tested script and settings.json block.

Try toolConfig generator

settings.json Generator

Pick permission rules, hook presets, env vars, and a model override one step at a time, then copy or download the finished settings.json.

Try toolConfig generator

CLAUDE.md Generator

Answer 7 quick questions, get a tuned CLAUDE.md for your project in 30 seconds.

Try toolTemplate library

Claude Code Templates

A curated library of copy-paste Claude Code templates: subagents, hooks, slash commands, settings, and CLAUDE.md starters, each one explained and pulled from a setup that gets used every day.

Try toolToken scanner

UsageCut

Scan your Claude Code setup in 30 seconds and see exactly what is burning your tokens - bloated context, heavy MCP servers, and settings quietly draining your usage limits.

Try tool