Skip to main content
Glama
N1jada

pterodactyl-mcp

by N1jada
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to pterodactyl-mcp

No user-submitted related servers found.

    Related Servers

    • Pufferfish-MCP

      BSpoones
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to control Coral/Pufferfish game panels by managing power, console commands, files, backups, SFTP transfers, and server listings across multiple panels via the Coral client API.
      -

    • pebblehost-mcp

      bop-del
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language management of Pebblehost Minecraft servers, including server status, control, console commands, file management, and backups.
      MIT

    • Minecraft Server MCP

      Ver-zhzh
      A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to interact with and manage Minecraft servers through a standardized interface, supporting server monitoring, player management, log analysis, and command execution.
      11
      MIT

    • OpenCraft

      vulnix0x4
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients like Codex and Claude Code to manage Minecraft servers through the Exaroton API, including status, logs, crash diagnostics, player management, and guarded server actions with confirmation.
      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.3/5.0

    Scored across 20 tools

    Disambiguation5/5

    Every tool targets a distinct resource and action: server listing, configuration, live resources, console, power, files, backups, schedules, and startup variables are all cleanly separated. Potentially confusing pairs like ptero_get_server vs ptero_get_server_resources and ptero_get_console_log vs ptero_read_file are explicitly differentiated in their descriptions.

    Naming Consistency5/5

    All tools follow a uniform ptero_ prefix followed by a verb_noun pattern (list_servers, get_server, write_file, set_power_state, create_backup, get_backup_download_url). The convention is perfectly consistent across all 20 tools with no mixed styles or vague verbs.

    Tool Count3/5

    At 20 tools, the server is on the heavy side for its scope, covering server info, power, console, files, backups, schedules, allocations, and startup variables. The count is justified by the breadth of the domain, but it feels dense compared to typical well-scoped servers.

    Completeness3/5

    Core workflows are well covered: full file CRUD (list/read/write/upload/rename/copy/delete), backup lifecycle (list/create/delete/download), power control, console read/write, and configuration introspection. However, schedules are read-only with no create/edit/delete, and startup variables and allocations cannot be mutated, leaving notable gaps for agents that need to modify server configuration.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources