Plane MCP Server

Created By
gh-Constanta year ago
Overview

what is Plane MCP Server?

Plane MCP Server is an MCP (Model Context Protocol) server designed to facilitate interaction between AI assistants and the Plane project management platform.

how to use Plane MCP Server?

To use the Plane MCP Server, clone the repository, install the necessary dependencies, configure your environment variables, build the TypeScript code, and run the server. For development, you can use the automatic reloading feature.

key features of Plane MCP Server?

  • List workspaces, projects, cycles, modules, and issues
  • Create, update, and delete issues
  • Add comments to issues
  • Filter issues by various criteria
  • Retrieve details of Plane entities (projects, cycles, etc.)

use cases of Plane MCP Server?

  1. Managing project tasks and issues in the Plane platform.
  2. Automating project updates and status checks through AI assistants.
  3. Facilitating team collaboration by managing comments and issues.

FAQ from Plane MCP Server?

  • What is the purpose of the Plane MCP Server?

It allows AI assistants to interact with the Plane project management platform for better task management.

  • How do I set up the Plane MCP Server?

Follow the setup instructions in the documentation, including cloning the repo and configuring your environment.

  • Can I run the server in development mode?

Yes! You can run the server in development mode with automatic reloading using the command npm run dev.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
gh-Constant
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago