claude-mcp-config-manager
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_CONFIG_MANAGER_NO_AUTOCONFIG | No | When set to 1, skip automatic registration in claude_desktop_config.json during installation. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| open-mcp-config-managerA | Open an interactive panel to view and edit Claude Desktop's MCP server configuration (add, remove, or update servers without editing claude_desktop_config.json by hand). |
| read-mcp-configA | Read Claude Desktop's MCP config from disk (UI use only). |
| write-mcp-configA | Persist an MCP config to disk. Creates a timestamped backup of the previous file first. |
| check-server-statusA | Probe each configured MCP server with an MCP initialize handshake to see which ones actually respond (UI use only). |
| restart-claudeA | Quit and relaunch Claude Desktop so config changes take effect (UI use only). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| MCP Config Manager UI | UI panel for managing claude_desktop_config.json |
TDQS
Scored across 5 tools
Each tool maps to a clearly distinct action: interactive editing, reading config, writing config, checking server status, and restarting Claude. There is no meaningful overlap between them.
All tool names follow a consistent imperative verb-first pattern with hyphenated lowercase naming, such as read-mcp-config, write-mcp-config, and restart-claude. The naming is predictable and easy to scan.
Five tools is well-scoped for a config management server. Each tool covers a necessary step in the config lifecycle without redundant additions.
The tool set covers the full workflow: read the current config, edit it interactively, persist changes with backups, verify server connectivity, and restart Claude to apply changes. No obvious dead ends or missing critical operations.