add_server_configuration
Add or update a server configuration in a client configuration
LABSCO SUMMARY
A small server whose entire point is that it can rewrite the file deciding which servers exist.
The read half — get_configuration_path, get_configuration, list_servers, get_server_configuration — is convenience; the write half is a real capability, because add_server_configuration accepts an arbitrary json_config and allow_override decides whether it replaces an entry that is already registered. Grant that deliberately: an agent able to add a server configuration to a client can also add one you did not choose, and remove_server_configuration takes a name with no confirmation step in its signature.
What it is
A configuration manager for MCP clients: 6 tools that locate a client's configuration file, read it whole or entry by entry, and add, overwrite or remove a server entry within it.
What you get
- The file's location before anything else:
get_configuration_pathreturns the path to the configuration file for a namedclient. - The whole file when you need the surrounding context:
get_configurationreturns a client's entire configuration. - A registry view rather than raw JSON:
list_serversreturns the server names configured in a client. - One entry at a time when that is all you need:
get_server_configurationreturns the configuration for a singleserver_namewithin a client. - Writes with the overwrite decision made explicit:
add_server_configurationtakes ajson_configfor aserver_nameplus anallow_overrideflag that decides whether an entry already there is replaced. - Removal by name:
remove_server_configurationtakes aclientand aserver_nameand deletes that entry.
Requirements
No account and no key. What it does need is filesystem access to the configuration file of the client you name, since the tools read from and write to that file directly.
Setup effort
One command — npx -y @landicefu/mcp-client-configuration-server
USE CASES
01
Registering a new server in a client's config
Find where that client keeps its configuration, write the entry, and read the registry back to confirm it landed.
02
Finding out what is already wired into a client
List the registered names, open the one you are unsure about, and read the whole file when the surrounding settings matter.
03
Removing a server you no longer want loaded
Confirm the exact registered name, read what it was set to in case you need it back, then delete the entry.
04
Copying a working setup between two clients
Read the entry out of the client where it already works and write it into the second client, choosing whether it may overwrite.
6 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_configuration
Get the entire configuration for a specific client
get_configuration_path
Get the path to the configuration file for a specific client
get_server_configuration
Get the configuration for a specific server from a client configuration
list_servers
List all server names configured in a specific client
remove_server_configuration
Remove a server configuration from a client configuration
BEFORE YOU INSTALL
What to know first
Tools you get
6 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 6 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-client-configuration-server": {
"command": "npx",
"args": [
"-y",
"@landicefu/mcp-client-configuration-server"
]
}
}
}npx
TERMINAL
npx -y @landicefu/mcp-client-configuration-server
