Planner MCP — provable "done" for AI agents

by planner.monopoly-gold.com · com.monopoly-gold.planner/mcp

Goal and task planning MCP for Codex and AI agents, with evidence-backed completion.

OnlineRemote
Category
Productivity
Connection
Remote (HTTP)
Tools
43 reported
Status
Online

Connect it to your AI

Claude Code

claude mcp add --transport http mcp https://planner.monopoly-gold.com/_mcp

Claude, ChatGPT, Cursor and other apps

Add it as a custom connector with this URL (Streamable HTTP):

https://planner.monopoly-gold.com/_mcp

Cursor, VS Code and other apps (mcp.json)

{
  "mcpServers": {
    "mcp": {
      "url": "https://planner.monopoly-gold.com/_mcp"
    }
  }
}

Tools it offers

43 tools, as the server itself reported during our check on Oct 31, 2026.

  • project-listList all projects with optional status filter (active/archived/paused). Returns id, title, slug, webUrl, icon, and goals_count for each project. Use project-get for full details with goals breakdown by status.
  • project-createCreate a new project container for goals. Requires title and a unique slug (lowercase a-z, 0-9, hyphens). Optional: description, status (active/archived/paused, default active), tags, icon (emoji), repositoryPath, reposi
  • project-getFetch full project details: title, slug, status, description, icon, tags, repository info, sourceRef ({type,url,ref} for remote-research or null), goals breakdown by status (backlog/in_progress/blocked/done/cancelled cou
  • project-updatePartial update of a project — only the fields you pass are changed; omitted fields are untouched. Updatable: title, slug, description, status (active/archived/paused), tags, icon (emoji), repositoryPath, repositoryUrl, s
  • project-deleteDelete a project. If the project has goals, pass force=true to cascade-delete them all; without force, the call is rejected with the goals count. Returns deleted title, slug, and goals_deleted count.
  • project-add-dependencyDeclare that one project depends on another (depends-on relationship). Accepts UUID or slug for both sides. Idempotent: if the dependency already exists, returns it with already_existed=true. Self-references are rejected
  • project-remove-dependencyRemove a project dependency. Two lookup modes: pass dependency_id (UUID of the link itself), or pass both projectId and dependsOnProjectId (UUID or slug). Returns removed=true on success, removed=false if the dependency
  • goal-listList goals with optional filters: projectId (UUID), status (backlog/checking_ac/checking_ac_failed/checking_ac_errored/ready_for_work/in_progress/blocked/done/cancelled), type (goal/milestone/task/habit), parentId (UUID
  • goal-createCreate a goal/task/milestone/habit in the planning tree. Two modes: grove (default) — enforces acceptance criteria gate on status transitions (AC required before ready_for_work, file-evidence per AC before done); standar
  • goal-getFetch full details of a single goal: title, description, status, priority, type, mode, children, acceptance criteria (with evidence coverage), blockers, tags, deadline, estimate, history log, and project. The primary dri
  • goal-updatePartial update of a goal — only the fields you pass are changed; omitted fields are untouched. Updatable: title, status, priority (1-5), description, type, tags, deadline, estimate, mode, attemptCommit (git SHA of the at
  • goal-deleteIRREVERSIBLY delete a goal and all its descendants (children, evidence, blockers). Prefer goal-update status=cancelled to preserve history, or goal-block to mark an obstacle. Use delete only for erroneous/duplicate entri
  • goal-moveMove a goal to a different parent or project. Pass newParentId=UUID to reparent (inherits project from new parent), newParentId=null to make root. Optional projectId=UUID overrides the target project when making root (cr
  • goal-reorderSet display order of sibling goals within the same parent and priority band. Pass an array of goal UUIDs in the desired order — each is assigned position = its array index. All goals must share the same parent and priori
  • goal-blockAdd a blocker to a goal (blockers are additive — each call appends a new one, existing blockers are preserved). Sets status to blocked. Optionally create an inline resolver goal (resolverTitle) or link an existing one (l
  • goal-remove-blockerRemove a blocker from a goal by blocker UUID. If it was the last active blocker, the goal automatically returns to its previous status (in_progress or backlog). Does not delete the linked resolver goal if one exists.
  • goal-todoQuick-capture a task or improvement idea into a project. Creates a backlog task with priority 4 (low) and auto-adds the "suggestion" tag. Resolves project by slug (falls back to the default project). Lightweight alternat
  • goal-add-noteAdd a free-form note (markdown supported) to a goal — decisions taken, dead ends hit, context worth carrying into the next session. Notes are NOT evidence: they hang off the goal rather than an acceptance criterion and n
  • goal-remove-noteRemove a note from a goal by note UUID. Note ids come from goal-get (notes[].id). Deletes only the note — never touches acceptance criteria, evidence or blockers.
  • goal-treeFetch the full goal hierarchy as a nested tree. Optional filters: projectId (UUID) to scope to one project, rootId (UUID) to get a subtree. Each node includes id, title, status, priority, type, progress, and nested child
  • goal-summaryAggregate statistics across all goals (or scoped to a projectId): total count, breakdown by status, root count, blocked count, and overdue count. Useful for daily standups and dashboard views.
  • goal-add-criterionAppend an acceptance criterion to a goal. The text must describe an observable check over an artifact (e.g. "GET /api/health returns 200 with {status:ok}"), not a subjective approval. Each criterion has a class: pre-merg
  • goal-update-criterionUpdate an acceptance criterion: its text and/or its class + probe. probeClass=post-deploy requires an executable probeSpec {method, url, expect:{http_code, body}} (kept from the criterion when omitted and one already exi
  • goal-remove-criterionRemove an acceptance criterion from a goal. Grove mode: only while goal is in backlog (frozen once started). Standard mode: until goal is done. Cascades to all evidence on the criterion. Returns confirmation with removed
  • goal-attach-evidencePRIMARY path to close a Grove goal: this is the ONLY tool that covers an acceptance criterion. Attach binary evidence (screenshot, log dump, API response, export) to an AC — call it once per criterion to satisfy the clos
  • goal-request-uploadPREFERRED path to attach a LARGE binary evidence file (screenshot, log dump, PDF, session transcript — anything > ~1 KB) to an acceptance criterion. Returns a one-time {uploadUrl, expiresAt} scoped to this criterion. The
  • goal-add-evidence-textSUBORDINATE / supplementary path — does NOT close an acceptance criterion. Adds a text-only note (URL to a permanent external source like CI run / GitHub commit / issue, or a description of a manual scenario) as extra co
  • goal-remove-evidenceDelete an evidence record by UUID. Forbidden if the owning goal is already done (evidence is frozen after close). Removes both the database record and the attached file (if any).
  • goal-add-assumptionAdd an assumption to a goal edge (parent→this goal). An assumption is an explicit premise: "why does completing this goal contribute to the parent?" Requires the goal to have a parent (root goals have no edge). Text must
  • goal-update-assumptionUpdate text or signpost of an assumption. Status cannot be changed manually — transitions happen only via evidence judge verdicts.
  • goal-remove-assumptionRemove an assumption from a goal edge.
  • goal-suggest-assumptionsLLM generates suggested assumptions for a goal edge (parent→child). Returns 2-4 assumptions with signposts and type classification. Author should review, edit, and accept relevant ones via goal-add-assumption.
  • goal-attach-assumption-evidenceAttach text evidence to an assumption and judge it. The judge evaluates whether the evidence supports or challenges the assumption and automatically transitions its status: supports → supported, first challenges → challe
  • goal-request-ac-changeRequest a change to an acceptance criterion. grounds=unreachable (default): the AC cannot be proven — requires ≥3 failed evidence attempts (weak/mismatch) with 0 matches. grounds=wrong_criterion: the AC measures the wron
  • goal-resolve-escalationResolve a pending AC escalation. Owner decides: edit (provide new AC text), split (move AC to a child goal), drop (remove the AC outright, optionally with a linkedGoalId audit reference), or reject (agent must find anoth
  • goal-attach-fileAttach a small file (mockup, diagram, screenshot, PDF) to a GOAL as a description attachment — NOT evidence: it is not bound to any acceptance criterion, is never judged and never counts toward closing the goal. Returns
  • goal-dismiss-red-teamDismiss the red-team finding that blocks a goal from starting, when you disagree with the verdict. Requires a reason of at least 80 characters explaining why the counterexample does not apply. The dismissal is recorded i
  • goal-read-evidence-contentRead attached evidence through MCP without changing its format. Pass evidenceId from goal-get. Text (text/plain, JSON, NDJSON) returns newline-preserving redacted lines; offset/limit are zero-based line pagination. Image
  • goal-recent-unresolvedPull-инбокс для «подхватить и довести» в неосновное окно. По одному проекту, за окно N дней, статусы для подхвата (очередь исполнителя — ready_for_work и checking_ac_errored: backlog-цели брать нельзя). Возвращает обогащ
  • goal-record-iteration-certificateRecord one completed LeanSolver iteration against the current tracked contract. Result artifact refs must resolve to existing evidence or goal_attachment rows owned by this goal. Rework iterations accept only registered

Questions

What is the Planner MCP — provable "done" for AI agents MCP server?

Goal and task planning MCP for Codex and AI agents, with evidence-backed completion. It is made by planner.monopoly-gold.com and listed in the official MCP Registry as com.monopoly-gold.planner/mcp. MCP (Model Context Protocol) is the open standard that lets AI apps like Claude, ChatGPT and Cursor use outside tools.

How do I add Planner MCP — provable "done" for AI agents to Claude?

In the Claude app or claude.ai, open Settings, then Connectors, choose "Add custom connector" and paste https://planner.monopoly-gold.com/_mcp. In Claude Code, run: claude mcp add --transport http mcp https://planner.monopoly-gold.com/_mcp

How do I add Planner MCP — provable "done" for AI agents to ChatGPT?

ChatGPT can use remote MCP servers as connectors. In ChatGPT settings, under Apps and Connectors, turn on developer mode if asked, create a new connector and paste https://planner.monopoly-gold.com/_mcp.

How do I add Planner MCP — provable "done" for AI agents to Cursor?

Open Cursor settings, go to MCP, choose "Add new MCP server" (or edit ~/.cursor/mcp.json) and add: { "mcpServers": { "mcp": { "url": "https://planner.monopoly-gold.com/_mcp" } } }

Does Planner MCP — provable "done" for AI agents work right now?

Yes. It responded when we last checked on 31 Oct 2026. We check remote MCP servers every day.

What can Planner MCP — provable "done" for AI agents do?

It gives your AI 43 tools, including project-list, project-create, project-get, project-update, project-delete. The full list is on this page.

Is this your server? Get the badge for your README
chen.media/mcp badge

Markdown (GitHub README)

[![Listed on chen.media/mcp](https://chen.media/mcp/badge/com-monopoly-gold-planner-mcp.svg)](https://chen.media/mcp/com-monopoly-gold-planner-mcp)

HTML (switches to dark mode on its own)

<a href="https://chen.media/mcp/com-monopoly-gold-planner-mcp"><picture><source media="(prefers-color-scheme: dark)" srcset="https://chen.media/mcp/badge/com-monopoly-gold-planner-mcp.svg?theme=dark"><img src="https://chen.media/mcp/badge/com-monopoly-gold-planner-mcp.svg" alt="Listed on chen.media/mcp" height="40"></picture></a>

More in Productivity

See all