MCP server that exposes the Plane project management API to AI clients, built with FastMCP.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"plane-mcp-oss","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Plane MCP Server [](https://github.com/abelsr/plane-mcp-oss/actions/workflows/ci.yml) [](https://pypi.org/project/plane-mcp-oss/) [](LICENSE) [](pyproject.toml) [](https://gofastmcp.com) [](https://modelcontextprotocol.io) An [MCP](https://modelcontextprotocol.io) server that exposes the [Plane](https://plane.so) REST API to AI clients (Claude, Cursor, VS Code, Codex, …). Built with [FastMCP](https://gofastmcp.com). It authenticates as a Plane personal access token and acts on a single workspace, giving the model tools to read and manage projects, work items, states, labels, cycles, modules, members and comments. ## Requirements - Python 3.10+ - A Plane account and a **personal access token**: *Plane → Profile settings → Personal access tokens → Add personal access token* - Your **workspace slug** — the segment in your Plane URL: `https://app.plane.so/<workspace-slug>/projects/` ## Install From PyPI — package `plane-mcp-oss`: ```bash uvx plane-mcp-oss # run without installing # or pip install plane-mcp-oss # installs the `plane-mcp` and `plane-mcp-oss` commands ``` From source: ```bash uv sync # installs fastmcp + httpx into .venv # or, without uv: pip install -e . ``` ## Configure The server targets one Plane **instance** and one **workspace**. Settings are resolved with the following precedence (highest wins): 1. CLI flags (`--base-url`, `--workspace`, `--api-key`) 2. Process environment variables 3. A `.env` file in the working directory (loaded automatically) 4. Built-in defaults | Variable | Alias | Req…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.