Plane MCP server

What the model can do

Plane projects, work items with state, priority, assignees and dates, work-item search, comments, states and workspace members, on Plane Cloud or a self-hosted instance; can also create, change, archive and delete work items, add, edit or delete internal comments, log and correct time, create cycles, modules, labels, states and projects, put work items into cycles and modules, add links and relations, and change who is subscribed, when you ask.

Reads

• plane_list_projectsProjects in the Plane workspace: id (needed by every other Plane tool), identifier (the prefix of work-item keys such as WEB-12)…
• plane_list_work_itemsWork items in one Plane project, in Plane's default order: key (WEB-12), name, state, priority, assignees, labels, start and target dates…
• plane_search_work_itemsSearch Plane work items by words in the name, by sequence number or by key (WEB-12), across the workspace or within one project.
• plane_list_commentsComments on one Plane work item, oldest first as Plane returns them: text (HTML reduced to plain text and cut short), whether internal or external…
• plane_list_statesThe workflow states of one Plane project (Backlog, Todo, In Progress, Done…) with their ids and groups.
• plane_list_membersPeople in the Plane workspace with their user ids and role, for assigning a work item or naming who is on what.
• plane_list_cyclesCycles (sprints) in one Plane project: id, name, start and end dates, status and work-item counts.
• plane_list_modulesModules in one Plane project: id, name, status, start and target dates and work-item counts.
• plane_list_labelsLabels in one Plane project with their ids, colours and parent label.

Acts, when you ask

These change something in Plane. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• plane_create_work_itemCreate a work item in a Plane project.
• plane_add_commentAdd an internal comment to a Plane work item.
• plane_log_timeLog time spent on a Plane work item, as the connection's own user.
• plane_update_work_itemChange fields of an existing Plane work item: name, description, state, priority, assignees, start or target date.
• plane_delete_work_itemDELETE a Plane work item, with its comments, worklogs and attachments.
• plane_delete_commentDELETE one comment from a Plane work item.
• plane_archive_work_itemArchive a Plane work item: it leaves the active lists and boards but is kept, with its comments and history…
• plane_unarchive_work_itemRestore an archived Plane work item to the active lists.
• plane_update_commentReplace the text of an existing comment on a Plane work item (plane_list_comments shows the ids).
• plane_create_cycleCreate a cycle (sprint) in a Plane project, owned by the connection's user.
• plane_add_work_items_to_cycleAdd work items to a Plane cycle (a work item belongs to one cycle at a time, so one already in another cycle moves).
• plane_remove_work_item_from_cycleTake one work item out of a Plane cycle; the work item itself is kept in the project.
• plane_archive_cycleArchive a Plane cycle that has ended, hiding it from the active cycle lists while keeping it for reference (it can be restored in Plane).
• plane_create_moduleCreate a module in a Plane project, optionally with a lead and members (user ids from plane_list_members, only people the user named…
• plane_add_work_items_to_moduleAdd work items to a Plane module (an item can be in several modules).
• plane_remove_work_item_from_moduleTake one work item out of a Plane module; the work item itself is kept.
• plane_create_labelCreate a label in a Plane project, optionally nested under a parent label.
• plane_create_stateAdd a workflow state to a Plane project (e.g. "In review" in the started group).
• plane_add_work_item_linkAttach a web link (https URL, with an optional title) to a Plane work item.
• plane_add_work_item_relationRelate one Plane work item to others: blocking, blocked_by, duplicate, relates_to, or a scheduling dependency (start_before, start_after…
• plane_update_worklogCorrect a time log on a Plane work item: its minutes or its description (each given value replaces the old one).
• plane_create_projectCreate a project in the Plane workspace, created by the connection's user.
• plane_update_work_item_subscribersSubscribe people to a Plane work item, or unsubscribe them (user ids from plane_list_members).

Connect it

First connect Plane on Dashboard → Connections, then add Memtro to your client once. The Plane tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Plane connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › What is in progress in the Website project right now?
• › Which urgent work items are assigned to Priya Sharma?
• › What was said in the comments on WEB-42?
• › Create a work item in Website called Fix the pricing page footer and add it to the current cycle
• › Move WEB-17 to Done and set its target date to Friday

Questions

Is this an official Plane MCP server?

No. It is Memtro's MCP server with Memtro's Plane connector behind it: the connector reads Plane through its API with the credentials you connect on Dashboard → Connections, and Plane publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Plane?

Only when you ask, and only what it has been granted: create a work item in a Plane project; add an internal comment to a work item; log time spent on a work item; change a work item's name, description, state, priority, assignees or dates; delete a work item; delete a comment on a work item; archive or restore a work item; edit the text of a comment; create a cycle; add work items to a cycle or take one out; archive a cycle that has ended; create a module; add work items to a module or take one out; create a label; add a workflow state to a project; attach a link to a work item; relate, block or mark a work item as a duplicate of others; correct a time log; create a project; subscribe or unsubscribe people from a work item. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Work management

• Clio Manage MCP server
• Linear MCP server
• Jira MCP server
• Asana MCP server
• monday.com MCP server
• Airtable MCP server