Skip to main content
Glama
Sign In
aptible-mcp

aptible-mcp

Official
by aptible
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to aptible-mcp

No user-submitted related servers found.

    Related Servers

    • @vertracloud/mcp

      @vertracloud/mcpofficial

      vertracloud
      A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to operate Vertra Cloud resources through the public API: deploy and manage applications, view logs and metrics, create and restore snapshots, and administer databases and environment variables.
      138
      476 npm
      2
      MIT

    • Datadog MCP Server

      ppandrangi
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Datadog APIs through natural language, supporting full CRUD operations on metrics, monitors, dashboards, logs, infrastructure, and more.
      4
      MIT
    • Lizard MCP

      Lizard MCPofficial

      lizard-build
      A
      license
      A
      quality
      B
      maintenance
      Run code in Lizard Sandboxes on Lizard (lizard.build). Provides 89 MCP tools, including 17 sandbox tools for commands, files, pause/resume, snapshots, forks and HTTPS ports, plus app, database and Git tools. Connect over Streamable HTTP with OAuth or your own API key. Cloud usage is billed; see lizard.build/pricing.
      89
      3
      MIT

    • Pylon MCP Server

      gasconc
      A
      license
      B
      quality
      D
      maintenance
      Enables interaction with the Pylon API for managing accounts, issues, messages, and custom fields through natural language.
      36
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    B3.1/5.0

    Scored across 38 tools

    Disambiguation4/5

    Most tools are clearly distinct by resource and action, such as createApp, deleteDatabase, and listStacks. The only minor overlap is between listVhosts and listServiceVhosts, and getAccountsByStack vs listAccounts, but descriptions clarify the intended scope.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (list, get, create, delete, configure, scale) with no mixed conventions or vague verbs. Examples like getAppProvisionExample still fit the pattern as get + resource + Example.

    Tool Count2/5

    With 38 tools, the surface is quite large and exceeds the 25+ threshold. While the domain is broad (accounts, apps, databases, vhosts, services, operations, examples), the sheer number feels heavy and could overwhelm agents, especially with 10 example template tools.

    Completeness3/5

    Core resources have CRUD coverage, but there are notable gaps: no update/delete for accounts, no database backup or restore operations, and no app logs. The example tools provide templates but don't fill operational dead ends, so agents may need to work around missing lifecycle features.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources