mcp-omnienv-nix
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_languagesB | List supported languages and their base Nix packages. |
| run_in_env_implC | Run a shell command in a disposable Nix shell for the chosen language. |
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 2 tools
The two tools have clearly distinct purposes: list_languages enumerates available options, while run_in_env_impl executes commands in a specific environment. There is no overlap or ambiguity between them.
The naming is mixed: list_languages follows a verb_noun pattern, but run_in_env_impl uses a less conventional verb_in_noun_impl style. While readable, the inconsistency in naming conventions is noticeable.
With only 2 tools, the server feels thin for its apparent scope of managing language environments in Nix. A typical server in this domain would include more operations like creating, updating, or inspecting environments, making this count borderline inadequate.
The toolset is severely incomplete for managing Nix language environments. It lacks essential operations such as creating, updating, or deleting environments, and provides no way to inspect or modify specific environment configurations, leaving significant gaps in coverage.