Schema | dev-env-mcp

dev-env-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

Features and capabilities supported by this server

Capability	Details
`tools`	{ "listChanged": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`experimental`	{}

Functions exposed to the LLM to take actions

Name	Description
workspace_useA	Select the project/workspace to manage. 'path' can be a repo root or any subdirectory inside a repo. The server will auto-find the workspace root by walking up to pyproject.toml or .git. All future operations (env_create/pip/freeze) are sandboxed to this workspace.
env_createA	Create a venv inside the active workspace (default: .venv) and set it active.
env_useC	Use an existing venv inside the active workspace and set it active.
pipA	Run a restricted pip action inside the active venv. Parameters: action: install \| uninstall \| list \| show \| check packages: list of packages/specs (e.g. ["requests", "numpy==2.1.0"]) options: allowlisted pip options only (see server policy) confirm: required for uninstall (safety)
freezeC	Write pinned requirements from the active venv to a file in the workspace.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Tova501/Dev-Env-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server