local-kms-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port used only when TRANSPORT=http | 8080 |
| TRANSPORT | No | MCP transport: stdio or http | stdio |
| STORE_PATH | No | Directory used for persisted key files | ./keys |
| ENCRYPT_STORE | No | Set to true or 1 to encrypt key files at rest | false |
| STORE_ENCRYPTION_KEY | No | Base64-encoded 32-byte key required when encryption is enabled |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_keypairA | Check if a key pair exists for the given key ID |
| get_key_infoB | Get the key pair information for the given key ID |
| list_algorithmsA | List all supported signing algorithms |
| list_keysA | List all key pairs in the key store |
| generate_keyA | Generate and store a new key pair for the given key ID |
| rotate_keyB | Rotate the key pair for the given key ID, preserving the existing algorithm |
| delete_keyB | Delete a key pair from the keystore |
| sign_messageB | Sign a base64-encoded message with the stored private key |
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 8 tools
Each tool has a distinct purpose: checking existence, deleting, generating, getting info, listing algorithms, listing keys, rotating, and signing. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case, such as generate_key, list_keys, rotate_key, etc. No deviations.
8 tools is within the ideal range (3-15) for a KMS server, covering key lifecycle and signing without bloat or scarcity.
The tool set covers key generation, deletion, rotation, listing, info retrieval, and signing. Missing encrypt/decrypt or import/export, but core key management is well-covered for a signing-focused KMS.