MCP-native plan publishing

Plans your agents can come back to.

Publish implementation plans from any coding agent. PlanStack returns a stable public URL and preserves every revision as an immutable version.

ONE LINK

Publish v1. Tighten the approach. Publish v2. The URL stays put.

LIVE PLAN LEDGER MCP CONNECTED

AGENT CALL

publish_plan

title: "Billing refactor"

content: "## Approach…"

✓ PUBLISHEDv1
update_plansame plan · new immutable version
WORKS WITHClaude CodeCursorCodexWindsurfAny MCP client

The plan lifecycle

One artifact. Useful at every handoff.

  1. 01 / PUBLISH

    Your agent makes the plan durable.

    One MCP call turns temporary chat output into a readable, addressable artifact.

    publish_plan
  2. 02 / REVIEW

    Your team reads it without setup.

    No account, client, or copied markdown. Send the public link and keep the discussion anchored.

    /p/k3f9qm2p
  3. 03 / VERSION

    Revisions add history, not ambiguity.

    Every update creates a permanent version. The latest stays obvious; the past stays available.

    ?v=1 → ?v=2
  4. 04 / RE-CONSUME

    The next agent starts with context.

    Fetch a plan back over MCP so another tool can continue from the same source of truth.

    get_plan

Private access

Give every plan a permanent place.

Join the waitlist

Invites open in small batches.