
Plane Workflow
io.github.amirhosseinkzPublished by GitHub account amirhosseinkzv0.7.0Updated Nov 6, 2026
Plan, start, and complete Plane work items under team rules, with previews and idempotent writes.
Overview
Local MCP server that lets an assistant plan, start, and complete Plane work items under configurable team rules, with previews and read-only briefings.
- What you can do
- Draft and plan Plane work items, in advisory or strict mode with required fields
- Preview and apply work-item writes, including dry-run previews and idempotent updates
- Start and complete items, recording completion evidence before the state change
- Read project briefings and generate DOCX or PDF reports
- List and activate projects, and check the active workspace and project status
- When to use it
- Useful when a coding agent should keep Plane tasks in sync with its work: drafting structured tasks, checking overdue or unassigned items, and closing items with verification notes. Also fits teams that want configurable planning rules and project guards around task changes.
- Requirements
- Runs locally over stdio as a Python package installed with uv (Python 3.11+ and uv). Needs a Plane workspace and an API key, stored in the OS keyring by guided setup or supplied through environment variables for headless use. Setup supports several client adapters; desktop only.
Installation
In SourceWeft
- Open Plane Workflow in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Plane Workflow MCP
Keep Plane tasks in sync with your coding agent using configurable team workflows. Draft structured tasks, preview changes, record completion evidence, and get read-only project briefings or DOCX/PDF reports.
Install and get your first result
Requires Python 3.11+, uv, and a Plane workspace with an API key. Install from PyPI:
Replace PROJECT_ID with a listed ID. Setup also has --client codex, cursor,
claude-desktop, opencode, and zed adapters. Restart the client, then ask:
Confirm my active Plane workspace and project, then show overdue and unassigned work. Include identifiers and totals, flag truncated lists, and do not change Plane data.
To use an unreleased checkout, run uv tool install ./plugins/plane-workflow
from the repository root instead.
Workflow behavior
- Advisory planning accepts incomplete planning data; strict planning requires scope, complexity, assignment, an estimate mapping, dates, and an unstarted state.
- Project selection guards work-item mutations against conflicting projects.
- Completion requires a started item, a summary, and verification text; the completion record is written before the state transition.
- API keys are stored in the OS keyring by guided setup. Environment variables support headless use.
Preview supported writes with dry_run=true and ask the agent to wait for approval.
Some writes default to applying changes. Approval is a client workflow, not a
server-enforced human approval gate. Updates happen through tool calls, not a
background code-to-task sync.
Documentation
- Quick start and official-server comparison
- Installation and client compatibility
- Copyable workflow examples
- Planning and workflow configuration
- Demo
- Support
MIT licensed. Independent community project; not affiliated with Plane.
Source: plugins/plane-workflow/README.md at commit 6324399
Tools
0Version history
1- v0.7.0LatestOct 29, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts