Skip to main content
Glama
rvforest

nox-mcp

by rvforest
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to nox-mcp

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

    • terminal-bridge-mcp

      dividduang
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that bridges AI assistants to real terminal sessions, enabling creation, management, and interaction with persistent PTY processes for running commands, monitoring output, and debugging.
      1
      MIT

    • gotask-mcp

      PaddyAlton
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables AI agents to list and run tasks defined in Taskfile.yml, useful for automated development workflows.
      2
      4
      MIT

    • mcp-creator

      gmoneyn
      A
      license
      A
      quality
      C
      maintenance
      A tool that enables AI assistants to conversationally scaffold, build, and publish Python MCP servers to PyPI. It automates the entire development lifecycle, including package naming, tool scaffolding, GitHub repository setup, and package publishing.
      10
      MIT

    • linux-ssh-mcp

      JINDEZHIDIYE
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables AI assistants to manage SSH terminal sessions, execute commands, and automate server operations through natural language, with multi-tab support and session persistence.
      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

    A4.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one lists available sessions, the other runs them. There is no overlap or ambiguity.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern with 'nox_' prefix (nox_list_sessions, nox_run_session), making them predictable and easy to understand.

    Tool Count4/5

    With only 2 tools, the server is minimal but appropriately scoped for listing and running nox sessions. It covers the essential interactions without unnecessary complexity.

    Completeness5/5

    The tool set is complete for its intended purpose: discovering available sessions and executing them. There are no missing operations since sessions are defined externally in noxfiles.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources