Skip to main content
Glama
vovayartsev-dice

devcontainer-mcp

by vovayartsev-dice
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to devcontainer-mcp

No user-submitted related servers found.

    Related Servers

    • Bash MCP Server

      NimbleBrainInc
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables the execution of arbitrary bash commands and returns detailed output including stdout, stderr, and exit codes. It supports customizable working directories, execution timeouts, and environment variable configurations.
      1
      MIT

    • Shell Server

      joandiazcapell
      F
      license
      A
      quality
      D
      maintenance
      A lightweight MCP server that provides AI assistants with access to a system's terminal through a secure terminal tool. It enables users to execute shell commands and receive stdout, stderr, and exit codes directly within an MCP-compatible client.
      1
      -

    • machine-root-mcp

      tusharnain
      A
      license
      Not graded
      quality
      B
      maintenance
      A self-hosted MCP server that gives AI coding assistants direct shell access to your local machine, enabling execution of arbitrary bash commands for development workflows.
      2,360 npm
      -

    • mcp-stdio

      Balneario-de-Cofrentes
      A
      license
      Not graded
      quality
      C
      maintenance
      A minimal, zero-dependency MCP server that enables defining and running tools over stdio transport, without extra features like HTTP or resources.
      29 npm
      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

    A4.2/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no ambiguity between tools. The single 'bash' tool is clearly defined for running commands inside a devcontainer.

    Naming Consistency5/5

    With only one tool named 'bash', naming is trivially consistent. The name is simple and lowercase, which is fine for a single tool.

    Tool Count3/5

    The server has only one tool, which feels thin for a server named 'devcontainer-mcp'. Most devcontainer workflows involve more than just running commands, so the count is borderline low.

    Completeness3/5

    The server covers only shell execution inside a devcontainer. While this is core functionality, it lacks tools for container lifecycle management (start, stop, config), leaving notable gaps for typical devcontainer use.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources