Skip to main content
Glama
crunchloop

MCP Devcontainers

by crunchloop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to MCP Devcontainers

No user-submitted related servers found.

    Related Servers

    • mcp-devcontainers

      AI-QL
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for generating and configuring development containers from devcontainer.json files, enabling management of devcontainer environments through tools like devcontainer_up, devcontainer_exec, and cleanup.
      19 npm
      8
      MIT

    • Docker MCP Server

      RodrigoUC
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables managing Docker containers through natural language commands, allowing users to create, list, and delete containers. It facilitates automated container orchestration and integrates with VS Code via the Cline extension.
      96 npm
      MIT

    • DevServer MCP

      Uninen
      A
      license
      Not graded
      quality
      F
      maintenance
      An MCP server that enables programmatic management and monitoring of development servers through a unified interface and interactive TUI. It provides tools for process control, log streaming, and experimental browser automation via Playwright.
      1
      MIT

    • Code MCP Server

      agentics-ai
      A
      license
      C
      quality
      D
      maintenance
      An experimental MCP server that enables AI assistants to interact with VS Code workspaces through file operations, code execution, and Git management. It also provides tools for Docker integration, project scaffolding, and secure command execution using project-specific configurations.
      76
      59 npm
      3
      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.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: starting the devcontainer, executing arbitrary commands, and running user-defined lifecycle scripts. No overlapping functionality.

    Naming Consistency5/5

    All tools follow the 'devcontainer_verb' pattern in snake_case (exec, run_user_commands, up). Naming is consistent and predictable.

    Tool Count4/5

    With 3 tools, the server is lean but covers core devcontainer operations. Could be slightly more comprehensive but appropriate for a focused utility.

    Completeness3/5

    The tool set covers starting, executing commands, and running lifecycle scripts, but misses common operations like stopping, rebuilding, or checking status, which are notable gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources