Connect Plane to Claude Code

Read and manage Plane projects, work items, cycles, states, labels and comments. Add Toolspoke to Claude Code once and it can use 17 Plane actions. Your Plane credential stays in Toolspoke, and you choose which actions Claude Code may call.

Set it up in Claude Code

Three steps, the first one once for every toolkit you will ever add.

  1. Add Toolspoke to Claude Code

    Run it in your project, then /mcp to sign in

    claude mcp add --transport http toolspoke https://toolspoke.com/mcp

    The sign-in opens in your browser, and Toolspoke asks you to approve it.

  2. Install Plane and connect it

    Add Plane to a project in your Toolspoke workspace.

    API key. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

    Personal access token
    Plane → Profile settings → Personal access tokens → Add personal access token. The token acts as you, so it reaches only the projects you are a member of.
    Workspace slug
    The first path segment of your Plane URL. In https://app.plane.so/my-team/projects/ the slug is my-team.
  3. Choose what Claude Code may do

    All 17 actions start on. Switch off any of the 5 actions that change something in Plane, and Claude Code gets a refusal if it tries.

What you can ask Claude Code for

A few of the Plane actions that only read, so they are safe to try first.

  • List the projects in the workspace that you are a member of
  • Read one project by id, including its identifier (the ENG in ENG-42)
  • List the work items in a project
  • Read one work item by its UUID

What Claude Code can do in Plane

12 actions read, 4 write and one deletes or permanently changes something.

Reads

  • List projects

    List the projects in the workspace that you are a member of. Proves the token, the workspace slug and the instance URL together, which is why an install tests itself with it.

  • Get project

    Read one project by id, including its identifier (the ENG in ENG-42).

  • List work items

    List the work items in a project. Use expand=assignees,labels,state to get names rather than ids.

  • Get work item

    Read one work item by its UUID.

  • Get work item by identifier

    Read one work item by the identifier people use, e.g. ENG-42. No project id needed.

  • Search work items

    Search work items across the workspace by text, optionally within one project.

  • List states

    List a project's workflow states (Backlog, Todo, In Progress, Done, Cancelled and any custom ones) with the UUIDs work items take.

  • List labels

    List a project's labels with the UUIDs work items take.

  • List cycles

    List a project's cycles (sprints), optionally filtered by status.

  • List cycle work items

    List the work items in one cycle.

  • List comments

    List the comments on a work item. Comments are other people's words, so the response is not written to the audit log.

  • List workspace members

    List the workspace's members with the UUIDs that assignees take.

Writes

  • Create work item

    Create a work item in a project. Only name is required. state, labels and assignees take UUIDs from list_states, list_labels and list_workspace_members.

  • Update work item

    Change a work item. Only the fields sent change; assignees and labels replace the current set.

  • Add work items to cycle

    Add work items to a cycle.

  • Add comment

    Add a comment to a work item, as HTML, e.g. <p>Fixed in

Deletes or permanently changes

  • Delete work item

    Delete a work item. To close one, move it to a completed or cancelled state with update_work_item instead.

Plane in Claude Code: questions

Does Claude Code see my Plane credential?

No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.

Can I stop Claude Code from changing things in Plane?

Yes. Each of the 17 actions can be switched off for a project. Turn off the 5 that change something and Claude Code can only read.

Will 17 actions crowd Claude Code's context?

No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the Plane action it needs when it needs it. Adding more toolkits does not add more tools to its list.

Can I add it once for every project?

Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.

What does it cost?

Tool calls are free on every plan, and a Plane call does not run in a sandbox, so it bills nothing.

Try Plane in Claude Code

Free to start, and tool calls cost nothing on any plan.