Plane Agent

CLI or API | MCP

Version: 2.3.4

Documentation — Installation, deployment, usage across the API, CLI, and MCP interfaces, and guidance for provisioning a self-hosted Plane instance are maintained in the official documentation.

Table of Contents

• Overview
• Key Features
• CLI or API
• MCP
  • Available MCP Tools
  • MCP Configuration Examples
  • Dynamic Tool Selection & Visibility
  • Running the Agent CLI
  • Docker Compose Orchestration
• Security & Governance
• Environment Variables
• Installation
• Documentation
• Repository Owners
• Contribute

Overview

Plane Agent is a production-grade Agent and Model Context Protocol (MCP) server designed to interface directly with Plane MCP Agent.

Key Features

• Consolidated Action-Routed MCP Tools: Minimizes token overhead and eliminates tool bloat in LLM contexts by grouping methods into optimized, togglable tool modules.
• Enterprise-Grade Security: Complete support for Eunomia policies, OIDC token delegation, and granular execution context tracking.
• Native Telemetry & Tracing: Out-of-the-box OpenTelemetry exports and native Langfuse tracing.

CLI or API

This agent wraps the Plane MCP Agent API. The operator can interact with it programmatically or via its integrated execution entrypoints.

Detailed instructions on how to use the underlying API wrappers, extended schema bindings, and developer SDK references are maintained in docs/index.md.

MCP

This server use dynamic Action-Routed tools to optimize token overhead and maximize IDE compatibility.

Available MCP Tools

This table is auto-generated from the live server — do not edit by hand.

Condensed action-routed tools (MCP_TOOL_MODE=condensed)

Verbose 1:1 API-mapped tools (MCP_TOOL_MODE=verbose or both)

14 action-routed tool(s) · 102 verbose 1:1 tool(s). Each is enabled unless its <DOMAIN>TOOL toggle is set false; MCP_TOOL_MODE selects the surface (intent default — the six verb-tools, granular set loaded on demand · condensed action-routed · verbose 1:1 · both). Auto-generated — do not edit.

Detailed tool schemas, parameter shapes, and validation constraints are preserved in docs/index.md.

Dynamic Tool Selection & Visibility

This MCP server supports dynamic toolset selection and visibility filtering at runtime. This allows the operator to restrict the set of exposed tools to prevent blowing up the LLM's context window.

The operator can configure tool filtering via multiple input channels:

• CLI Arguments: Pass --tools or --toolsets (or their disabled counterparts --disabled-tools and --disabled-toolsets) during startup.
• Environment Variables: Define standard environment variables:
  • MCP_ENABLED_TOOLS / MCP_DISABLED_TOOLS
  • MCP_ENABLED_TAGS / MCP_DISABLED_TAGS
• HTTP SSE Request Headers: Pass custom headers during transport initialization:
  • x-mcp-enabled-tools / x-mcp-disabled-tools
  • x-mcp-enabled-tags / x-mcp-disabled-tags
• HTTP SSE Request Query Parameters: Append query parameters directly to the operator's transport connection URL:
  • ?tools=tool1,tool2
  • ?tags=tag1

When query strings or parameters are supplied, an LLM-free Knowledge Graph resolution layer (using DynamicToolOrchestrator) matches query intents against known tool tags, names, or descriptions, with safe fallback and automated 24-hour background cache refreshing.

MCP Configuration Examples

Install the connector-focused [mcp] extra. Examples use plane-agent[mcp] to add FastMCP / FastAPI through agent-connector-sdk; the required Agent Connector SDK core still carries epistemic-graph[full]. The [agent-runtime] extra additionally enables model orchestration.

stdio Transport (local IDEs — Cursor, Claude Desktop, VS Code)

{
  "mcpServers": {
    "plane-mcp": {
      "command": "uvx",
      "args": [
        "--from",
        "plane-agent[mcp]",
        "plane-mcp"
      ],
      "env": {
        "MCP_TOOL_MODE": "intent",
        "CYCLESTOOL": "True",
        "EPICSTOOL": "True",
        "INITIATIVESTOOL": "True",
        "INTAKETOOL": "True",
        "KGTOOL": "True",
        "LABELSTOOL": "True",
        "MILESTONESTOOL": "True",
        "MODULESTOOL": "True",
        "PAGESTOOL": "True",
        "PLANE_API_KEY": "your_plane_api_key_here",
        "PLANE_BASE_URL": "https://api.plane.so",
        "PLANE_KG_INGEST": "true",
        "PLANE_TLS_PROFILE": "system",
        "PROJECTSTOOL": "True",
        "STATESTOOL": "True",
        "USERSTOOL": "True",
        "WORKSPACESTOOL": "True",
        "WORK_ITEMSTOOL": "True"
      }
    }
  }
}

Runtime references require an alias-aware launcher such as Arbora. Other launchers must omit those entries and inject the resolved values through their own runtime secret boundary.

Streamable-HTTP Transport (networked / production)

