add_credential
Add a new credential to the store
LABSCO SUMMARY
Minimal exposure by default, tokens only on request.
Listing returns ids and app names; the access token comes back only from get_credential_details, so the model does not carry secrets it has no use for. Write access stays off until an environment variable is changed, which makes a destructive call a configuration decision rather than an accident.
What it is
A local credential store exposed over MCP. Credentials live in ~/.credential-manager-mcp/credentials.json, and the server is read-only by default: the write tools work only once you turn them on.
What you get
- Stored credentials listed with the id and app name, and the username only when several entries share an app (list_credentials)
- One credential returned in full, access token included, when a call actually needs it (get_credential_details)
- Credentials added, updated and deleted once write mode is on (add_credential, update_credential, delete_credential)
- Read-only by default: CREDENTIAL_MANAGER_READ_ONLY has to be set to false before anything can change
- Fresh reads from disk on every call, so several clients can share one store
- A shell script for adding credentials outside the agent, interactively or from the command line
Requirements
A recent Python and uvx, then uvx credential-manager-mcp. Set CREDENTIAL_MANAGER_READ_ONLY to false if you want the write tools.
Setup effort
One command — uvx credential-manager-mcp
USE CASES
01
Letting an agent call an API without pasting a key into the chat
It looks up the entry, then pulls the token only for the call that needs it.
02
Finding out which services you have keys stored for
List the store and read back ids and app names only.
03
Adding a key you just generated
Store the app, base URL, token and expiry in write mode.
04
Rotating a token that expired
Check the stored entry, then update it in place.
05
Taking access away again
Delete the credential from the store.
5 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
delete_credential
Delete a credential from the store
get_credential_details
Get detailed information about a specific credential including the access token
list_credentials
List all stored credentials with essential data (id, app name, and username only if multiple apps)
update_credential
Update an existing credential
BEFORE YOU INSTALL
What to know first
Tools you get
5 tools when we connected. CREDENTIAL_MANAGER_READ_ONLY defaults to true, exposing only list_credentials and get_credential_details; set it to false for add_credential, update_credential and delete_credential.
Requires
uvx on PATH
Where it runs
Both documented setups run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 5 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx credential-manager-mcpMCP Clients
Claude Desktop — uvx
CLAUDE DESKTOP — UVX · JSON
{
"mcpServers": {
"credential-manager": {
"command": "uvx",
"args": [
"credential-manager-mcp"
],
"env": {
"CREDENTIAL_MANAGER_READ_ONLY": "false"
}
}
}
}Claude Desktop — from source
CLAUDE DESKTOP — FROM SOURCE · JSON
{
"mcpServers": {
"credential-manager": {
"command": "uv",
"args": [
"--directory",
"<YOUR_PATH_TO_CREDENTIAL_MANAGER_MCP>",
"run",
"credential-manager-mcp"
],
"env": {
"CREDENTIAL_MANAGER_READ_ONLY": "false"
}
}
}
}
