Skip to main content
Glama
sparfenyuk

venv-mcp-server

by sparfenyuk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to venv-mcp-server

No user-submitted related servers found.

    Related Servers

    • uv-mcp

      yriveiro
      A
      license
      B
      quality
      B
      maintenance
      MCP server enabling AI assistants to inspect and manage Python environments via uv, including package management, virtual environments, Python versions, tools, and security auditing.
      50
      Apache 2.0

    • ipykernel-mcp

      0x0L
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that manages an IPython kernel, allowing LLMs to execute Python code in a project's virtual environment.
      8
      2
      MIT

    • dev-env-mcp

      Tova501
      F
      license
      A
      quality
      D
      maintenance
      A local MCP server that provides a safe, structured way to manage Python environments inside a project workspace, including virtual environment creation, restricted pip operations, and dependency freezing.
      5
      -

    • venv-manager

      jacopobonomi
      A
      license
      Not graded
      quality
      A
      maintenance
      Python venv runtime for AI agents. MCP server exposing list/create/describe/install/run/exec/snapshot/rollback/scan as typed tools
      50
      MIT

    • mcp-python-repl

      aazizisoufiane
      A
      license
      A
      quality
      D
      maintenance
      A production-grade MCP server providing a persistent Python REPL with multi-session support, sandboxing, and timeout protection, enabling LLM agents to execute Python code across multiple turns with variables that persist between calls.
      12
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: init, add/remove packages (singular/plural), sync, and run commands. No overlap or ambiguity.

    Naming Consistency4/5

    All tools use snake_case and follow a verb_noun pattern (add_package, remove_package, run_in_venv), but 'init' and 'sync' are single words, which is a minor deviation.

    Tool Count5/5

    6 tools cover the essential operations for virtual environment management (init, add, remove, sync, run). No excess or deficiency.

    Completeness4/5

    Covers core workflows: init, add/remove packages, sync, run commands. Missing operations like listing installed packages or updating packages, but not critical.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources