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
F
license - not found
-
quality - not tested
C
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

View all related MCP servers

Related MCP Connectors

  • MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.

  • The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.

  • A MCP server built for developers enabling Git based project management with project and personal…

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kore4lyf/pier-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server