Coding Agents

Your coding agent reaches Planton through the Planton skills and the Planton MCP server, or through the CLI. It sits beside the tools you already use; nothing about how you work changes.

For the developer with Cursor, Claude Code, or Codex already open, and the platform engineer who wants that agent inside the same rules as everyone else.

How It Works

1

Install the Skills

One command installs the two Planton skills into every coding agent on your machine, in the open Agent Skills format.

2

Facts, Not Memory

Without the skills, an agent writes infrastructure from memory. With them, every fact comes from the catalog kind’s reference page at answer time.

3

The Same Door as Everyone

The agent deploys through the same door as a person in the console or a script on the CLI: the same catalog, the same rules, the same record.

4

The Platform Over MCP

An agent that wants to build, apply, deploy, or read your organization’s estate directly reaches those operations through the hosted MCP server, with the CLI or without it.

What You Get

Shipped behavior, stated as it works today.

Validated Before It Is Handed Over

The agent wires resources by reference instead of pasting IDs, validates the manifest, tells you the monthly cost, and asks before it applies.

The Same List, the Same Refusals

The catalog can be curated to the catalog kinds your organization allows. The console, the CLI, and the agent all see the same list and refuse the same things, because one answer serves both.

Lines the Agent Never Crosses

The skills say so in plain words: never change anything without asking, and never work outside your repository.

One Assistant, Every Surface

The same skills power the Planton Assistant in Planton Desktop and the web console, so your agent and the platform’s own assistant work from the same instructions.

.cursor/mcp.json

{  "mcpServers": {    "planton": {      "type": "http",      "url": "https://mcp.planton.ai/",      "headers": { "Authorization": "Bearer ${env:PLANTON_API_KEY}" }    }  }}

Teach your agent

npx skills add plantonhq/skillsbrew install plantonhq/tap/planton

The first line installs the two skills into every agent on the machine; the second is the CLI they drive; the file above is the optional MCP door. All three are from the Coding Agents guide.

Where This Is Proven

The same claims, written for the person who signs, with the record beside each one.

Rules and Approvals

Deployment budgets that pause a deploy, protected environments that refuse self-approval, a curated catalog, and sensitive fields that only take managed secrets.

What It Proves →

Verified Before Deploy

Before anything is created, Planton states the monthly cost with its coverage, the least-privilege permissions, and the controls each kind enforces.