GitHub Actions for Plane-MCP

What is GitHub Actions for Plane-MCP?

GitHub Actions for Plane-MCP is a Model Context Protocol server that acts as a bridge to the Plane.so API. It allows MCP clients (such as AI assistants) to interact with Plane.so resources—initially Issues—through defined tools.

How to use GitHub Actions for Plane-MCP?

The server requires Node.js v20 or higher and npm. After installing dependencies with npm install, configure your Plane.so API key and workspace slug as environment variables (e.g., PLANE_API_KEY, PLANE_WORKSPACE_SLUG). The server communicates via stdin/stdout and must be launched by an MCP client (like Cursor or Claude App). Tools are invoked by the client using the names plane_get_issue, plane_create_issue, and plane_update_issue.

Key features of GitHub Actions for Plane-MCP

• Provides three MCP tools to manage Plane.so issues
• Uses Zod for input validation and structured error handling
• Built with TypeScript and follows a domain‑driven project structure
• Supports CI, linting, and formatting via Biome
• Open source under the MIT license

Use cases of GitHub Actions for Plane-MCP

• AI assistants fetching issue details from Plane.so workspaces
• Automated creation of issues from natural language prompts
• Updating issue priority, description, or assignees through conversational interfaces

FAQ from GitHub Actions for Plane-MCP

What runtime is required?

Node.js v20 or higher and npm.

How do I obtain a Plane.so API key?

In Plane.so, go to Workspace Icon → Settings → API Tokens → Add API Token.

What tools does the server expose?

Three tools: plane_get_issue, plane_create_issue, and plane_update_issue.

How is the server secured?

The API key is stored in a .env file and must never be committed to version control. Most MCP clients require explicit user approval before executing write operations.

Can I extend the server with new tools?

Yes. Contributors can add new tools by following the documented process: define the tool interface, add validation schemas, implement