MCP Client Configuration 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_configuration_pathC | Get the path to the configuration file for a specific client |
| get_configurationC | Get the entire configuration for a specific client |
| list_serversC | List all server names configured in a specific client |
| get_server_configurationB | Get the configuration for a specific server from a client configuration |
| add_server_configurationC | Add or update a server configuration in a client configuration |
| remove_server_configurationC | Remove a server configuration from a client configuration |
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 6 tools
Each tool has a clearly distinct purpose with no ambiguity: adding/updating, getting full config, getting config path, getting server-specific config, listing servers, and removing server config. The descriptions clearly differentiate between operations on the entire configuration versus specific servers.
All tools follow a consistent verb_noun pattern using snake_case throughout. The naming convention is perfectly uniform with clear action prefixes (add, get, list, remove) followed by specific objects (server_configuration, configuration, configuration_path, etc.).
Six tools is well-scoped for a client configuration management server. Each tool earns its place by covering essential CRUD operations for server configurations within client configs, plus utility functions for listing and path retrieval. The count is neither too sparse nor bloated.
The tool set provides complete lifecycle coverage for managing server configurations within client configurations: create/update (add_server_configuration), read (get_configuration, get_server_configuration, list_servers), delete (remove_server_configuration), plus utility (get_configuration_path). No obvious gaps exist for the stated domain.