{
  "mcpServers": {
    "plane-mcp": {
      "command": "uvx",
      "args": [
        "--from",
        "plane-agent[mcp]",
        "plane-mcp",
        "--transport",
        "streamable-http",
        "--port",
        "8000"
      ],
      "env": {
        "TRANSPORT": "streamable-http",
        "HOST": "127.0.0.1",
        "PORT": "8000",
        "MCP_TOOL_MODE": "intent",
        "CYCLESTOOL": "True",
        "EPICSTOOL": "True",
        "INITIATIVESTOOL": "True",
        "INTAKETOOL": "True",
        "KGTOOL": "True",
        "LABELSTOOL": "True",
        "MILESTONESTOOL": "True",
        "MODULESTOOL": "True",
        "PAGESTOOL": "True",
        "PLANE_API_KEY": "your_plane_api_key_here",
        "PLANE_BASE_URL": "https://api.plane.so",
        "PLANE_KG_INGEST": "true",
        "PLANE_TLS_PROFILE": "system",
        "PROJECTSTOOL": "True",
        "STATESTOOL": "True",
        "USERSTOOL": "True",
        "WORKSPACESTOOL": "True",
        "WORK_ITEMSTOOL": "True"
      }
    }
  }
}

Alternatively, connect to a pre-deployed Streamable-HTTP instance by url:

{
  "mcpServers": {
    "plane-mcp": {
      "url": "http://localhost:8000/plane-mcp/mcp"
    }
  }
}

Run a reviewed container image as a least-privilege stdio child (no listener or published port):

docker run -i --rm \
  --read-only \
  --cap-drop=ALL \
  --security-opt=no-new-privileges \
  --pids-limit=256 \
  --tmpfs /tmp:rw,noexec,nosuid,nodev,size=64m \
  -e TRANSPORT=stdio \
  -e MCP_TOOL_MODE=intent \
  -e CYCLESTOOL=True \
  -e EPICSTOOL=True \
  -e INITIATIVESTOOL=True \
  -e INTAKETOOL=True \
  -e KGTOOL=True \
  -e LABELSTOOL=True \
  -e MILESTONESTOOL=True \
  -e MODULESTOOL=True \
  -e PAGESTOOL=True \
  -e PLANE_API_KEY=your_plane_api_key_here \
  -e PLANE_BASE_URL=https://api.plane.so \
  -e PLANE_KG_INGEST=true \
  -e PLANE_TLS_PROFILE=system \
  -e PROJECTSTOOL=True \
  -e STATESTOOL=True \
  -e USERSTOOL=True \
  -e WORKSPACESTOOL=True \
  -e WORK_ITEMSTOOL=True \
  registry.example.invalid/plane-agent@sha256:<digest> plane-mcp

For containerized network HTTP, supply an authenticated TLS ingress (or direct server TLS), exact MCP_ALLOWED_HOSTS, and an exact trusted-proxy CIDR policy through the operator-owned deployment profile. The generator does not emit an unauthenticated non-loopback listener.

Auto-generated from the code-read env surface (MCP_TOOL_MODE + package vars) — do not edit.

Additional Deployment Options

plane-agent can run as a local stdio process or container, or behind a remote network boundary. The Deployment guide carries the detailed transport contract.

• Local container — launch a reviewed immutable image as a least-privilege stdio child with no listener or published port.
• Remote URL — connect through an operator-supplied authenticated HTTPS ingress. Keep its URL, outbound identity references, trust profile, and exact MCP_ALLOWED_HOSTS in AgentConfig.

Agent

Set credentials

export PLANE_BASE_URL="your_value" export PLANE_WORKSPACE_SLUG="your_value" export DEBUG="your_value" export PYTHONUNBUFFERED="your_value" export PLANE_API_KEY="your_value"

Connector-focused MCP server (includes the shared graph engine)

uv pip install "plane-agent[mcp]"

Everything (development)

uv pip install "plane-agent[all]" # or: python -m pip install "plane-agent[all]"

### Container images (`:mcp`)

One multi-stage `docker/Dockerfile` builds the MCP-only image (`--target mcp`):

| Image tag | Build target | Contents | Entrypoint |
|-----------|--------------|----------|------------|

```bash

agent (immutable agent digest) with a co-located :mcp sidecar.

Knowledge-graph database (epistemic-graph)

Agent Connector SDK core dependency (epistemic-graph[full]). The [mcp] extra keeps deployments can use the bundled engine. For production or shared state, run epistemic-graph as a dedicated database service and configure the runtime to use it. Deployment recipes (single-node + Raft HA), connection configuration, and architecture diagrams are documented in the epistemic-graph deployment guide.

Documentation

The complete documentation is published as the official documentation site and is the recommended reference for installation, deployment, and day-to-day operation.

Repository Owners

Contribute

Contributions are welcome! Please ensure code quality by running local checks before submitting pull requests:

• Format code using ruff format .
• Lint code using ruff check .
• Validate type-safety with mypy .
• Run test suites using pytest

Deploy with agent-connector-sdk-deployment

Provision this package with the consolidated agent-connector-sdk-deployment workflow. It selects an installed-package, editable-source, or immutable-container path; records only runtime secret and TLS-profile references in AgentConfig; and runs doctor, registration, policy, observability, and rollback gates. Ask your agent to "deploy plane-agent with agent-connector-sdk-deployment".

The repository embeds no deployment profile, credential value, certificate path, or environment-specific endpoint. Supply those at runtime through AgentConfig and the configured secret provider.

Governed capability contract

This package ships a compact canonical skill surface with specialist procedures kept as referenced workflows. The current MCP tools, skill metadata, connector_manifest.yml, ontology, mappings, shapes, fixtures, migrations, tool-schema fingerprints, and certification metadata form one versioned capability contract. Validate them together; do not rely on stale tool names or historical per-task skill wrappers.

Runtime endpoints, credentials, certificate trust, tenant identity, retention, and observability policy are deployment inputs and are never packaged values. See Configuration, trust, and privacy before enabling a network transport, connector ingestion, Arbora delegation, or trace export.