Native Model Context Protocol (MCP) Runtime

Empower Claude Code, Cursor, and Windsurf to deploy and manage containerized infrastructure without giving them unchecked root bash access.

Why MCP Matters for Infrastructure

Traditional self-hosted PaaS tools (like Coolify or Portainer) were designed for human clicks inside browser dashboards. Giving an AI coding agent access to infrastructure by having it script SSH commands with root privileges is extremely dangerous: a single hallucinated rm -rf, unquoted variable, or unverified flag can bring down production databases or expose root sockets.

Smoooth is engineered from scratch around Anthropic's open Model Context Protocol (MCP) standard. The Smoooth daemon exposes a suite of strongly-typed, JSON-schema-validated tools that coding agents can invoke natively inside their conversation context.

Typed MCP Tool Inventory

# 1. Inspect host resources and container states
smoooth.inspect_host() → { cpus: 2, mem_total_mb: 4096, mem_free_mb: 3200 }

# 2. Dry-run execution plan validation
smoooth.create_plan({
  name: "saas-app",
  containers: [{ image: "my-app:v1", port: 3000 }],
  databases: [{ type: "postgres", version: "16", volume: "pgdata" }]
}) → { plan_id: "plan_948a", changes: 3, rollback_safe: true }

# 3. Transactional execution with automatic rollback
smoooth.execute_plan({ plan_id: "plan_948a" }) → { status: "committed", ingress_url: "https://app.com" }

Transport Flexibility

Smoooth supports two standard MCP transport channels:

• Standard I/O (stdio): For local development or remote SSH tunnel execution via smoooth mcp run.
• Server-Sent Events (SSE / HTTP): For remote agents pairing over an authenticated, encrypted loopback tunnel with scoped bearer tokens.

← Return to Features Overview · Read the Claude Code Tutorial →