keyshade-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KEYSHADE_API_KEY | Yes | Your Keyshade API key |
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 |
|---|---|
| health_checkA | Check if the Keyshade API is healthy |
| get_userA | Get current user information |
| list_workspacesB | Lists all accessible Keyshade workspaces with pagination support |
| get_workspaceA | Gets details for a specific Keyshade workspace |
| list_projectsA | Lists all projects within a specific Keyshade workspace |
| get_projectA | Gets details for a specific Keyshade project |
| list_environmentsB | Lists all environments within a specific Keyshade project |
| get_environmentA | Gets details for a specific Keyshade environment |
| list_secretsB | Lists all secrets within a specific Keyshade project |
| list_secrets_in_environmentA | Lists all secrets within a specific environment |
| list_variablesB | Lists all variables within a specific Keyshade project |
| list_variables_in_environmentA | Lists all variables within a specific environment |
| list_api_keysB | Lists all API keys for the current user |
| get_api_keyC | Gets details for a specific API key |
| get_workspace_eventsC | Gets events for a specific workspace |
| list_workspace_rolesC | Lists all roles within a specific workspace |
| list_workspace_membersB | Lists all members of a specific workspace |
| global_searchB | Performs a global search within a workspace |
| create_workspaceC | Creates a new workspace in Keyshade |
| create_projectC | Creates a new project in a workspace |
| fork_projectC | Forks an existing project |
| create_environmentC | Creates a new environment in a project |
| create_secretC | Creates a new secret in a project |
| create_variableC | Creates a new variable in a project |
| create_workspace_roleC | Creates a new workspace role |
| delete_environmentC | Deletes an environment in a project |
| delete_projectC | Deletes a project |
| unlink_fork_parentC | Unlinks a forked project from its parent project |
| delete_secretC | Deletes a secret from a project |
| delete_secret_environment_valueC | Deletes an environment-specific value of a secret |
| delete_variableC | Deletes a variable from a project |
| delete_variable_environment_valueC | Deletes an environment-specific value of a variable |
| delete_workspaceC | Deletes a workspace |
| delete_workspace_roleC | Deletes a workspace role |
| leave_workspaceC | Leaves a workspace |
| update_environmentC | Updates an environment in a project |
| update_projectC | Updates a project |
| sync_forkB | Syncs a forked project with its parent |
| update_secretC | Updates a secret in a project |
| rollback_secretC | Rolls back a secret to a previous version |
| update_variableC | Updates a variable in a project |
| rollback_variableC | Rolls back a variable to a previous version |
| update_workspaceC | Updates a workspace |
| update_workspace_roleC | Updates a workspace role |
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 44 tools
Tools are mostly distinct with clear purposes, but some pairs like list_secrets and list_secrets_in_environment could cause minor confusion despite descriptions.
All tool names follow a consistent verb_noun or verb_noun_noun pattern using lowercase snake_case, with no mixing of conventions.
At 44 tools, the server is on the high side; while many operations are justified by the complexity of keyshade management, some tools may be redundant or could be consolidated.
Covers most CRUD operations for core entities, but lacks create/delete/update for API keys and workspace members, which are notable gaps.