PlaneSAFE
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[](https://archestra.ai/mcp-catalog/kelvin6365__plane-mcp-server) [](https://smithery.ai/server/@kelvin6365/plane-mcp-server)
[](https://mseep.ai/app/kelvin6365-plane-mcp-server) [](https://mseep.ai/app/0af9cef9-605a-411c-98a2-cc7156ab1e7d)
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.
Features
- List all projects in your Plane workspace
- Get detailed information about specific projects
- Create new issues with customizable properties
- List and filter issues from projects
- Get detailed information about specific issues
- Update existing issues with new information
Prerequisites
- Node.js 22.x or higher
- A Plane.so API key
- A Plane.so workspace
Installation
Option 1: Using Smithery
The quickest way to get started is to use Smithery to install the server directly:
# Install to Claude for Desktop npx -y @smithery/cli install @kelvin6365/plane-mcp-server --client claude
This command will automatically set up the Plane MCP Server for use with Claude. After installation, you'll need to configure the server with your Plane API key and workspace slug through the Claude settings.
Valid client options are: claude, cline, windsurf, roo-cline, witsy, enconvo, cursor
Example
74a5099c4a4aOBSERVED · 2026-10-08Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add plane-mcp-server --env PLANE_API_KEY=${PLANE_API_KEY} -- npx -y [email protected]{
"mcpServers": {
"plane-mcp-server": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"PLANE_API_KEY": "${PLANE_API_KEY}"
}
}
}
}Exposed tools (6)
4 read · 1 write · 1 destructive. Blast radius: 1 tool can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.
| Tool | Risk | Description |
|---|---|---|
create-issue | write | Create a new issue in a project |
get-issue | read | Get detailed information about a specific issue |
get-project | read | Get detailed information about a specific project |
list-issues | read | List issues from a project |
list-projects | read | List all projects in the workspace |
update-issue | destructive | Update an existing issue in a project, delete just update the issue title with |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (1 observation(s))
- Network
- declared (1 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (2)
update-issue
@modelcontextprotocol/sdk, dotenv, typescript, shx, @types/node
Gates applied: no_behavioural_pass.
74a5099c4a4afull audit observations/trust-audit/mcp-server/kelvin6365__plane-1.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | 74a5099c4a4a | SAFE | B | 89 | first audit |
Questions
What tools does Plane expose?
6 in total: 4 read-only, 1 that write, and 1 that can delete or overwrite (update-issue). Every one is listed on this page with its risk.
Is Plane safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B. Separately from the audit: 1 of its tools can destroy data, so scope the token you give it to what you actually need.
What credentials does Plane need?
It reads PLANE_API_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does Plane run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as plane-mcp-server at 0.1.0.
How current is this page?
The grade is for one exact copy of the source (74a5099c4a4a), read on 2026-10-08. The repository is watched and re-audited when it changes.