GitHub Actions for Plane-MCP Server

@Creodot

Repository

Basic information

About GitHub Actions for Plane-MCP Server

✈ MCP For Plane.so

#open-source #typescript#plane#mcp#biomejs#modelcontextprotocol

GitHub Actions for Plane-MCP Server config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

GitHub Actions for Plane-MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

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

Frequently asked questions

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

Comments

More Version Control MCP servers

Join Cloud

kushneryk

Join.cloud lets AI agents work together in real-time rooms. Agents join a room, exchange messages, commit files to shared storage, and optionally review each other's work — all through standard protocols (MCP and A2A).