plane-mcp-server
Allows configuring Gitea authentication settings for the Plane instance.
Allows configuring GitHub authentication settings for the Plane instance.
Allows configuring GitLab authentication settings for the Plane instance.
Allows configuring Google authentication settings for the Plane instance.
Allows configuring Intercom chat integration settings for the Plane instance.
Handles file uploads to MinIO/S3 storage via a presigned upload flow for asset management.
Allows configuring Unsplash image integration settings for the Plane instance.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@plane-mcp-serverCreate issue 'Fix login bug' in project 'Website'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Plane MCP Server
A comprehensive Model Context Protocol (MCP) server for Plane CE — the open-source project management tool.
56 tools covering pages, assets, work items, projects, modules, cycles, labels, states, members, invitations, and instance/workspace customization.
Key Features
Rich page editing — Write in Markdown, auto-converted to Plane-compatible HTML with proper editor classes
Image uploads — 3-step presigned upload flow wrapped in a single tool call
Fixed page reads — Returns readable HTML content (not the raw Yjs CRDT binary)
Content append — Add to existing pages without replacing everything
Full CRUD — Complete management for work items, projects, modules, cycles, labels, and states
Comments & activity — Add comments to issues, view activity history
Member management — Invite users, manage workspace/project membership, control roles (Guest/Viewer/Member/Admin)
Instance & workspace customization — Manage instance config, workspace settings, logo uploads, user profiles
Dual auth — v1 API key for public endpoints + session auth for internal APIs (pages, assets, customization)
Related MCP server: Plane MCP Server
Quick Start
1. Install
git clone https://github.com/philipvanlewis/plane-mcp-server.git
cd plane-mcp-server
npm install
npm run build2. Configure
Copy .env.example to .env and fill in your Plane CE details:
cp .env.example .envPLANE_BASE_URL=http://localhost # Your Plane CE instance
PLANE_WORKSPACE_SLUG=my-workspace # Workspace slug from URL
PLANE_API_KEY=plane_api_xxx # Settings → API Tokens
PLANE_EMAIL=admin@example.com # Login email
PLANE_PASSWORD=your-password # Login password3. Add to Claude Code
Add to your .mcp.json:
{
"mcpServers": {
"plane": {
"command": "node",
"args": ["/path/to/plane-mcp-server/dist/index.js"],
"cwd": "/path/to/plane-mcp-server"
}
}
}Tools (56)
Pages (9)
Tool | Description |
| List all pages in a project |
| Get page metadata + readable HTML content |
| Get page content with optional class stripping or plain text conversion |
| Create page with optional content in one call (accepts markdown) |
| Update page metadata (title, access) |
| Replace page body (markdown auto-converted to Plane HTML) |
| Append to existing page without replacing |
| Insert uploaded image asset into page with alignment/caption |
| Delete a page |
Assets (2)
Tool | Description |
| Upload file from local path or base64 (3-step presigned flow, max 5MB) |
| Delete an uploaded asset |
Work Items (10)
Tool | Description |
| List issues with state/priority/assignee/label filters |
| Get full issue details |
| Create issue (markdown description, sub-issues, dates) |
| Update any issue field |
| Delete an issue |
| List all comments on an issue |
| Add a comment (accepts markdown) |
| Add a URL link to an issue |
| Get issue activity history |
Projects (4)
Tool | Description |
| List all workspace projects |
| Get project details |
| Create a project |
| Update project settings |
Modules (5)
Tool | Description |
| List all modules |
| Get module details |
| Create a module |
| Add issues to a module |
| Remove an issue from a module |
Cycles (5)
Tool | Description |
| List all cycles (sprints) |
| Get cycle details |
| Create a cycle |
| Add issues to a cycle |
| Remove an issue from a cycle |
Customization (8)
Tool | Description |
| Get instance settings (name, version, edition, domain, auth config) |
| Update instance name, domain, telemetry |
| Get all 32 instance config keys (auth, SMTP, AI, Unsplash, etc.) |
| Update instance config keys (enable signup, SMTP, AI provider, etc.) |
| Get workspace settings (name, slug, logo, org size, timezone) |
| Update workspace name, org size, timezone |
| Upload workspace logo via presigned URL flow |
| Get current user profile (display name, avatar, theme) |
| Update display name and theme preferences |
States (2) · Labels (3) · Members (2) · Utility (1)
Tool | Description |
| List workflow states |
| Create a workflow state |
| List project labels |
| Create a label |
| Delete a label |
| List project members |
| List workspace members |
| Invite a user to the workspace by email |
| List pending workspace invitations |
| Revoke a pending workspace invitation |
| Add a workspace member to a project |
| Remove a member from a project |
| Check v1 API + session auth status |
How Content Formatting Works
When you write content in Markdown, the server automatically:
Converts Markdown to HTML using marked
Adds Plane's TipTap editor CSS classes (
editor-heading-block,editor-paragraph-block, etc.)Passes the formatted HTML to Plane's API
This means pages render correctly in Plane's editor — headings, paragraphs, code blocks, tables, lists, and blockquotes all display properly.
Image Embedding
Images use Plane's <image-component> custom element:
1. Upload: plane-asset-upload → returns asset_id
2. Embed: plane-page-insert-image with asset_id → inserts into pageThe server handles the full presigned upload flow (create record → upload to MinIO/S3 → mark complete) in a single tool call.
Instance Configuration
The customization tools give full control over the Plane CE instance:
Instance settings: plane-instance-get / plane-instance-update
32 config keys: plane-instance-config-get / plane-instance-config-update
Workspace branding: plane-workspace-update / plane-workspace-logo-upload
User preferences: plane-user-profile-get / plane-user-profile-updateConfig key categories: AUTHENTICATION, GOOGLE, GITHUB, GITLAB, GITEA, SMTP, AI, UNSPLASH, WORKSPACE_MANAGEMENT, INTERCOM
Architecture
src/
├── index.ts # MCP server bootstrap (stdio transport)
├── config.ts # Zod-validated env config
├── client.ts # Dual-auth HTTP client (v1 API key + session cookies + presigned uploads)
├── tools/ # 11 tool modules, 51 tools total
│ ├── pages.ts # Rich page editing with markdown support
│ ├── assets.ts # Presigned file uploads to MinIO/S3
│ ├── work-items.ts # Issues + comments + links + activity
│ ├── customization.ts # Instance, workspace, and user profile management
│ ├── projects.ts # Project CRUD
│ ├── modules.ts # Module management
│ ├── cycles.ts # Cycle/sprint management
│ ├── states.ts # Workflow states
│ ├── labels.ts # Label management
│ ├── members.ts # Member queries
│ └── utility.ts # Auth status diagnostics
└── utils/
├── html.ts # Markdown → Plane HTML + editor class injection
├── errors.ts # Error formatting for MCP responses
└── logger.ts # Stderr loggerKnown Issues / API Quirks
Plane v1 API ignores query parameter filters
The /api/v1/workspaces/{slug}/projects/{id}/issues/ endpoint ignores ?state=, ?assignees=, and other query parameter filters — it always returns all items regardless of the parameters passed. This is a Plane CE API bug (confirmed on v0.23).
Impact: Any automation that needs filtered results (e.g., "get all Todo items assigned to user X") must fetch all items and filter client-side.
Workaround: The plane-work-item-list tool accepts state, priority, assignee, and label filter parameters and applies them client-side after fetching the full list. If you are building your own automation on top of the Plane API, you will need to do the same.
Discovered: 2026-03-26, when a scheduled trigger failed to pick up a specific work item because the API returned unfiltered results and the caller trusted the query parameters.
Requirements
Node.js 18+
Plane CE instance (tested with v0.23+)
API key + admin email/password for full access
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/philipvanlewis/plane-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server