Skip to directory

Plane MCP

Plane

Streamable HTTP; stdio; legacy SSE (deprecated)15+ documented tools12

About Plane MCP

Plane's official MCP server connects AI clients to Plane projects and workspace data, enabling work-item management, planning, releases, customers, and related project operations.

What you can use it for

  • List, search, create, update, comment on, and organize work items
  • Plan cycles, modules, milestones, and initiatives
  • Manage releases, project metadata, customers, pages, and workspace resources
  • Query work with Plane Query Language (PQL)
Connection and setup
Hosting
Both: hosted Plane Cloud endpoint and local stdio for self-hosted/local use
Transport
Streamable HTTP; stdio; legacy SSE (deprecated)
Endpoint
https://mcp.plane.so/http/mcp
Authentication
Hosted OAuth interactive consent binds the session to a selected Plane workspace. Hosted PAT endpoint also supported with Authorization: Bearer <PAT> and x-workspace-slug headers. Local stdio uses PLANE_API_KEY and PLANE_WORKSPACE_SLUG.

Requirements

  • Plane account/workspace and permissions for intended resources
  • For local stdio: Python 3.10+, uv, PLANE_API_KEY and PLANE_WORKSPACE_SLUG
  • Plan/role access for gated features; hosted server cannot reach private self-hosted instances

Setup steps

  1. For hosted use, add https://mcp.plane.so/http/mcp via the selected MCP client's HTTP setup and complete Plane OAuth in the browser.
  2. In Codex, run codex mcp add plane --url https://mcp.plane.so/http/mcp, then codex mcp login plane and codex mcp list.
  3. In Claude Code, run claude mcp add --transport http plane https://mcp.plane.so/http/mcp and authenticate with /mcp or claude mcp login plane.
  4. For a self-hosted/private Plane instance, use the documented local command uvx plane-mcp-server stdio and set PLANE_API_KEY, PLANE_WORKSPACE_SLUG, plus PLANE_BASE_URL if not using the default API host.
  5. For token-based hosted automation, use https://mcp.plane.so/http/api-key/mcp and both required headers. Keep credentials in environment variables or a secret store.
  6. Verify with a read-only project/work-item listing before attempting writes.
Tools 15+

Plane docs state the hosted 0.3.3 server exposes 30 resource tools and 207 actions. The 15 stored resource-tool names are a partial subset; each tool dispatches multiple resource actions.

  • workitem

    Resource tool for listing, searching, creating, updating, archiving, and deleting work items; action parameter selects operation.

    01
  • workitem_comment

    Resource tool for listing, retrieving, creating, updating, and deleting work-item comments.

    02
  • workitem_activity

    Read work-item change history.

    03
  • workitem_attachment

    List, read, download, upload, and delete work-item attachments.

    04
  • workitem_link

    Manage external links attached to work items.

    05
  • workitem_relation

    Manage relations and dependencies between work items.

    06
  • work_log

    Manage time logs for work items.

    07
  • workitem_type

    Manage workspace/project work-item types.

    08
  • workitem_property

    Manage custom work-item properties and values.

    09
  • project_estimate

    Manage project estimate systems and estimate points.

    10
  • cycle

    Manage cycles and their work items.

    11
  • module

    Manage project modules and associated work items.

    12
  • milestone

    Manage project milestones and linked work.

    13
  • initiative

    Manage workspace initiatives and linked projects/work items.

    14
  • get_pql_reference

    Retrieve brief or full Plane Query Language reference; only documented tool without an action parameter.

    15

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

Limitations and notes
  • Version 0.3.3 tool reference says 30 tools and 207 actions, but another line in current server guide says 30 tools; prior versions exposed 177 per-operation tools and are deprecated.
  • SSE endpoint is deprecated.
  • Many features are gated by Plane plan, API availability, and user role.
  • Server performs actions as the authenticated user; it has write and destructive operations.
  • Hosted service cannot reach private self-hosted instances; use stdio or self-hosted server.
  • The server itself is MIT licensed, but usable Plane capabilities remain subject to the account plan.
Original sources
  • official tool reference

    Current Plane docs state hosted version 0.3.3 exposes 30 resource tools covering 207 actions. The 15 stored names are a partial representative inventory; tools are action-dispatch resources and older per-operation names are not current tools.

  • official documentation or source

    Current Plane docs state hosted version 0.3.3 exposes 30 resource tools covering 207 actions. The 15 stored names are a partial representative inventory; tools are action-dispatch resources and older per-operation names are not current tools.

Documentation checked 2026-10-28T12:55:35.000Z. Connection has not been runtime tested.

Similar tools