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:
uv tool install plane-workflow-mcp
plane-workflow setup --client claude-code
plane-workflow project list
plane-workflow project activate PROJECT_ID
plane-workflow status
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.
Metadata
Release files for plane-workflow-mcp 0.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| plane_workflow_mcp-0.7.0.tar.gz | 71.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| plane_workflow_mcp-0.7.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 132.4 kB
Release files / plane_workflow_mcp-0.7.0.tar.gz
| Download URL | plane_workflow_mcp-0.7.0.tar.gz |
|---|---|
| Size | 71.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
93e3cb98d069a3ea2e840f7560e7c47c1d23892b76c28a088362ec08a19bd17e
|
|
BLAKE2b-256 checksum How to use checksums |
55a9f1b96b205c7dda6468e81b80b43d9a50bd7a17db12dfcb55d89131a8bdfa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / plane_workflow_mcp-0.7.0-py3-none-any.whl
| Download URL | plane_workflow_mcp-0.7.0-py3-none-any.whl |
|---|---|
| Size | 60.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e1150e01bba8058ade48c1f564a1a57cee7aa3cb82c944cc7a6c6edf4aa7909c
|
|
BLAKE2b-256 checksum How to use checksums |
e2bf7dd1128a6ffdd1aa89c50854c7c8a82a9dd0e70ffe1c8595b725ec431145
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for plane-workflow-mcp 0.7.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.