Skip to main content
mcpSource-backed
Plane logo

Plane MCP Server

Official Plane MCP server for connecting Claude to Plane projects, work items, cycles, modules, initiatives, comments, links, work logs, pages, and workspace metadata.

by Plane · submitted by oktofeesh1·added 2026-06-06·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://github.com/makeplane/plane-mcp-server/blob/main/README.md, https://github.com/makeplane/plane-mcp-server, https://plane.so
Brand
Plane
Brand domain
plane.so
Brand asset source
brandfetch
Safety notes
Plane MCP exposes 100+ tools across projects, work items, cycles, modules, initiatives, intake, labels, states, comments, links, work logs, pages, workspaces, and users., Many tools can create, update, delete, archive, unarchive, transfer, or otherwise change Plane workspace state., Remote OAuth and PAT transports grant read and write scopes, so configure the narrowest workspace access and review actions before execution., Stdio transport requires PLANE_API_KEY and PLANE_WORKSPACE_SLUG; protect API keys and rotate them if they are exposed., The server uses structured logging middleware with payloads enabled in source, so review logging behavior before sending sensitive issue data through the server.
Privacy notes
Plane workspaces can contain roadmap plans, bug reports, customer requests, comments, assignees, estimates, links, work logs, labels, and internal operational metadata., Tool calls and logs can expose workspace slugs, project identifiers, work item IDs, titles, descriptions, comments, links, activity history, and user details to the MCP client and model provider., PLANE_API_KEY, PLANE_ACCESS_TOKEN, PAT values, OAuth client secrets, workspace slugs, and self-hosted Plane URLs should stay out of prompts, issues, logs, screenshots, and committed files., Claude-generated updates may notify teammates or alter shared planning state, so review visible changes before applying them.
Author
Plane
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

10 minutes

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

5 prerequisites to line up before setup. Have accounts and credentials ready first. Includes a review or approval gate.

0/5 ready
Account & credentials3Install & runtime1Review & approval110 minutes

Safety & privacy surface

Safety & privacy surface

5 safety and 4 privacy notes across 5 risk areas. Review closely: credentials & tokens, network access, third-party handling.

5 areas
  • SafetyData retentionPlane MCP exposes 100+ tools across projects, work items, cycles, modules, initiatives, intake, labels, states, comments, links, work logs, pages, workspaces, and users.
  • SafetyGeneralMany tools can create, update, delete, archive, unarchive, transfer, or otherwise change Plane workspace state.
  • SafetyCredentials & tokensRemote OAuth and PAT transports grant read and write scopes, so configure the narrowest workspace access and review actions before execution.
  • SafetyCredentials & tokensStdio transport requires PLANE_API_KEY and PLANE_WORKSPACE_SLUG; protect API keys and rotate them if they are exposed.
  • SafetyData retentionThe server uses structured logging middleware with payloads enabled in source, so review logging behavior before sending sensitive issue data through the server.
  • PrivacyNetwork accessPlane workspaces can contain roadmap plans, bug reports, customer requests, comments, assignees, estimates, links, work logs, labels, and internal operational metadata.
  • PrivacyThird-party handlingTool calls and logs can expose workspace slugs, project identifiers, work item IDs, titles, descriptions, comments, links, activity history, and user details to the MCP client and model provider.
  • PrivacyCredentials & tokensPLANE_API_KEY, PLANE_ACCESS_TOKEN, PAT values, OAuth client secrets, workspace slugs, and self-hosted Plane URLs should stay out of prompts, issues, logs, screenshots, and committed files.
  • PrivacyGeneralClaude-generated updates may notify teammates or alter shared planning state, so review visible changes before applying them.

Safety notes

  • Plane MCP exposes 100+ tools across projects, work items, cycles, modules, initiatives, intake, labels, states, comments, links, work logs, pages, workspaces, and users.
  • Many tools can create, update, delete, archive, unarchive, transfer, or otherwise change Plane workspace state.
  • Remote OAuth and PAT transports grant read and write scopes, so configure the narrowest workspace access and review actions before execution.
  • Stdio transport requires PLANE_API_KEY and PLANE_WORKSPACE_SLUG; protect API keys and rotate them if they are exposed.
  • The server uses structured logging middleware with payloads enabled in source, so review logging behavior before sending sensitive issue data through the server.

Privacy notes

  • Plane workspaces can contain roadmap plans, bug reports, customer requests, comments, assignees, estimates, links, work logs, labels, and internal operational metadata.
  • Tool calls and logs can expose workspace slugs, project identifiers, work item IDs, titles, descriptions, comments, links, activity history, and user details to the MCP client and model provider.
  • PLANE_API_KEY, PLANE_ACCESS_TOKEN, PAT values, OAuth client secrets, workspace slugs, and self-hosted Plane URLs should stay out of prompts, issues, logs, screenshots, and committed files.
  • Claude-generated updates may notify teammates or alter shared planning state, so review visible changes before applying them.

Prerequisites

  • Python 3.10 or newer available through uvx for local stdio usage.
  • Plane workspace slug and API key for stdio transport.
  • Plane OAuth or Personal Access Token setup when using hosted remote HTTP transport.
  • Clear project and workspace scope for what Claude may read or modify.
  • Human review rules for any create, update, delete, archive, unarchive, transfer, or comment operation.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
10 minutes
Difficulty
intermediate
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "plane": {
      "command": "uvx",
      "args": ["plane-mcp-server", "stdio"],
      "env": {
        "PLANE_API_KEY": "<your-plane-api-key>",
        "PLANE_WORKSPACE_SLUG": "<your-workspace-slug>",
        "PLANE_BASE_URL": "https://api.plane.so"
      }
    }
  }
}

About this resource

Content

Plane MCP Server is Plane's official Model Context Protocol server for connecting Claude and other MCP clients to Plane workspaces. It exposes tools for reading and managing Plane projects, work items, cycles, modules, initiatives, intake work items, labels, states, comments, links, work logs, pages, workspace features, and user information.

The current repository is the Python and FastMCP implementation. Its README notes that the older Node.js @makeplane/plane-mcp-server package is deprecated and directs users to migrate to this Python-based server.

Source Review

These sources were reviewed on 2026-06-06. Prefer the live repository, README, PyPI metadata, package metadata, server implementation, tool directory, and license for current package names, transport options, authentication requirements, tool coverage, and migration notes.

Features

  • Official MCP server from Plane.
  • Python package plane-mcp-server with plane-mcp-server console script.
  • Local stdio transport with uvx plane-mcp-server stdio.
  • Hosted remote HTTP transport with Plane OAuth.
  • Hosted remote HTTP transport with Personal Access Token headers.
  • Legacy SSE transport for backward compatibility.
  • 100+ tools across more than 20 Plane resource categories.
  • Project, work item, cycle, module, initiative, intake, property, epic, milestone, label, state, comment, link, relation, activity, work log, page, workspace, and user tools.
  • Pydantic model usage through the Plane SDK for typed tool inputs.
  • Structured logging for server runtime events.

Installation

For local stdio usage with uvx:

{
  "mcpServers": {
    "plane": {
      "command": "uvx",
      "args": ["plane-mcp-server", "stdio"],
      "env": {
        "PLANE_API_KEY": "<your-plane-api-key>",
        "PLANE_WORKSPACE_SLUG": "<your-workspace-slug>",
        "PLANE_BASE_URL": "https://api.plane.so"
      }
    }
  }
}

Use the README's hosted HTTP examples when you want Plane-managed OAuth or PAT authentication instead of local stdio environment variables.

Use Cases

  • Ask Claude to list Plane projects and summarize active work.
  • Search work items across a workspace before planning a sprint.
  • Retrieve a work item and its comments before drafting a response.
  • Create or update a work item after a human reviews the exact fields.
  • Add work items to a cycle, module, or milestone with explicit approval.
  • Summarize work logs, project membership, workspace features, or activity history.
  • Use hosted OAuth transport for a managed Plane connection when the MCP client supports it.

Safety and Privacy

Plane MCP can alter shared planning and issue-tracking state. Treat create, update, delete, archive, unarchive, transfer, and comment tools as write operations that need human review. Use a workspace-scoped API key or OAuth grant with the minimum access needed for the workflow.

Plane issues often contain customer names, product plans, security bugs, support conversations, implementation links, and internal assignments. Review which workspace and project Claude can access, protect API keys and PATs, and avoid forwarding sensitive issue bodies or comments to unapproved model sessions.

Disclosure

Plane offers open-source and commercial project management products. This listing is not sponsored, paid, or affiliate-driven, and it is scoped to the source-backed official Plane MCP server.

Duplicate Check

No dedicated Plane MCP Server, makeplane/plane-mcp-server, or plane-mcp-server source URL entry was found in content/mcp. Existing text matches were unrelated PlanetScale entries and incidental non-Plane mentions.

Source citations

Add this badge to your README

Show that Plane MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/plane-mcp-server.svg)](https://heyclau.de/entry/mcp/plane-mcp-server)

How it compares

Plane MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Submitter).

Field

Official Plane MCP server for connecting Claude to Plane projects, work items, cycles, modules, initiatives, comments, links, work logs, pages, and workspace metadata.

Open dossier

Manage Backlog projects from Claude — create and update issues, comment on tickets, manage wiki pages, review pull requests, and navigate your Nulab Backlog space — with the official Backlog MCP server supporting stdio and HTTP transports.

Open dossier

MCP server for Trello boards, cards, lists, comments, checklists, attachments, labels, board activity, workspace selection, and rate-limited Trello API automation from Claude.

Open dossier

Official Microsoft Azure DevOps MCP server for querying work items, pull requests, repositories, pipelines, wikis, test plans, and project metadata through remote HTTP or local stdio transports.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
SubmitterDiffersoktofeesh1oktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandPlane logoPlaneTrello MCP Server logoTrello MCP ServerAzure logoAzure
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorPlaneNulabJarad DeLorenzoMicrosoft
Added2026-06-062026-06-182026-06-062026-06-03
Platforms
Harness
Source repo
Safety notesPlane MCP exposes 100+ tools across projects, work items, cycles, modules, initiatives, intake, labels, states, comments, links, work logs, pages, workspaces, and users. Many tools can create, update, delete, archive, unarchive, transfer, or otherwise change Plane workspace state. Remote OAuth and PAT transports grant read and write scopes, so configure the narrowest workspace access and review actions before execution. Stdio transport requires PLANE_API_KEY and PLANE_WORKSPACE_SLUG; protect API keys and rotate them if they are exposed. The server uses structured logging middleware with payloads enabled in source, so review logging behavior before sending sensitive issue data through the server.Tools can create, update, and delete projects, issues, wikis, and pull requests — changes affect your live Backlog space. Use `ENABLE_TOOLSETS` to restrict which tool groups are available if you only need read access.Trello MCP Server can create, read, update, move, archive, and delete board data depending on token permissions and requested tools. Card, checklist, label, due-date, start-date, comment, attachment, board, list, workspace, and active-board changes can affect real team workflows. File attachments are added from URLs; review source URLs and destination cards before allowing an agent to attach files. Use `TRELLO_ALLOWED_WORKSPACES` to limit workspace access, especially when a token can see personal, client, or production boards. Require confirmation before creating boards, adding attachments, deleting or archiving cards, changing due dates, moving cards between lists, or posting comments on behalf of a user.Start with read-only mode for investigation. The remote server supports the `X-MCP-Readonly: true` header, and the local server supports domain filtering so agents only load the Azure DevOps areas they need. Azure DevOps write-capable tools can create or update work items, pull requests, pull request comments, branches, wiki pages, test plans, test suites, test cases, and pipeline runs. Keep manual approval on any operation that changes project state. Treat Azure DevOps PATs, Microsoft Entra tokens, Azure CLI sessions, and MCP configuration as sensitive credentials. Do not paste tokens into prompts, commit them to repositories, or share them in issue/PR threads. Use toolsets, domains, project defaults, and team defaults to keep the MCP surface narrow. Loading every repo, work item, wiki, pipeline, and test plan tool can confuse the model and expose more context than the task needs. The remote MCP server is in public preview. Preview behavior, available tools, supported clients, and authentication requirements can change before general availability.
Privacy notesPlane workspaces can contain roadmap plans, bug reports, customer requests, comments, assignees, estimates, links, work logs, labels, and internal operational metadata. Tool calls and logs can expose workspace slugs, project identifiers, work item IDs, titles, descriptions, comments, links, activity history, and user details to the MCP client and model provider. PLANE_API_KEY, PLANE_ACCESS_TOKEN, PAT values, OAuth client secrets, workspace slugs, and self-hosted Plane URLs should stay out of prompts, issues, logs, screenshots, and committed files. Claude-generated updates may notify teammates or alter shared planning state, so review visible changes before applying them.Issue content, comments, wiki pages, pull request details, and user information from your Backlog space are surfaced in Claude's context. Your `BACKLOG_API_KEY` grants account-level Backlog access — keep it in the MCP config env and never commit it to version control.Trello API keys, tokens, board IDs, workspace IDs, card IDs, member names, labels, comments, checklists, attachments, due dates, and activity logs can be exposed to the MCP client. Active board and workspace selections may persist locally in Trello MCP configuration. Card descriptions, comments, attachments, and activity histories can contain private customer, roadmap, incident, or operational data. Proxy settings, Trello credentials, and workspace allowlists should be kept out of shared MCP configs, logs, screenshots, and transcripts. Response previews reduce some large card-description exposure, but full-card and activity tools can still return sensitive Trello content.Tool results can expose organization names, project names, teams, iteration data, capacity information, work item titles and fields, comments, attachments, pull request discussions, repository file content, branch names, commit metadata, pipeline logs, build artifacts, wiki pages, test plans, and search results. Work item comments, PR threads, pipeline logs, wiki pages, and attachments often contain customer data, production incident details, credentials, internal URLs, unreleased roadmap information, employee names, or security findings. MCP client logs, AI transcripts, generated code comments, local terminal history, and downstream ticket summaries can retain Azure DevOps content outside the original Azure DevOps audit, permission, and retention model. Microsoft Entra authentication exposes the user's organizational identity to the MCP client and constrains access to the authenticated user's Azure DevOps permissions.
Prerequisites
  • Python 3.10 or newer available through uvx for local stdio usage.
  • Plane workspace slug and API key for stdio transport.
  • Plane OAuth or Personal Access Token setup when using hosted remote HTTP transport.
  • Clear project and workspace scope for what Claude may read or modify.
  • A Backlog account on backlog.com or your Backlog.jp/enterprise space.
  • A Backlog API key: Personal Settings → API → Generate API Key.
  • Node.js with `npx` available.
  • An MCP client such as Claude Code or Claude Desktop.
  • Trello API key and token with access to the boards and workspaces Claude may use.
  • Bun-compatible published package runtime or an MCP client that can launch the packaged stdio server through npx.
  • Optional `TRELLO_BOARD_ID` or `TRELLO_WORKSPACE_ID` when a default board or workspace should be selected at startup.
  • Optional `TRELLO_ALLOWED_WORKSPACES` to constrain the token to specific approved Trello workspaces.
  • Azure DevOps organization and project membership for the resources Claude should access
  • Microsoft Entra ID connected Azure DevOps organization for the remote MCP server
  • Visual Studio Code or Visual Studio for the Microsoft-supported remote MCP preview path
  • Node.js 20 or later and npx for the optional local `@azure-devops/mcp` stdio server
