Skip to main content
Glama
kore4lyf

pier-mcp

by kore4lyf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to pier-mcp

No user-submitted related servers found.

    Related Servers

    • vito-mcp

      xerxes-on
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server wrapping the full VitoDeploy REST API to manage projects, servers, sites, databases, services, workers, SSL, DNS, and more through any MCP-compatible agent, with 108 tools covering every endpoint.
      MIT

    • Havlio

      kanduit-lab
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Self-hosted PaaS MCP server providing a write-capable control plane with over 100 tools to deploy, roll back, manage domains, and administer infrastructure, while ensuring agent permissions never exceed human RBAC.
      -

    • hermes-mcp

      Stratfiy
      F
      license
      A
      quality
      C
      maintenance
      MCP server for controlling a Hermes agent deployment via its HTTP API, enabling health checks, log retrieval, task management, and deployment configuration from MCP clients.
      17
      -

    • yala

      MalekYala
      A
      license
      A
      quality
      C
      maintenance
      MCP server exposing 570 config-driven dev tools across plan, develop, QA, feedback automation, and deploy stages, with meta-tools for searching and running them via natural language.
      4
      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.8/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools target a distinct app or environment action, and descriptions explicitly clarify differences such as set_env_vars vs update_env_var. However, start_or_restart_app vs deploy_service and get_logs vs get_container_logs are close enough that an agent could misselect without careful reading.

    Naming Consistency5/5

    All tools share the pier_ prefix and follow a consistent verb_noun snake_case pattern (list/get/start/stop/delete/rename/set/update + noun). Minor noun choices like service vs app don't break the predictable pattern.

    Tool Count5/5

    14 tools is within the ideal range and each operation covers a distinct administrative need: app lifecycle, environment variables, logs, and server/container visibility. The count feels complete without bloating the surface.

    Completeness3/5

    The set covers app lifecycle management well: list, status, start/stop/restart, delete, rename, deploy, env vars, and logs. However, there is no explicit create-app operation and no way to update core app configuration such as ports, image, or command, which is a notable gap for a deployment server.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources