Skip to main content
Glama
scarr7981

cargoshipper-mcp

by scarr7981
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to cargoshipper-mcp

No user-submitted related servers found.

    Related Servers

    • vps-mcp

      ereskovsky
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for managing VPS servers via SSH, enabling command execution, file transfer, Docker management, and server documentation from within Claude.
      10 npm
      ISC

    • Claude MCP Server Ecosystem

      Coder-RL
      F
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server ecosystem providing Claude AI with 150+ specialized tools across enhanced memory, data analytics, security, design, and infrastructure domains with PostgreSQL, Redis, Qdrant, and Docker orchestration.
      -

    • easypanel-mcp-server

      helbertparanhos
      A
      license
      B
      quality
      A
      maintenance
      MCP Server for full Easypanel control via Claude Code, Cursor, and Claude Desktop. Provides 37 tools for deploy, logs, env vars, domains, databases, and monitoring with built-in safety guards.
      57
      28 npm
      4
      MIT

    • infra-mcp

      odanree
      A
      license
      A
      quality
      D
      maintenance
      MCP server that wraps Docker, Caddy, and GitHub Actions operations on a remote VPS, enabling Claude to take read-then-write-with-confirmation infrastructure actions over SSH with a service allowlist and audit-trail-friendly responses.
      8
      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 21 tools

    Disambiguation4/5

    Tools are clearly disambiguated by their 'cf_' and 'docker_' prefixes, making it easy to distinguish between CloudFlare and Docker operations. However, the presence of two unrelated domains may confuse an agent about which set to use for a given task.

    Naming Consistency5/5

    All tool names follow a consistent pattern: prefix (cf_ or docker_) followed by verb_noun (e.g., cf_create_dns_record, docker_list_containers). No style mixing or vague verbs observed.

    Tool Count3/5

    21 tools is on the high side for a typical single-purpose server, though each subdomain (CloudFlare and Docker) has a reasonable count. The combined set feels heavy and could be split into separate servers for better coherence.

    Completeness3/5

    The CloudFlare tools cover core zone and DNS operations, while Docker tools cover basic container lifecycle. However, both lack advanced features (e.g., Docker networks, CloudFlare firewall rules), and the dual-domain focus leaves potential gaps in each area.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources