MCP Configurator Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_configB | Reads the Claude Desktop configuration file. |
| save_configA | Saves the configuration JSON after automatically creating a timestamped backup. |
| list_backupsA | Lists all available configuration backups with filename, creation timestamp, and size. |
| restore_backupB | Restores a selected backup configuration to the configuration file. |
| validate_commandB | Checks whether a command executable exists on the system path or as an absolute path. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct operation: reading config, listing backups, restoring, saving, and validating a command. No overlap in purpose.
All tool names follow a consistent snake_case verb_noun pattern (get_config, list_backups, restore_backup, save_config, validate_command).
5 tools is well-scoped for a configuration server, covering essential operations without excess or deficiency.
Core CRUD-like operations are present (read, save with backup, backup management, path validation). Missing a delete backup tool, but it's a minor gap.