# Plane MCP Server — Manage Issues from Agents

> Plane MCP Server brings Plane projects and work items into MCP: uvx for local stdio or remote HTTP via mcp.plane.so. Verified 220★; setup ~5–12 minutes.

## Install

Merge the JSON below into your `.mcp.json`:

## Quick Use

```bash
# Local stdio (recommended):
# command: uvx
# args: ["plane-mcp-server","stdio"]
# env: PLANE_API_KEY=... PLANE_WORKSPACE_SLUG=... PLANE_BASE_URL=https://api.plane.so
# Remote HTTP: npx mcp-remote@latest https://mcp.plane.so/http/mcp
```

## Intro

Plane MCP Server brings Plane projects and work items into MCP: uvx for local stdio or remote HTTP via mcp.plane.so. Verified 220★; setup ~5–12 minutes.

**Best for:** Teams using Plane who want agents to create and triage work items

**Works with:** Any MCP client (stdio via uvx; remote HTTP via npx mcp-remote)

**Setup time:** 5-12 minutes

### Key facts (verified)

- GitHub: 220 stars · 92 forks · pushed 2026-05-13.
- License: MIT · owner avatar + repo URL verified via GitHub API.
- README-verified entrypoint: `uvx plane-mcp-server stdio`.

## Main

- Use the uvx stdio transport for local, key-based access when you need predictable auth and low-latency tool calls.

- If you need a hosted option, README documents remote HTTP endpoints with OAuth or PAT headers via mcp.plane.so.

- Treat it as a work-item backbone: list/create/update issues and cycles so agents can turn plans into tracked execution.

### Source-backed notes

- README recommends uvx for stdio transport and shows MCP client JSON using `command: uvx` + `args: ["plane-mcp-server","stdio"]`.
- README documents remote HTTP endpoints (OAuth and PAT token variants) and suggests npx `mcp-remote@latest` for clients without native support.
- README lists supported transports: stdio, SSE (legacy), and streamable HTTP.

### FAQ

- **Do I need Node.js for local use?**: No — README says stdio transport works with Python (uvx); Node is for remote transports.
- **Is SSE still recommended?**: No — README marks SSE as legacy and recommends HTTP transports instead.
- **Can I use OAuth instead of API keys?**: Yes — README documents OAuth remote HTTP at mcp.plane.so.

## Source & Thanks

> Source: https://github.com/makeplane/plane-mcp-server
> License: MIT
> GitHub stars: 220 · forks: 92

---

<!-- ZH -->

## Quick Use

```bash
# Local stdio (recommended):
# command: uvx
# args: ["plane-mcp-server","stdio"]
# env: PLANE_API_KEY=... PLANE_WORKSPACE_SLUG=... PLANE_BASE_URL=https://api.plane.so
# Remote HTTP: npx mcp-remote@latest https://mcp.plane.so/http/mcp
```

## Intro

Plane MCP Server 把 Plane 项目/工单接入 MCP：本地用 uvx stdio，或通过 mcp.plane.so 远程 HTTP。已验证 220★；约 5–12 分钟可接入。

**Best for:** 使用 Plane 且希望让 agent 创建/分流工单的团队

**Works with:** 任意 MCP 客户端（uvx stdio；或用 npx mcp-remote 连接远程 HTTP）

**Setup time:** 5-12 minutes

### Key facts (verified)

- GitHub：220 stars · 92 forks；最近更新 2026-05-13。
- 许可证：MIT；作者头像与仓库链接均已通过 GitHub API 复核。
- README 中核对过的入口命令：`uvx plane-mcp-server stdio`。

## Main

- 本地优先：用 uvx 的 stdio（API key + workspace slug）获得更可控的认证与更稳定的延迟。

- 需要托管服务时，README 提供 mcp.plane.so 的远程 HTTP（OAuth 或 PAT header）接入方式。

- 把它当作工单骨架：列出/创建/更新 work items 与 cycles，让 agent 的计划可落地到可跟踪执行。

### Source-backed notes

- README 推荐 stdio 使用 uvx，并给出 `command: uvx` + `args: ["plane-mcp-server","stdio"]` 的 MCP 配置示例。
- README 说明远程 HTTP（OAuth 与 PAT）端点，并建议用 npx `mcp-remote@latest` 连接不原生支持远程的客户端。
- README 列出多种传输方式：stdio、SSE（legacy）以及 streamable HTTP。

### FAQ

- **本地使用需要 Node.js 吗？**：不需要。README 表示 stdio 可用 Python（uvx）；Node 主要用于远程传输。
- **还建议用 SSE 吗？**：不建议。README 标注 SSE 为 legacy，推荐改用 HTTP 传输。
- **能用 OAuth 吗？**：可以。README 说明 mcp.plane.so 的 OAuth 远程 HTTP 接入。

## Source & Thanks

> Source: https://github.com/makeplane/plane-mcp-server
> License: MIT
> GitHub stars: 220 · forks: 92


---
Source: https://tokrepo.com/en/workflows/plane-mcp-server-manage-issues-from-agents
Author: MCP Hub