mcpconfig

A CLI to discover and inspect MCP (Model Context Protocol) configs and servers across your AI coding tools.

Published on npm: @yash_pandit/mcpconfig

If you use Claude Desktop, Cursor, Codex, Cline, or similar apps, each one stores its MCP configuration in a different place. mcpconfig finds those config files and lists them—and can show every MCP server (name, command, args) from all of them in one view.

What is MCP?

The Model Context Protocol (MCP) is a standard that lets AI assistants connect to external tools and data sources (files, databases, APIs). Many AI coding apps support MCP via a config file where you declare “servers” (each with a command and optional args). mcpconfig does not run or manage those servers; it only lists where configs live and what servers are defined in them.

Features

• List config locations — See which MCP config files exist on your system and their full paths. Optionally show all known locations (including ones that don’t exist yet).
• List servers across configs — For every found JSON config and Codex TOML, show a combined table of app name, server name, command, and args so you can compare setups at a glance.
• Add a server interactively — Run add-server to select one or more apps (multi-select with “Select all”), then enter server name, command, and args; mcpconfig writes to every selected config (JSON or Codex TOML) per each app’s spec.
• Multi-app support — Knows the default config paths for Claude Desktop, Cursor, Codex, Cline, Roo Code, Windsurf, Zed, Cody, Goose, Continue.dev, and Junie CLI.

Requirements

• Node.js 16 or newer

Install

Global install (recommended if you want the mcpconfig command everywhere):

npm install --global @yash_pandit/mcpconfig

Run without installing (e.g. try it once or use in scripts):

npx @yash_pandit/mcpconfig list-configs
npx @yash_pandit/mcpconfig list-servers

From source (clone the repo, then):

npm install
npm run build
npm link

After npm link, mcpconfig is available globally from your dev build. You can also run the built CLI with npm start or node dist/cli.js.

Usage

mcpconfig <command> [options]

Commands

| Command | Description | |----------------|-------------| | list-configs | List MCP config file locations. By default shows only configs that were found on disk. | | list-servers | Read all found JSON configs and Codex config.toml, extract MCP servers (mcpServers or mcp_servers), and print a table: app name, server name, command, args. | | add-server | Interactive flow: select one or more apps (↑/↓ move, Space toggle, “Select all” option, Enter to confirm), then enter server name, command, and args. Writes to every selected config (JSON or Codex TOML) per spec. |

Options

| Option | Short | Description | |-----------|-------|-------------| | --all | -a | Only for list-configs. Show every known config location (found and not found). |

Examples

# See which MCP configs exist and where they are
mcpconfig list-configs

# See all known config locations (including missing ones)
mcpconfig list-configs --all

# See all MCP servers from every found JSON config in one table
mcpconfig list-servers

# Interactively add an MCP server to a config (choose app, then name, command, args)
mcpconfig add-server

list-configs prints one line per config: app name, ✓ or ✗ (found or not), and the full path when found.

list-servers prints a table with columns: APP, SERVER, COMMAND, ARGS. JSON configs use the mcpServers key; Codex uses ~/.codex/config.toml and the [mcp_servers.<name>] tables per the Codex config reference. Other TOML/YAML configs are not parsed for servers.

add-server shows only configs that exist and support adding servers (JSON and Codex TOML). You can select multiple apps: use ↑/↓ to move, Space to toggle each app (or “Select all”), then Enter to continue. You’re then prompted for name, command, and args (comma-separated). The new server is written to every selected config; JSON gets a mcpServers entry and Codex TOML gets an [mcp_servers.<name>] section.

Supported apps and config paths

mcpconfig looks for these files under your home directory:

| App | Config path (relative to ~) | |------------------|-------------------------------| | Claude Desktop | Library/Application Support/Claude/claude_desktop_config.json | | OpenAI Codex | .codex/config.toml | | Cursor | .cursor/mcp.json | | Cline | .cline/data/settings/cline_mcp_settings.json | | Roo Code | Library/Application Support/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/mcp_settings.json | | Windsurf | .codeium/windsurf/mcp_config.json | | Zed | .config/zed/settings.json | | Cody | .config/cody/mcp_servers.json | | Goose | .config/goose/config.yaml | | Continue.dev | .continue/config.yaml | | Junie CLI | .junie/mcp/mcp.json |

Only JSON configs are used for list-servers; the tool expects an mcpServers object in them. TOML/YAML apps are listed by list-configs but not parsed for servers.

Development

# Install dependencies
npm install

# Build TypeScript → dist/
npm run build

# Watch mode (rebuild on file changes)
npm run dev

# Run the CLI from the built output
npm start
# or
npx @yash_pandit/mcpconfig list-configs

# Lint and test
npm test

License

MIT