Provider REST API

17 actions

Connect Claude to Plane

Read and manage Plane projects, work items, cycles, states, labels and comments. Toolspoke puts 17 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connect View pricing

Connection: Provider REST API
Authentication: API key
Actions exposed: 17
What a call bills: Nothing
Adapter: Maintained by Toolspoke

Connected in three steps

1
Install Plane
Open the marketplace in your workspace, add Plane to the project your agents work in, and it appears on the gateway immediately.
2
Connect the credential
Authenticate with api key. Where to get one, and what it has to be able to reach, is the next section.
3
Point your agent at the gateway
Give your client one address, https://toolspoke.com/mcp. Claude Code takes it as a command, Claude and Claude Desktop add it as a custom connector, and Cursor, Codex and VS Code each read it from a config file of their own.

.mcp.json

{
  "mcpServers": {
    "toolspoke": {
      "type": "http",
      "url": "https://toolspoke.com/mcp"
    }
  }
}

One block covers every tool you have installed. Plane shows up in the client as soon as your policy allows it, and so does everything else you install later.

Where the address goes, per client

Claude Code: Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcp
Claude and Claude Desktop: Settings, then Connectors, then Add custom connector
https://toolspoke.com/mcp
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json for one project
{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }
Codex: ~/.codex/config.toml
[mcp_servers.toolspoke] url = "https://toolspoke.com/mcp"
VS Code: .vscode/mcp.json, or the MCP: Add Server command
{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }

What Plane asks for

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 tokenRequired: 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.; plane_api_…
Workspace slugRequired: The first path segment of your Plane URL. In https://app.plane.so/my-team/projects/ the slug is my-team.; my-team
Plane URLOptional: Leave blank for Plane Cloud. For a self-hosted instance, its root URL without /api/v1. It has to be publicly reachable.; https://plane.example.com

What Claude can do in Plane

17 actions, each one declared and named by the connector rather than discovered at runtime. A workspace policy grants a person all of them, a hand-picked selection, everything on the read side, everything on the write side, or none.

Reads: 12Reads
Writes: 4Writes
Destructive: 1Destructive

Reads

Fetches data and changes nothing.

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

Creates or updates something on the other side.

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

Destructive

Deletes or permanently alters something. Worth granting on purpose.

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

What it will not do

Enforced by the gateway rather than left to convention, which is why each of these can be stated flatly.

It cannot call anything else: The 17 actions above are the whole of it. A call to any other name is refused before it reaches Plane rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time.
It reaches no further than your credential: Toolspoke holds no access to Plane of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either.
It never hears from Plane: Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Plane. An agent has to ask.
It does not smooth over provider limits: Toolspoke does not retry, queue or back off around Plane's own rate limits. A call that Plane refuses comes back to the agent as a failed call.

Before you connect it

What can Claude do in Plane?

17 named actions: 12 that only read, 4 that write and 1 that delete or permanently alter something. They include list_projects, get_project and list_work_items. Nothing outside that list is reachable: the connector declares each operation by name rather than proxying whatever an agent asks for.

What credentials does the Plane connector need?

API key. The connector asks for personal access token and workspace slug, and optionally plane url. Values are encrypted at rest and attached to the outbound request by the gateway, so they are never part of the arguments an agent sends and never reach the audit log.

Does the Plane connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 17 actions. There is a single address, https://toolspoke.com/mcp. Claude Code adds it with claude mcp add --transport http, Claude and Claude Desktop take it as a custom connector in settings, Cursor reads it from .cursor/mcp.json, Codex from ~/.codex/config.toml, and VS Code from .vscode/mcp.json. Each of them signs in to the gateway itself, so there is no key to paste.

What does the Plane connector not do?

The 17 actions above are the whole of it. A call to any other name is refused before it reaches Plane rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time. Toolspoke holds no access to Plane of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either. Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Plane. An agent has to ask. Toolspoke does not retry, queue or back off around Plane's own rate limits. A call that Plane refuses comes back to the agent as a failed call.

Can I limit which actions an agent can call?

Yes, in two places. The project switches Plane's actions on and off one at a time, for everyone in the project at once, and the screen groups them by read, write and destructive so turning off everything that deletes is one click. An individual agent key can then be narrowed further, to particular toolkits in a project and to particular actions in a toolkit. Whatever it was granted, a key never reaches a project its owner cannot.

What gets recorded when an agent calls Plane?

Every attempt, with the agent that made it and the person that agent belongs to, the full request payload, the response payload, the status, the duration, and what the call cost in sandbox time and model tokens. Values whose key names a secret are masked out before the record is shown to anyone. An operation the connector marks as not retained never has its response body written at all, so the gateway keeps no second copy of what was read.

More project management connectors

Browse all of them