# Plane Workflow (pypi · plane-workflow-mcp)

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

- Trust score: 66/100 (medium)
- Change this week: +15
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `plane-workflow-mcp`: 66/100 (this document), [markdown](https://verifymcp.io/servers/amirhosseinkz-plane-workflow-mcp/plane-workflow-mcp.md), [page](https://verifymcp.io/servers/amirhosseinkz-plane-workflow-mcp/plane-workflow-mcp)

## Channel facts

- Registry: `pypi`
- Package: `plane-workflow-mcp`
- Version: `0.7.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

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

**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.

## 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.

### Claude

```bash
claude mcp add amirhosseinkz-plane-workflow-mcp -- uvx plane-workflow-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "amirhosseinkz-plane-workflow-mcp": {
      "command": "uvx",
      "args": [
        "plane-workflow-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "amirhosseinkz-plane-workflow-mcp": {
      "command": "uvx",
      "args": [
        "plane-workflow-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add amirhosseinkz-plane-workflow-mcp -- uvx plane-workflow-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "amirhosseinkz-plane-workflow-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "plane-workflow-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add amirhosseinkz-plane-workflow-mcp --command uvx --arg plane-workflow-mcp
```

### Hermes

```yaml
mcp_servers:
  amirhosseinkz-plane-workflow-mcp:
    command: "uvx"
    args: ["plane-workflow-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "amirhosseinkz-plane-workflow-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "plane-workflow-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add amirhosseinkz-plane-workflow-mcp -t stdio -c uvx -a plane-workflow-mcp
```

### Other

```json
{
  "mcpServers": {
    "amirhosseinkz-plane-workflow-mcp": {
      "command": "uvx",
      "args": [
        "plane-workflow-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 66, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-28 (score 51)

First indexed and scored.

## MCP tools (33)

### `get_plane_workflow_setup_status` (~26 tokens)

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

### `list_configured_plane_workspaces` (~29 tokens)

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

### `activate_plane_workspace` (~32 tokens)

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

Input parameters:

- `profile` (string, required)

### `get_active_plane_context` (~24 tokens)

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

### `list_plane_projects` (~25 tokens)

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

### `activate_plane_project` (~33 tokens)

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

Input parameters:

- `project_id` (string, required)

### `get_project_workflow_context` (~37 tokens)

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

Input parameters:

- `project_id`

### `get_project_workflow_profile` (~34 tokens)

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

Input parameters:

- `project_id`

### `get_workflow_options` (~36 tokens)

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

Input parameters:

- `project_id`

### `diagnose_plane_connection` (~35 tokens)

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

Input parameters:

- `project_id`

### `validate_workflow_profile` (~33 tokens)

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

Input parameters:

- `profile` (object, required)

### `save_project_workflow_profile` (~59 tokens)

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

Input parameters:

- `confirm` (boolean)
- `profile` (object, required)
- `project_id`
- `replace_existing` (boolean)

### `create_standardization_plan` (~48 tokens)

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

Input parameters:

- `expires_in_hours` (integer)
- `project_id`

### `get_standardization_plan` (~28 tokens)

Read a saved standardization plan without changing Plane.

Input parameters:

- `plan_id` (string, required)

### `apply_standardization_plan` (~44 tokens)

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

Input parameters:

- `confirm` (boolean)
- `plan_id` (string, required)

### `find_duplicate_candidates` (~51 tokens)

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

Input parameters:

- `max_results` (integer)
- `min_score` (number)
- `project_id`
- `title` (string)

### `find_work_items` (~52 tokens)

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

Input parameters:

- `max_results` (integer)
- `project_id`
- `query` (string)

### `list_work_items` (~119 tokens)

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

Input parameters:

- `assignee_ids`
- `cycle_ids`
- `include_completed` (boolean)
- `label_ids`
- `max_results` (integer)
- `module_ids`
- `offset` (integer)
- `overdue_only` (boolean)
- `priorities`
- `project_id`
- `query`
- `state_ids`
- `state_types`
- `updated_after`
- `updated_before`

### `get_project_briefing` (~52 tokens)

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

Input parameters:

- `attention_limit` (integer)
- `project_id`
- `stale_after_days`

### `get_work_item_relations` (~41 tokens)

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

Input parameters:

- `project_id`
- `work_item_id` (string, required)

### `add_work_item_relation` (~104 tokens)

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

Input parameters:

- `confirm` (boolean)
- `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_ids` (array, required)
- `relation_type` (string, required)
- `work_item_id` (string, required)

### `add_work_item_evidence_links` (~99 tokens)

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

Input parameters:

- `confirm` (boolean)
- `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_id` (string)

### `upload_work_item_attachment` (~104 tokens)

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

Input parameters:

- `confirm` (boolean)
- `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_path` (string)
- `max_size_mb` (integer)
- `project_id`
- `work_item_id` (string)

### `create_standard_work_item` (~292 tokens)

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.

Input parameters:

- `acceptance_criteria` (array, required)
- `additional_labels`
- `allow_create_module` (boolean)
- `allow_duplicate` (boolean)
- `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_run` (boolean)
- `estimate`
- `expected_behavior`
- `idempotency_key`
- `module_description`
- `module_name`
- `outcome` (string, required)
- `priority`
- `project_id`
- `release_id`
- `scope`
- `start_date`
- `state_id`
- `surface`
- `target_date`
- `title_parts`
- `work_item_type` (string)

### `start_standard_work_item` (~98 tokens)

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

Input parameters:

- `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_run` (boolean)
- `project_id`
- `start_date`
- `state_id`
- `work_item_id` (string, required)

### `complete_standard_work_item` (~123 tokens)

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

Input parameters:

- `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_run` (boolean)
- `follow_ups`
- `implementation_notes`
- `project_id`
- `state_id`
- `summary` (string, required)
- `verification` (array, required)
- `work_item_id` (string, required)

### `cancel_standard_work_item` (~104 tokens)

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

Input parameters:

- `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_run` (boolean)
- `follow_ups`
- `project_id`
- `reason` (string, required)
- `state_id`
- `work_item_id` (string, required)

### `update_standard_work_item` (~223 tokens)

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

Input parameters:

- `acceptance_criteria`
- `additional_labels`
- `allow_create_module` (boolean)
- `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_run` (boolean)
- `estimate`
- `expected_behavior`
- `module_description`
- `module_name`
- `outcome`
- `priority`
- `project_id`
- `release_id`
- `replace_description` (boolean)
- `scope`
- `start_date`
- `state_id`
- `surface`
- `target_date`
- `title_parts`
- `work_item_id` (string, required)
- `work_item_type`

### `ensure_module` (~103 tokens)

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

Input parameters:

- `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_missing` (boolean)
- `description`
- `dry_run` (boolean)
- `module_name` (string)
- `project_id`
- `work_item_ids`

### `audit_work_items` (~34 tokens)

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

Input parameters:

- `project_id`

### `export_work_items_report` (~102 tokens)

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"]}.

Input parameters:

- `filters`
- `format` (string, required)
- `layout`
- `output_directory`
- `project_id`
- `title`

### `plan_git_backfill` (~167 tokens)

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.

Input parameters:

- `author`
- `include_uncommitted` (boolean)
- `max_gap_days` (integer)
- `module_map`
- `project_id`
- `repo_path` (string, required)
- `since` (string, required)
- `until`

### `apply_git_backfill` (~193 tokens)

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.

Input parameters:

- `allow_create_modules` (boolean)
- `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_run` (boolean)
- `modules`
- `plan_id` (string, required)
- `skip`
- `titles`

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/amirhosseinkz-plane-workflow-mcp/plane-workflow-mcp#diagnostics

## Score history

- 2026-11-05: 66
- 2026-11-04: 51
- 2026-11-03: 51
- 2026-11-02: 51
- 2026-11-01: 51
- 2026-10-31: 51
- 2026-10-30: 51
- 2026-10-29: 51
- 2026-10-28: 51

## 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.

## Links

- PyPI project: https://pypi.org/project/plane-workflow-mcp/
- Socket report: https://socket.dev/pypi/package/plane-workflow-mcp
- Repository: https://github.com/amirhosseinkz/plane-workflow-mcp
- Changelog RSS feed: https://verifymcp.io/servers/amirhosseinkz-plane-workflow-mcp/plane-workflow-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/amirhosseinkz-plane-workflow-mcp/plane-workflow-mcp.json
- HTML version of this page: https://verifymcp.io/servers/amirhosseinkz-plane-workflow-mcp/plane-workflow-mcp