Planton MCP Server

A stateless MCP server that connects AI-powered IDEs to Planton. It translates MCP tool calls and resource reads into gRPC requests against the Planton backend, letting Cursor, Claude Desktop, VS Code, Windsurf, and any MCP-compliant client manage cloud resources across 17 cloud providers without leaving the editor — from discovering organizations and environments through creating, listing, and destroying resources to observing provisioning outcomes via stack jobs.

flowchart TD
    IDE["AI IDE\n(Cursor / Claude Desktop / VS Code / Windsurf)"]
    MCP["mcp-server-planton\n(stdio or Streamable HTTP)"]
    Backend["Planton Backend\n(gRPC · TLS on :443)"]
    IDE -->|"MCP protocol"| MCP
    MCP -->|"gRPC"| Backend

This server does not store state. It is a protocol bridge: every tool call opens a short-lived gRPC connection, performs the RPC, and returns the result. It can serve both STDIO and HTTP transports concurrently from a single process.

Key Concepts

| Term | Definition | |------|------------| | cloud resource | Any infrastructure component managed by Planton (e.g. an EKS cluster, a GCP VPC, an Azure database). | | kind | PascalCase type identifier for a cloud resource (e.g. AwsEksCluster, GcpCloudSqlInstance). | | org | Organization identifier -- the tenant-level namespace that owns a resource. | | env | Environment identifier (e.g. production, staging). | | slug | URL-safe unique name for a resource within an (org, env, kind) scope. | | api_version | Versioned API namespace for a cloud provider (e.g. ai.planton.provider.aws.v1). | | apply | Idempotent create-or-update. Same semantics as kubectl apply -- if the resource exists it is updated, otherwise it is created. |

Installation

Prerequisites

1. A Planton account
2. An API key (Console > Profile > API Keys > Create Key)
3. A compatible MCP host (Cursor, Claude Desktop, VS Code, Windsurf, or any MCP-compliant client)

Go Install

go install github.com/plantonhq/mcp-server-planton/cmd/mcp-server-planton@latest

Pre-built Binary

# macOS (ARM64)
curl -L https://github.com/plantonhq/mcp-server-planton/releases/latest/download/mcp-server-planton_Darwin_arm64.tar.gz | tar xz
sudo mv mcp-server-planton /usr/local/bin/

# macOS (Intel)
curl -L https://github.com/plantonhq/mcp-server-planton/releases/latest/download/mcp-server-planton_Darwin_x86_64.tar.gz | tar xz
sudo mv mcp-server-planton /usr/local/bin/

# Linux (AMD64)
curl -L https://github.com/plantonhq/mcp-server-planton/releases/latest/download/mcp-server-planton_Linux_x86_64.tar.gz | tar xz
sudo mv mcp-server-planton /usr/local/bin/

Docker

docker run -i --rm \
  -e PLANTON_API_KEY=your-api-key \
  ghcr.io/plantonhq/mcp-server-planton

Docker networking: localhost inside a container refers to the container's own loopback, not the host machine. To reach a custom endpoint running on the host, use host.docker.internal on Docker Desktop (macOS / Windows) or add --network host on Linux.

MCP Client Configuration

All MCP clients use the same JSON structure. The differences are the config file location and the top-level key.

Using the standalone binary or Go install

{
  "mcpServers": {
    "planton": {
      "command": "mcp-server-planton",
      "env": {
        "PLANTON_API_KEY": "YOUR_PLANTON_API_KEY"
      }
    }
  }
}

Using Docker

{
  "mcpServers": {
    "planton": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-e", "PLANTON_API_KEY",
        "ghcr.io/plantonhq/mcp-server-planton"
      ],
      "env": {
        "PLANTON_API_KEY": "YOUR_PLANTON_API_KEY"
      }
    }
  }
}

Where to put the config

| Client | Config file | Top-level key | |--------|-------------|---------------

... View full README on GitHub