Skip to main content
Glama
nunombispo

dokku-mcp

by nunombispo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to dokku-mcp

No user-submitted related servers found.

    Related Servers

    • VPS Docker MCP (Advanced)

      mordanov
      F
      license
      B
      quality
      B
      maintenance
      Enables safe VPS diagnostics and Docker/Docker Compose management over SSH, providing predefined read-only and mutating tools for system monitoring, container inspection, and Compose orchestration without exposing arbitrary shell execution.
      26
      -

    • infra-mcp

      Phloraxx
      F
      license
      Not graded
      quality
      B
      maintenance
      Securely inspect and operate self-hosted infrastructure including Linux host health, Docker containers and logs, Dokploy deployments, and OCI resources through a narrowly scoped, auditable MCP gateway.
      -

    • ssh-mcp-server

      yuyi-clip
      F
      license
      B
      quality
      B
      maintenance
      A structured SSH management service that exposes command execution, file transfer, background jobs, GPU monitoring, systemd operations, and port forwarding as MCP tools with strict security and explicit input schemas.
      19
      1
      -

    • SSH Nexus MCP

      faridarjmand
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to list SSH hosts, test reachability, retrieve Linux resource metrics, index and search project files, and run remote SSH commands when allowed, with local-first and safety-focused operations.
      MIT

    • MCP-Server-Agent

      domwokorach
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables secure remote management of the platform through nine MCP tools over STDIO and HTTP, including terminal execution, service controls, and live status monitoring.
      398 npm
      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

    A3.9/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools are clearly distinct: list_apps is the only app-level listing, app_report/app_config/app_logs/app_domains/app_url each target a different aspect of an app, and the write tools (create_app, set_config, restart_app, scale_app) have distinct actions. The only mild overlap is app_domains vs app_url, since app_url is a convenience wrapper over domains:report, but the descriptions make the relationship clear.

    Naming Consistency4/5

    The naming pattern is mostly consistent: read operations use app_* (app_report, app_config, app_logs, app_domains, app_url) plus list_apps, and write operations use verb_app (create_app, set_config, restart_app, scale_app). The minor inconsistency is that list_apps breaks the app_* pattern and set_config/restart_app/scale_app use verb_app rather than app_verb, but the overall convention is still predictable.

    Tool Count5/5

    10 tools is well-scoped for a Dokku MCP server. The read-only surface covers the most common inspection needs (list, report, config, logs, domains, URL), and the write surface covers the core app lifecycle operations (create, config, restart, scale). No tool feels redundant or unnecessary.

    Completeness4/5

    The tool surface covers the primary Dokku workflows: listing/creating apps, inspecting app state/config/logs/domains, updating config, restarting, and scaling. Obvious gaps include app deletion, app destruction, and process management (e.g. ps:scale is covered but ps:restart is not), but these are reasonable omissions for a safe MCP server and agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources