env-mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| env_getC | Get an environment variable value |
| env_setC | Set an environment variable |
| env_deleteC | Delete an environment variable |
| env_searchC | Search environment variables |
| env_listA | List all environment variables or by category |
| env_exportC | Export environment variables |
| env_importC | Import environment variables from file |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| All Environment Variables | Access all 0 environment variables |
TDQS
Scored across 7 tools
Each tool has a clear, distinct action (delete, export, get, import, list, search, set) on environment variables, with no overlapping functionality.
All tools follow the consistent pattern 'env_<verb>' using snake_case, making them predictable and easy to distinguish.
With 7 tools covering CRUD, listing, searching, export, and import, the count is well-scoped for environment variable management.
The tool set covers all essential operations (create/set, read/get, update/set, delete/list/search, plus import/export), leaving no obvious gaps for typical workflows.