Skip to main content
Glama
4ears-me

Arcane MCP

by 4ears-me
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Arcane MCP

No user-submitted related servers found.

    Related Servers

    • Arcane Docker MCP Server

      cougz
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables managing Docker environments through Arcane via natural language, providing tools for containers, images, volumes, networks, and Docker Compose stacks.
      MIT

    • arcane-mcp

      MikeCase
      A
      license
      C
      quality
      D
      maintenance
      Exposes Arcane Docker management capabilities to AI agents, covering containers, images, volumes, networks, Compose projects, registries, vulnerability scanning, and more with 123 tools across 13 modules.
      100
      1
      MIT

    • gnosis-docker-mcp

      kordless
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Docker containers and images, including starting, stopping, listing, and building operations.
      2
      -

    • Arcane MCP

      jmagar
      A
      license
      Not graded
      quality
      A
      maintenance
      AI-powered Docker management server that enables natural language control of environments, containers, images, networks, volumes, and more through a unified Arcane API interface.
      2
      MIT

    • Docker MCP Server

      alisaitteke
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Docker containers, images, networks, volumes, and Compose services through the Model Context Protocol. It supports system operations, command execution within containers, and integration with Docker Hub and GitHub Container Registry.
      61 npm
      2
      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 52 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action combination, with clear separation across environments, containers, images, volumes, networks, projects, and system operations. Even similar prune operations are differentiated by the resource type (images, volumes, networks, system).

    Naming Consistency5/5

    All 52 tools follow the exact pattern 'arcane_<verb>_<noun>' in lowercase snake_case, with verbs always placed first (e.g., list, get, create, update, delete, start, stop, prune). No mixed styles or inconsistent verb usage.

    Tool Count3/5

    At 52 tools, the count is high and exceeds typical thresholds, but the server's scope is broad, covering full lifecycle management for multiple resource types. The number feels heavy but justified; some consolidation could reduce it without losing functionality.

    Completeness4/5

    The tool surface provides robust CRUD and lifecycle coverage for all major resource types, including specialized features like volume backups and file browsing. Minor gaps exist (e.g., container logs, network connect), but these do not hinder core container management workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources