# Plansmith MCP server

Give a coding agent the plan it is meant to build from. Hosted is read-only; the local server adds the write tools.



## Hosted [#hosted]

```json
{
  "mcpServers": {
    "plansmith": {
      "url": "https://mcp.plansmith.co"
    }
  }
}
```

Your client discovers how to authorize on its own and sends you to a consent screen the first time.
Nothing to paste.

## Local [#local]

```json
{
  "mcpServers": {
    "plansmith": {
      "command": "plansmith",
      "args": ["mcp"]
    }
  }
}
```

Runs on your machine and reuses the session from `plansmith auth`. Useful when the agent is already
local and you would rather not authorize a second connection.

## What the agent can do [#what-the-agent-can-do]

Read the plan and build from it: list projects and plans, pull a whole plan tree in one call, read a
Spec with its numbered acceptance criteria, and export a plan as markdown.

The hosted server is read-only in v1. To let an agent create plans and Specs, set a status, write an
epic, attach context or push to your issue tracker, run the local server instead: it acts under the
session you just created rather than a connection you authorized months ago.

<Callout>
  An agent connected this way acts as you. It can reach exactly the plans you can reach, and a
  read-only credential can never change anything. Revoke a connection any time in Settings → API keys.
</Callout>

## A good first prompt [#a-good-first-prompt]

```text
Read PLAN-12 in the recipe-box project from Plansmith and
implement SPEC-1, following its acceptance criteria exactly.
```