canonical: https://jentic.com/apis/plane.so/plane

# Plane So Plane API

The Plane API manages projects and work items for teams using the open-source project management tool. It creates and updates projects, work items, cycles, modules, labels, and workflow states within a workspace. Plane is positioned as a Jira and Linear alternative, giving agents programmatic control over an issue tracker that teams can self-host.

## For AI agents

Create and update projects, work items, cycles, modules, labels, and workflow states in a Plane workspace. Programmatic access to an open-source Jira and Linear alternative.

## Scope

Does not handle source code hosting, CI/CD, or time tracking. Use for project and work item management only.

## Capabilities

- Create projects and work items in a workspace
- Move work items through project workflow states
- Group work into cycles and modules
- Label and categorize work items
- List workspace members and project states
- Update work item fields on an existing item

## Use cases

### AI Project Management Agent

An AI agent connected to Plane through Jentic can file work items from incoming requests, assign them to a cycle, and move them through workflow states as work progresses. Because Plane is open-source and self-hostable, teams keep their project data on their own infrastructure while the agent drives the board.

Example prompt: Create a work item in a project, add it to the current cycle, and set its workflow state to in-progress

### Issue Tracking

Track issues as work items that move through a project's workflow states. The Plane API creates work items, updates their fields, and applies labels so a backlog stays organized and queryable.

Example prompt: Create a work item, apply a bug label, and move it to the triage state

### Cycle and Module Planning

Plan work into cycles and modules to organize sprints and feature groupings. Plane lets an agent create cycles and modules in a project and list the states work items can occupy.

Example prompt: Create a new cycle for a project and list its workflow states

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/workspaces/{workspace_slug}/projects` | List projects in a workspace |
| POST | `/workspaces/{workspace_slug}/projects` | Create a project |
| GET | `/workspaces/{workspace_slug}/projects/{project_id}/work-items` | List work items in a project |
| POST | `/workspaces/{workspace_slug}/projects/{project_id}/work-items` | Create a work item |
| PATCH | `/workspaces/{workspace_slug}/projects/{project_id}/work-items/{work_item_id}` | Update a work item |
| POST | `/workspaces/{workspace_slug}/projects/{project_id}/cycles` | Create a cycle |

## Key resources

- **Projects** — Projects within a workspace, created and updated via the API
- **Work Items** — Issues tracked through workflow states, with labels and fields
- **Cycles and Modules** — Sprint-style cycles and feature modules in a project
- **States and Members** — Workflow states and workspace member listings

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 61 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 59 / 100
  - AI-Readiness & Agent Experience: 44 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/plane.so/plane/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Plane by hand means sending its API key in a custom header and learning the workspace, project, and work-item path structure yourself. Through Jentic you install once, import Plane from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Plane puts the project id in the URL path, so a rule can pin your agent to one project: it can create and update work items there and nothing else. You choose the operations it may call, so project deletion is not included unless you add it.
- **Credential handling:** Your Plane API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a work item' or 'list projects', and Jentic returns the matching Plane operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Linear** — Fast hosted issue tracker, where Plane is an open-source self-hostable alternative.
- **Jira** — Established enterprise issue tracker, where Plane offers a lighter open-source alternative.
- **Notion** — Docs and wiki workspace, complementing Plane's project and work-item tracking.

## FAQ

### Is there a Plane MCP server?

You don't need an MCP server to give your agent the Plane API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent can create and update work items. Operations are discovered on demand, so your agent's context stays lean.

### Can I limit what my agent is allowed to do with the Plane API?

Yes. Plane puts the project id in the URL path, so a rule can pin your agent to one project and allow only work-item creation and updates there. The agent cannot delete the project or touch other projects unless you add those operations, and every call is logged.

### What authentication does the Plane API use?

The Plane API authenticates with an API key sent in the X-API-Key header per its OpenAPI spec; you generate the key from Personal Access Tokens in your profile settings. With Jentic, the key is stored encrypted by your own Jentic One instance and injected at call time.

### Can I create a work item with the Plane API?

Yes. The work-items endpoint creates an item in a project, and a related endpoint updates its fields and state. You can also add the item to a cycle or module and apply labels to categorize it.

### What are the rate limits for the Plane API?

The OpenAPI spec does not specify rate limits. Check the Plane developer documentation at https://developers.plane.so for current limits before running bulk work-item operations.

### How do I create a work item with the Plane API through Jentic?

Import the Plane API from the Jentic API Directory, store your API key once, and have your agent search by intent such as 'create a work item'. Jentic returns the create operation with its input schema, and your agent passes the workspace and project. To run it on your own infrastructure, install Jentic One from its GitHub repo.