Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Plane Workflow

PYPI · PLANE-WORKFLOW-MCP

Plan, start, and complete Plane work items under team rules, with previews and idempotent writes.

Available components

+15 this week 66 Trust /100

Last scanned (3 hours ago)

Scores higher than 62% of PyPI servers

Category Project Management

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 4 of 39 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability58
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 2699 tokens (~81/item across 33 items; 33 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage73
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 6% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 33 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 34 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 28 Oct 26 51

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed pypi/plane-workflow-mcp@0.7.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 39 packages
Packages resolved 39
Stale 4
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 33 exposed · ~2,584 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
activate_plane_project ~33

Validate and select a project in the active stored workspace for future work-item operations.

NameTypeReqDescription
project_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

activate_plane_workspace ~32

Switch to a configured Plane workspace profile without contacting Plane or exposing its API key.

NameTypeReqDescription
profilestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

add_work_item_evidence_links ~99

Preview or attach validated evidence links to one work item. Set confirm=true to create the links.

NameTypeReqDescription
confirmboolean––
confirm_project_identifier––Only to target a project other than the active one: the target project's identifier (for example WEB). The call is rejected unless it matches project_id.
evidence–––
note–––
project_id–––
work_item_idstring––

Structured output declared, but exposes no named fields.

No examples provided.

add_work_item_relation ~104

Preview or create same-project work-item relations. Set confirm=true after reviewing the relation direction.

NameTypeReqDescription
confirmboolean––
confirm_project_identifier––Only to target a project other than the active one: the target project's identifier (for example WEB). The call is rejected unless it matches project_id.
project_id–––
related_work_item_idsarrayyes–
relation_typestringyes–
work_item_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

apply_git_backfill ~193

Preview or apply a saved git backfill plan: create, start, and complete each item with a commit-citing record. titles and modules override proposed values by item id; skip leaves items out. Committed work is completed with a comment listing its commits; uncommitted work is only started. Every step is idempotent, so re-running after an error resumes without duplicates. Plane sets completed_at to the time of this call; the real dates are kept in start_date, target_date, and the comment.

NameTypeReqDescription
allow_create_modulesboolean––
confirm_project_identifier––Only to target a project other than the active one: the target project's identifier (for example WEB). The call is rejected unless it matches project_id.
dry_runboolean––
modules–––
plan_idstringyes–
skip–––
titles–––

Structured output declared, but exposes no named fields.

No examples provided.

apply_standardization_plan ~44

Preview or apply a saved standardization plan. Set confirm=true only after reviewing its proposed actions.

NameTypeReqDescription
confirmboolean––
plan_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

audit_work_items ~34

Audit Plane work items without changing them. Reports structural and quality gaps for a human-approved cleanup.

NameTypeReqDescription
project_id–––

Structured output declared, but exposes no named fields.

No examples provided.

cancel_standard_work_item ~104

Preview or cancel unfinished work after recording a factual reason and optional follow-ups.

NameTypeReqDescription
confirm_project_identifier––Only to target a project other than the active one: the target project's identifier (for example WEB). The call is rejected unless it matches project_id.
dry_runboolean––
follow_ups–––
project_id–––
reasonstringyes–
state_id–––
work_item_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

complete_standard_work_item ~123

Preview or complete started work after recording a factual, human-readable completion comment.

NameTypeReqDescription
actual_minutes–––
confirm_project_identifier––Only to target a project other than the active one: the target project's identifier (for example WEB). The call is rejected unless it matches project_id.
dry_runboolean––
follow_ups–––
implementation_notes–––
project_id–––
state_id–––
summarystringyes–
verificationarrayyes–
work_item_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

create_standard_work_item ~292

Create a structured Plane work item with labels, duplicate review, optional module/cycle assignment, and planning fields. Retrying a create with the same idempotency_key (or, without one, the same title) returns the item the first attempt made instead of creating a second one. Use distinct idempotency_keys with allow_duplicate=true to create intentionally separate items that share a title.

NameTypeReqDescription
acceptance_criteriaarrayyes–
additional_labels–––
allow_create_moduleboolean––
allow_duplicateboolean––
assignee_ids–––
complexity–––
confirm_project_identifier––Only to target a project other than the active one: the target project's identifier (for example WEB). The call is rejected unless it matches project_id.
context–––
current_behavior–––
cycle_id–––
dry_runboolean––
estimate–––
expected_behavior–––
idempotency_key–––
module_description–––
module_name–––
outcomestringyes–
priority–––
project_id–––
release_id–––
scope–––
start_date–––
state_id–––
surface–––
target_date–––
title_parts–––
work_item_typestring––

Structured output declared, but exposes no named fields.

No examples provided.

create_standardization_plan ~48

Create and save a read-only cleanup proposal. The plan does not change Plane until apply_standardization_plan is confirmed.

NameTypeReqDescription
expires_in_hoursinteger––
project_id–––

Structured output declared, but exposes no named fields.

No examples provided.

diagnose_plane_connection ~35

Check local Plane configuration and, when given a project, read the available API capabilities without changing Plane.

NameTypeReqDescription
project_id–––

Structured output declared, but exposes no named fields.

No examples provided.

ensure_module ~103

Preview or find an existing module, then explicitly create or assign it when requested.

NameTypeReqDescription
confirm_project_identifier––Only to target a project other than the active one: the target project's identifier (for example WEB). The call is rejected unless it matches project_id.
create_if_missingboolean––
description–––
dry_runboolean––
module_namestring––
project_id–––
work_item_ids–––

Structured output declared, but exposes no named fields.

No examples provided.

export_work_items_report ~102

Export filtered Plane work items as a dynamic Word or PDF report without changing Plane. Example filters: {"state_names": ["Backlog", "In Progress"]}. Example layout: {"group_by": "state", "columns": ["identifier", "title", "state", "priority"]}.

NameTypeReqDescription
filters–––
formatstringyes–
layout–––
output_directory–––
project_id–––
title–––

Structured output declared, but exposes no named fields.

No examples provided.

find_duplicate_candidates ~51

Find potentially duplicate Plane work items by title similarity without changing Plane.

NameTypeReqDescription
max_resultsinteger––
min_scorenumber––
project_id–––
titlestring––

Structured output declared, but exposes no named fields.

No examples provided.

find_work_items ~52

Find Plane work items by their title, UUID, or project reference such as PROJECT-12 without changing Plane.

NameTypeReqDescription
max_resultsinteger––
project_id–––
querystring––

Structured output declared, but exposes no named fields.

No examples provided.

get_active_plane_context ~24

Show the active Plane workspace and project without exposing credentials or changing Plane.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_plane_workflow_setup_status ~26

Check whether Plane Workflow is configured, without contacting Plane or revealing credentials.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_project_briefing ~52

Summarize project execution and identify overdue, stale, unassigned, and unplanned active work.

NameTypeReqDescription
attention_limitinteger––
project_id–––
stale_after_days–––

Structured output declared, but exposes no named fields.

No examples provided.

get_project_workflow_context ~37

Read a project's identifiers, active profile, modules, labels, and work-item count without changing Plane.

NameTypeReqDescription
project_id–––

Structured output declared, but exposes no named fields.

No examples provided.

get_project_workflow_profile ~34

Read the merged workflow profile for a Plane project without changing Plane or local profile files.

NameTypeReqDescription
project_id–––

Structured output declared, but exposes no named fields.

No examples provided.

get_standardization_plan ~28

Read a saved standardization plan without changing Plane.

NameTypeReqDescription
plan_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_work_item_relations ~41

Read one work item's dependency, duplicate, schedule, and related-work relationships.

NameTypeReqDescription
project_id–––
work_item_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_workflow_options ~36

List the available state, cycle, assignee, and estimate choices for a project without changing Plane.

NameTypeReqDescription
project_id–––

Structured output declared, but exposes no named fields.

No examples provided.

list_configured_plane_workspaces ~29

List locally configured Plane workspaces and the project selected in each, without contacting Plane.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_plane_projects ~25

List projects in the active Plane workspace so one can be selected without changing Plane.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_work_items ~119

List project work items with cross-edition local filters and bounded pagination.

NameTypeReqDescription
assignee_ids–––
cycle_ids–––
include_completedboolean––
label_ids–––
max_resultsinteger––
module_ids–––
offsetinteger––
overdue_onlyboolean––
priorities–––
project_id–––
query–––
state_ids–––
state_types–––
updated_after–––
updated_before–––

Structured output declared, but exposes no named fields.

No examples provided.

plan_git_backfill ~167

Read local git history and propose Plane work items for it, without changing Plane. Commits are grouped by module_map path prefix (for example {"apps/web/": "Web"}), then by conventional-commit scope, then by top-level folder, and split when work pauses longer than max_gap_days. Start and target dates come from the commit dates, moved onto the project's business days. Review the items with the user, then call apply_git_backfill with the returned plan_id.

NameTypeReqDescription
author–––
include_uncommittedboolean––
max_gap_daysinteger––
module_map–––
project_id–––
repo_pathstringyes–
sincestringyes–
until–––

Structured output declared, but exposes no named fields.

No examples provided.

save_project_workflow_profile ~59

Preview or save a project-bound workflow-profile override locally. Set confirm=true to write the profile file.

NameTypeReqDescription
confirmboolean––
profileobjectyes–
project_id–––
replace_existingboolean––

Structured output declared, but exposes no named fields.

No examples provided.

start_standard_work_item ~98

Preview or start planned work using the project's configured started state and the actual start date.

NameTypeReqDescription
confirm_project_identifier––Only to target a project other than the active one: the target project's identifier (for example WEB). The call is rejected unless it matches project_id.
dry_runboolean––
project_id–––
start_date–––
state_id–––
work_item_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

update_standard_work_item ~223

Preview or update a specific Plane work item while preserving labels and description unless a structured replacement is requested.

NameTypeReqDescription
acceptance_criteria–––
additional_labels–––
allow_create_moduleboolean––
assignee_ids–––
confirm_project_identifier––Only to target a project other than the active one: the target project's identifier (for example WEB). The call is rejected unless it matches project_id.
context–––
current_behavior–––
cycle_id–––
dry_runboolean––
estimate–––
expected_behavior–––
module_description–––
module_name–––
outcome–––
priority–––
project_id–––
release_id–––
replace_descriptionboolean––
scope–––
start_date–––
state_id–––
surface–––
target_date–––
title_parts–––
work_item_idstringyes–
work_item_type–––

Structured output declared, but exposes no named fields.

No examples provided.

upload_work_item_attachment ~104

Preview or upload one local file as a Plane attachment. Set confirm=true to upload the file.

NameTypeReqDescription
confirmboolean––
confirm_project_identifier––Only to target a project other than the active one: the target project's identifier (for example WEB). The call is rejected unless it matches project_id.
file_pathstring––
max_size_mbinteger––
project_id–––
work_item_idstring––

Structured output declared, but exposes no named fields.

No examples provided.

validate_workflow_profile ~33

Validate a reusable workflow-profile override and return a representative title preview without saving it.

NameTypeReqDescription
profileobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Plane Workflow MCP server?

Plane Workflow runs locally as a PyPI package, launched with uvx plane-workflow-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · plane-workflow-mcp

# add to Claude Code
claude mcp add amirhosseinkz-plane-workflow-mcp -- uvx plane-workflow-mcp
Common questions

What is the Plane Workflow MCP server?

Plane Workflow is an MCP server listed in the public MCP registry as io.github.amirhosseinkz/plane-workflow-mcp. Plan, start, and complete Plane work items under team rules, with previews and idempotent writes. This page covers its PyPI package (plane-workflow-mcp).

Is the Plane Workflow MCP server safe to use?

Plane Workflow scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Plane Workflow MCP server expose?

Plane Workflow exposes 33 tools: get_plane_workflow_setup_status, list_configured_plane_workspaces, activate_plane_workspace, get_active_plane_context, list_plane_projects, and 28 more. Their descriptions and schemas cost roughly 2,584 tokens of context every time the server is loaded.

Is the Plane Workflow MCP server still maintained?

Plane Workflow is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Plane Workflow MCP server under?

Plane Workflow declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.