Plane MCP Server — Manage Issues from Agents

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.