Skip to main content
Glama

DeployForge MCP

Agent-controlled deployment stack built on Pier.

Stack

Layer

Tool

Version

PaaS

Pier

v1.0.0

Language

Rust

1.91.1

Container runtime

Docker Engine

29.6.1

Compose

Docker Compose

5.3.1

Reverse proxy

Traefik

v3.7.1

Buildkit

moby/buildkit

latest

Auto-builder

Railpack

v0.35.0

Agent interface

pier-mcp

v0.1.0 (planned)

Related MCP server: Enterprise MCP Server

Documentation

Status

Pier installed and running. Admin account created. Port 80 occupied by existing container (diamond-access-ai). Pier panel on port 8443.

pier-mcp

MCP server scaffolded with 14 initial tools mapped to Pier REST API endpoints.

  • Location: /root/deployforge-mcp/pier-mcp/

  • Transport: stdio (local), Streamable HTTP (remote)

  • Auth: Bearer token via PIER_TOKEN environment variable

Quick Start

cd /root/deployforge-mcp/pier-mcp
npm install
npm run build
PIER_TOKEN=$(cat .env | grep PIER_TOKEN | cut -d= -f2) npm start

Or source the env:

source .env
npm start

Available Tools

14 tools
pier_delete_appA

Permanently delete an app and all its resources. This is UNRECOVERABLE — all data, config, and volumes are destroyed.

Inputs: appId (required).

pier_deploy_serviceA

Trigger a new deployment for an app. Rebuilds and restarts the container from its configured source (Git, Dockerfile, Compose, or image).

Inputs: appId (required).

pier_get_app_statusA

Check the current status of an app — whether it is running, stopped, or deploying, plus its public endpoints. Use this to health-check an app or discover its URLs.

Inputs: appId (required).

pier_get_container_logsB

Fetch logs from a specific Docker container. Requires the container ID.

Inputs: containerId (required), tail.

pier_get_env_varsA

Read the full set of environment variables for an app.

Inputs: appId (required).

pier_get_logsB

Fetch recent deployment logs for an app. Optionally limit to the last N lines.

Inputs: appId (required), tail.

pier_get_system_metricsA

Get server-level metrics: CPU, RAM, disk, and network usage.

Inputs: no named parameters.

pier_list_appsA

List all apps/services deployed on the Pier server. Returns an array of services with IDs, names, status, and URLs. Call this first to discover app IDs, then use those IDs for all other operations.

Inputs: page, pageSize.

pier_list_containersA

List all Docker containers on the server, including Pier-managed and standalone containers.

Inputs: no named parameters.

pier_rename_appA

Change the display name of an app.

Inputs: name (required), appId (required).

pier_set_env_varsA

Replace the entire environment variable set for an app. Any existing variables not included in the new array will be deleted. For a single variable change, use update_env_var instead.

Inputs: appId (required), envVars (required).

pier_start_or_restart_appA

Start a stopped app, or restart a running one. Recreates the container — all non-volume state is lost. Use after ANY config change (env vars, ports, image, command) for the change to take effect.

Inputs: appId (required).

pier_stop_appA

Stop an app and remove its container. Persistent volumes are kept. Temporary teardown — restart later with start_or_restart_app.

Inputs: appId (required).

pier_update_env_varA

Add or update a single environment variable without affecting other variables. Preferred over set_env_vars for individual changes.

Inputs: name (required), appId (required), value (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers