mcp-web-setup: One CLI to Configure 18 MCP Servers Across Claude, Codex, and Gemini
Every AI coding tool has its own config format for MCP servers. Claude uses JSON, Codex uses TOML, Gemini uses a different JSON schema. Setting up the same 18 servers across all three means editing three files, remembering three formats, and hoping you didn't typo a credential. I built mcp-web-setup to do it once.
The Problem
MCP servers are powerful — Playwright for browser testing, Lighthouse for performance, Figma for design tokens, MySQL for database access. But configuring them is tedious:
- Each AI tool stores MCP config in a different file and format.
- Credentials (Figma tokens, MySQL passwords, Atlassian keys) need to go in the right places.
- Multi-workspace setups (different Bitbucket orgs per project) require per-directory configs.
- CMS projects on Lando need pre-filled database credentials.
Nobody wants to hand-edit TOML for the third time today.
The Solution
npx mcp-web-setup
An interactive CLI that walks you through selecting tools, server categories, and credentials — then writes correct configs for all selected platforms.
Included Servers (18 total)
| Category | Servers |
|---|---|
| Design | figma-desktop, figma-developer |
| Database | mysql |
| Browser / Testing | playwright, chrome-devtools, browser-tools |
| Performance / SEO | lighthouse, pagespeed |
| Accessibility | a11y |
| CSS / Styling | css, tailwindcss |
| Linting | eslint |
| Images | image-optimizer |
| Components | storybook |
| Utilities | sequential-thinking |
| Project Tools | atlassian, bitbucket, gtm |
Interactive Flow
- Select AI tools (Claude Code, Codex CLI, Gemini CLI)
- Select server categories
- Enter credentials (Figma token, MySQL password, etc.)
- Configure multi-workspace Bitbucket/Atlassian accounts
- Add CMS templates (WordPress/Drupal via Lando)
- Choose output mode (write to disk, print, or dry-run)
Safe Merge Behavior
Existing config files are backed up before writing. Only the MCP servers section is merged — all other settings are preserved. Servers you already have configured are kept untouched.
Config File Targets
| Tool | Global Config | Project Config |
|---|---|---|
| Claude Code | ~/.claude.json | .mcp.json |
| Codex CLI | ~/.codex/config.toml | .codex/config.toml |
| Gemini CLI | ~/.gemini/settings.json | .gemini/settings.json |
What I Learned
- Config format fragmentation across AI tools is a real friction point. Abstracting it away saves more time than it should.
- Multi-workspace support (different Atlassian/Bitbucket orgs per directory) is a common need that most setup tools ignore.
- Safe merge with backup is non-negotiable — overwriting someone's existing config is a trust-destroying experience.
- CMS templates (Lando defaults for WordPress/Drupal MySQL) eliminate a whole class of "why can't it connect" debugging sessions.