Plane▌
by disrex-group
Seamlessly integrate your Plane project management platform with 76 tools for efficient task and issue tracking.
Integrates with Plane's project management platform through 76 specialized tools for complete issue, project, module, cycle, label, state, comment, attachment, time tracking, custom property, sub-issue, and transfer operations with cursor-based pagination for efficient data handling.
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / Product managers tracking development progress
- / Engineering teams automating project workflows
- / AI-assisted project management and reporting
capabilities
- / Manage issues and sub-issues in Plane projects
- / Update project details, modules and cycles
- / Track time spent on tasks
- / Handle comments and attachments
- / Organize work with labels and states
- / Transfer issues between projects
what it does
Connects to your Plane.so project management workspace to manage issues, projects, and related data directly through AI assistants.
about
Plane is a community-built MCP server published by disrex-group that provides AI assistants with tools and capabilities via the Model Context Protocol. Seamlessly integrate your Plane project management platform with 76 tools for efficient task and issue tracking. It is categorized under productivity.
how to install
You can install Plane in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
Plane is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
Plane MCP Server
A Model Context Protocol (MCP) server that enables LLMs to interact with Plane.so, allowing them to manage projects and issues through Plane's API. Using this server, LLMs like Claude can directly interact with your project management workflows while maintaining user control and security.
⚠️ Important: This MCP server is designed specifically for Plane Cloud instances. It only works with workspaces hosted on
https://app.plane.so/workspace-slug. If you're using a self-hosted Plane installation, this server will not be compatible.
Note: This is an enhanced fork of the original kelvin6365/plane-mcp-server, extended with comprehensive Plane API functionality including states, modules (sprints), cycles, labels, team management, comments, links, attachments, time tracking, and issue types.
Features
Pagination Support
- Cursor-based pagination for all list operations (projects, issues, modules, cycles, labels)
- Configurable page sizes up to 100 items per page
- Navigation through large datasets with next/previous cursors
- Consistent pagination across all list tools
Project Management
- List all projects in your Plane workspace with pagination
- Get detailed information about specific projects
Issue Management
- Create new issues with customizable properties
- List and filter issues from projects
- Get detailed information about specific issues
- Update existing issues with new information
State Management
- List all states in a project
- Get detailed information about specific states
- Create new states with customizable properties
- Update existing states
- Delete states from projects
Module (Sprint) Management
- List all modules (sprints) in a project
- Get detailed information about specific modules
- Create new modules with customizable properties
- Update existing modules
- Delete modules from projects
- List issues assigned to specific modules
- Add/remove issues to/from modules
Cycle Management
- List all cycles in a project
- Get detailed information about specific cycles
- Create new cycles with customizable properties
- Update existing cycles
- Delete cycles from projects
- List issues assigned to specific cycles
- Add/remove issues to/from cycles
Label Management
- List all labels in a project
- Get detailed information about specific labels
- Create new labels with customizable properties
- Update existing labels
- Delete labels from projects
Team & Workspace Management
- List all members in the workspace
- List members assigned to specific projects
Issue Comments & Communication
- List, create, update, and delete comments on issues
- Track discussion history and collaboration
Issue Links & External References
- Attach external links to issues (documentation, PRs, etc.)
- Manage and update issue-related URLs
File Attachments
- List file attachments for issues
- Generate upload URLs for new attachments
Issue Activity & History
- View complete activity history for issues
- Track all changes and updates
Time Tracking (Worklogs)
- Log time spent on specific issues
- View project-wide time tracking summaries
- Update and manage worklog entries
Custom Issue Types
- Create and manage custom issue types
- Define project-specific issue categories
Intake Issues (Triage)
- Handle intake/inbox issues for triage
- Manage issue submissions before project assignment
Custom Issue Properties
- Create and manage custom properties for issue types
- Support for various property types (text, number, date, options, boolean)
- Configure dropdown options for select properties
- Set required fields and validation rules
Sub-issues & Relations
- Create hierarchical issue structures with parent-child relationships
- Convert existing issues to sub-issues
- List and manage sub-issue trees
- Convert sub-issues back to regular issues
Issue Transfer Operations
- Transfer issues between cycles for better sprint management
- Bulk move issues to different project phases
Prerequisites
- Node.js 22.x or higher
- A Plane.so API key
- A Plane.so workspace
Installation
Option 1: Using NPM (Recommended)
The quickest way to get started is to use the published npm package:
{
"mcpServers": {
"plane": {
"command": "npx",
"args": [
"-y",
"@disrex/plane-mcp-server"
],
"env": {
"PLANE_API_KEY": "your_plane_api_key_here",
"PLANE_WORKSPACE_SLUG": "your_workspace_slug_here"
}
}
}
}
Add this configuration to your Claude for Desktop config file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Option 2: Manual Setup
If you prefer to set up the server manually, follow these steps:
- Clone this repository:
git clone https://github.com/disrex-group/plane-mcp-server.git
cd plane-mcp-server
- Install dependencies:
npm install
- Build the server:
npm run build
Getting Your Plane API Credentials
To use this MCP server, you'll need:
- Plane API Key: Generate one from your personal settings (not workspace settings) in Plane
- Workspace Slug: Found in your Plane workspace URL (e.g.,
https://app.plane.so/workspace-slug/)
After obtaining these credentials, use them in your Claude configuration as shown in the installation options above.
Available Tools
Note: Tool names use hyphens (e.g.,
list-projects), not underscores. The server will automatically convert underscores to hyphens for compatibility.
list-projects
Lists all projects in your Plane workspace with pagination support.
Parameters:
per_page(optional): Number of items per page (default: 100, max: 100)cursor(optional): Pagination cursor in format 'value:offset:is_prev'
Example:
{
"per_page": 50
}
Example with pagination:
{
"per_page": 25,
"cursor": "project_name:25:false"
}
get-project
Gets detailed information about a specific project.
Parameters:
project_id: ID of the project to retrieve
Example:
{
"project_id": "01abc123-4567-89de-0123-456789abcdef"
}
create-issue
Creates a new issue in a specified project.
Parameters:
project_id: ID of the project where the issue should be createdname: Title of the issuedescription_html: HTML description of the issue (required by Plane API)priority(optional): Priority of the issue ("urgent", "high", "medium", "low", "none")state_id(optional): ID of the state for this issueassignees(optional): Array of user IDs to assign to this issuelabels(optional): Array of label IDs to assign to this issue
Note: The
assigneesandlabelsparameters must be arrays of ID strings. Common errors include providing a dictionary/object instead of an array, or accidentally nesting the entire issue data inside these fields. The server will attempt to handle these cases, but it's best to use the correct format.
Example:
{
"project_id": "01abc123-4567-89de-0123-456789abcdef",
"name": "Implement new feature",
"description_html": "<p>We need to implement the new reporting feature</p>",
"priority": "high",
"assignees": ["user-id-1", "user-id-2"],
"labels": ["446cf3ad-446e-4b7a-8706-14121a0338d7", "ab0c39d4-dcae-4ccd-971a-f4c66d1e7db7"]
}
list-issues
Lists issues from a specified project with optional filtering and pagination.
Parameters:
project_id: ID of the project to get issues fromstate_id(optional): Filter by state IDpriority(optional): Filter by priorityassignee_id(optional): Filter by assignee IDper_page(optional): Number of items per page (default: 100, max: 100)cursor(optional): Pagination cursor in format 'value:offset:is_prev'
Examples:
Basic filtering:
{
"project_id": "01abc123-4567-89de-0123-456789abcdef",
"priority": "high",
"per_page": 20
}
With pagination (first page):
{
"project_id": "01abc123-4567-89de-0123-456789abcdef",
"per_page": 20
}
With pagination (next page using cursor from previous response):
{
"project_id": "01abc123-4567-89de-0123-456789abcdef",
"per_page": 20,
"cursor": "20:1:0"
}
get-issue
Gets detailed information about a specific issue.
Parameters:
project_id: ID of the project containing the issueissue_id: ID of the issue to retrieve
Example:
{
"project_id": "01abc123-4567-89de-0123-456789abcdef",
"issue_id": "01def456-7890-12gh-3456-789ijklmnopq"
}
update-issue
Updates an existing issue in a project.
Parameters:
project_id: ID of the project containing the issueissue_id: ID of the issue to updatename(optional): Updated title of the issuedescription_html(optional): HTML description of the issue (required by Plane API)priority(optional): Updated priority of the issuestate_id(opti
FAQ
- What is the Plane MCP server?
- Plane is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Plane?
- This profile displays 30 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.5 out of 5—verify behavior in your own environment before production use.
Use Cases▌
Extended AI Capabilities
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Context Enhancement
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Workflow Automation
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Implementation Guide▌
Prerequisites
- ›Claude Desktop 0.7.0+ or Cursor IDE with MCP support
- ›Basic understanding of MCP architecture and capabilities
- ›Access credentials for integrated services (if required)
- ›Willingness to experiment and iterate on configuration
Time Estimate
15-60 minutes depending on server complexity
Installation Steps
- 1.Install MCP server: npm install -g [package-name] or via GitHub
- 2.Add server configuration to ~/.claude/mcp.json
- 3.Provide required credentials and configuration
- 4.Restart Claude Desktop to load new server
- 5.Test basic functionality with simple prompts
- 6.Explore capabilities and experiment with use cases
- 7.Document successful patterns for reuse
Troubleshooting
- ⚠MCP server not loading: Check config syntax, verify installation
- ⚠Connection errors: Check network, firewall, credentials
- ⚠Feature not working: Read server docs, check required parameters
- ⚠Performance issues: Monitor resource usage, check for network latency
- ⚠Conflicts with other servers: Check port assignments, namespace collisions
Best Practices▌
✓ Do
- +Read server documentation thoroughly before setup
- +Start with simple use cases to validate functionality
- +Test in non-production environment first
- +Monitor resource usage and performance
- +Keep servers updated for bug fixes and new features
- +Document configuration for team members
- +Use environment variables for sensitive configuration
✗ Don't
- −Don't grant overly permissive access to MCP servers
- −Don't skip reading security considerations in docs
- −Don't expose sensitive data without proper controls
- −Don't run untrusted MCP servers without code review
- −Don't ignore error messages—investigate root cause
💡 Pro Tips
- ★Combine multiple MCP servers for powerful workflows
- ★Create custom MCP servers for your specific needs
- ★Share successful configurations with team
- ★Use MCP inspector for debugging
- ★Join MCP community for tips and troubleshooting
Technical Details▌
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
- Model Context Protocol (MCP)
- JSON-RPC 2.0
- stdio or HTTP transport
Compatibility
- Claude Desktop
- Cursor IDE
- Custom MCP clients
When to Use This▌
✓ Use When
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid When
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.
Integration▌
- →Tool composition: Chain multiple MCP tools in workflows
- →Context augmentation: Provide AI with relevant external data
- →Action delegation: Let AI execute tasks on external systems
- →Bidirectional sync: Keep AI context and external systems in sync
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
List & Promote Your MCP Server
Share your MCP server with the developer community
Ratings
4.5★★★★★30 reviews- ★★★★★Dhruvi Jain· Dec 16, 2024
According to our notes, Plane benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Oshnikdeep· Nov 7, 2024
We wired Plane into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Ganesh Mohane· Oct 26, 2024
Plane is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
- ★★★★★Lucas Smith· Sep 21, 2024
Plane has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Sakshi Patil· Sep 17, 2024
Useful MCP listing: Plane is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Mateo Gupta· Sep 17, 2024
Plane reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Arya Bhatia· Aug 12, 2024
According to our notes, Plane benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Chaitanya Patil· Aug 8, 2024
Plane reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Mateo Khanna· Aug 8, 2024
Useful MCP listing: Plane is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Piyush G· Jul 27, 2024
I recommend Plane for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
showing 1-10 of 30