Install
uvx plane-mcp-server stdio
claude mcp add backlog -e BACKLOG_DOMAIN=yourspace.backlog.com -e BACKLOG_API_KEY=<your-api-key> -- npx backlog-mcp-server
npx @delorenj/mcp-server-trello
claude mcp add azure-devops -- npx -y @azure-devops/mcp YOUR_AZURE_DEVOPS_ORG
Config
{
  "mcpServers": {
    "plane": {
      "command": "uvx",
      "args": ["plane-mcp-server", "stdio"],
      "env": {
        "PLANE_API_KEY": "<your-plane-api-key>",
        "PLANE_WORKSPACE_SLUG": "<your-workspace-slug>",
        "PLANE_BASE_URL": "https://api.plane.so"
      }
    }
  }
}
{
  "mcpServers": {
    "backlog": {
      "command": "npx",
      "args": ["backlog-mcp-server"],
      "env": {
        "BACKLOG_DOMAIN": "yourspace.backlog.com",
        "BACKLOG_API_KEY": "<your-api-key>",
        "MAX_TOKENS": "50000"
      }
    }
  }
}
{
  "mcpServers": {
    "trello": {
      "command": "npx",
      "args": [
        "@delorenj/mcp-server-trello"
      ],
      "env": {
        "TRELLO_API_KEY": "your-api-key",
        "TRELLO_TOKEN": "your-token",
        "TRELLO_ALLOWED_WORKSPACES": "workspace-id-1,workspace-id-2"
      },
      "type": "stdio"
    }
  }
}
Manual-only setup:
{
  "servers": {
    "ado-remote-mcp": {
      "url": "https://mcp.dev.azure.com/YOUR_AZURE_DEVOPS_ORG",
      "type": "http",
      "headers": {
        "X-MCP-Toolsets": "repos,wiki,wit",
        "X-MCP-Readonly": "true"
      }
    }
  },
  "inputs": []
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.