Plane
This profile reflects information published by the agent provider.
Card passedProtocol probe not applicableUnsigned card
About this agent
LocalMark's observation
LocalMark first listed this public Agent Card on 10 Oct 2026, 13:00 UTC. Its latest card check succeeded; the card declares 41 skills and a MCP+HTTP interface. LocalMark has not run a task against this agent.
What LocalMark checked
- Published Agent Card
Inspect the source card ↗. The last successful fetch was 10 Oct 2026, 13:00 UTC.
- Latest card check: passed
10 Oct 2026, 13:00 UTC · Agent Card validated
- Advertised endpoint: TLS connection not yet checked
Not yet checked · A future cycle will check TLS connectivity. This does not test the A2A protocol or run a task.
- Read-only protocol probe: Protocol probe not applicable
10 Oct 2026, 13:00 UTC · Read-only probe currently supports JSON-RPC, not MCP+HTTP LocalMark sent no message and did not request task creation.
- Unsigned card
This card does not provide a digital signature. Checked 10 Oct 2026, 13:00 UTC.
- 30-day card check history
1 of 1 recorded card checks passed in the last 30 days. These are periodic observations, not continuous uptime monitoring.
- Publisher claim
No publisher claim has been completed for this listing.
Card availability and a valid signature do not prove provider identity, task performance, or safety. LocalMark has not executed a task against this agent.
Recent card checks
Periodic observations over the last 30 days; they are not continuous uptime monitoring.
Show 1 recent check
- Passed · 10 Oct 2026, 13:00 UTC
Agent Card validated
Card and signature changes
- No changes recorded since change tracking began.
Share this listing
Link to this profile with a status badge that updates from LocalMark checks.
README Markdown:
[](https://localmark.ai/agents/11427)Card-declared connections
These links come from statements in public Agent Cards. They do not verify common ownership or cooperation.
- No card-declared connections recorded yet.
Declared skills 41
- Attach a file to a work item
Upload a file to a work item. Request presigned upload credentials, POST the file to the returned URL, then confirm the upload. Over MCP the `upload_from_url` action does all three in one call.
- Attach an external link to a work item
Add a titled external URL to a work item — a pull request, a dashboard, a design file — and read back the links already on it.
- Comment on a work item
Post, edit, or read comments on a work item so an agent can report progress where the work lives.
- Count and group work items
Aggregate work item counts across a workspace or project, grouped and sub-grouped by state, priority, assignee, label, type, cycle, module, milestone, release, creator, or date. This is the reporting primitive: Plane's Dashboards and Analytics views themselves have no public API, so an agent answers "how many, broken down by what" with this.
- Create a project
Set up a project with a name, short identifier, lead, timezone, and the feature modules it should use.
- Create a work item
Open a new work item in a project with a name, description, priority, state, assignees, labels, and dates.
- Fill a module
Add work items to a module and list what it already contains.
- Fill and close out a cycle
Add work items to a cycle, list what is in it, transfer unfinished work to the next cycle, and complete or archive it — the rest of the sprint loop beyond creating the cycle.
- Find a work item by its readable identifier
Retrieve a work item from the identifier people actually use, such as ENG-42, without first resolving a UUID. This is the only work item action that accepts a readable identifier — every other action takes the work item's UUID.
- Identify the current user
Resolve who the credential authenticates as, including whether it is a bot. Call this to attribute work and to interpret `@me` in a PQL filter.
- List labels
Read a project's labels. Call this to turn label names into the ids that creating and updating work items requires.
- List projects
Enumerate the projects in a workspace with their ids, identifiers, and enabled features.
- List teamspaces
Read the teamspaces in a workspace with their members and projects, to scope work to the right team.
- List work items in a project
Page through the work items in one project, optionally filtered with PQL and narrowed to a sparse field set.
- List workflow states
Read a project's workflow states and their groups. Call this to turn a state name such as "In Progress" into the id that creating and updating work items requires.
- Log customer requests
Record what a customer asked for and link the work items that deliver it, so commitments are traceable back to the account.
- Log time against a work item
Record a work log with a duration in minutes, and read back the logs on a work item.
- Manage customers and requests
Create customer records, log their requests, and link the work items that deliver against them.
- Manage epics
Create epics and attach the work items that roll up into them. Plane models an epic as a work item whose type is named Epic, so over MCP there is no epic tool: resolve the Epic type with `workitem_type resolve`, pass the returned id as `type_id` to `workitem create`, then list epics with `pql='type = "<type id>"'` and an epic's children with `pql='childOf("ENG-12")'`. REST has dedicated epic paths that do this for you.
- Manage estimates
Create a project's estimation system and read its points, so the `estimate_point` id required when sizing a work item can be resolved.
- Manage releases and changelogs
Create releases, attach the work items shipping in them, manage release tags and labels, and generate or edit the changelog.
- Manage work item types
List and create the work item types in a project — Bug, Story, Epic and any custom type — each with its own icon and custom properties. Prefer the MCP `resolve` action over `create`: it finds an existing type or creates one without duplicating, which is also the only way to get a usable type in a workspace that centrally governs its type vocabulary and refuses project-scoped writes. `import_to_project` links existing workspace types to a project.
- Map identity provider groups to roles
List and create mappings from identity provider groups to Plane roles, at workspace or project scope. This is the one integration-shaped API Plane exposes — the native integrations (GitHub, GitLab, Slack, Sentry, Bitbucket) are configured in workspace settings and have no public endpoints.
- Plan a cycle
Create a time-boxed cycle, list what is in it, and move work items in or out — the sprint-planning loop.
- Plan a milestone
Create dated checkpoints in a project and attach the work items that must land by each one.
- Plan a module
Group related work into a module with a lead, members, dates, and a delivery status.
- Read a work item's history
Page through the change history of a work item — state moves, reassignments, field edits — to summarise what happened and when.
- Read and toggle project features
Read or change which feature modules a project has enabled — epics, modules, cycles, views, pages, intake, work item types. Check this before calling a capability that depends on a module being on.
- Read and toggle workspace features
Read or change which workspace-level features are enabled — initiatives, teamspaces, customers, wiki, project grouping, and Plane AI.
- Read and write custom property values
Set or read the value of a work item's custom properties, so an agent can populate the fields a team actually tracks rather than only the built-in ones.
- Read and write wiki pages
List and create pages at workspace (wiki) or project scope, so an agent can file specs and notes next to the work.
- Relate work items
Create a typed relation between two work items — blocking, blocked by, duplicate, relates to, or a custom workspace relation type — so dependencies are explicit.
- Report progress as a Plane agent
For agents installed as Plane apps: post thoughts, actions, responses, elicitations, and errors into the Agent Run created when a user @mentions the agent on a work item. Thoughts and actions are ephemeral; a response becomes a visible comment.
- Resolve workspace members
Look up workspace and project members and their roles, so names in a prompt can be turned into the ids other capabilities require.
- Retrieve the query language reference
Fetch the Plane Query Language syntax reference — operators, functions, fields, and worked examples. Call this before composing a `pql` filter for any capability that accepts one.
- Search work items
Find work items across a workspace by free-text query or a Plane Query Language (PQL) filter, without knowing project ids up front.
- Submit and resolve an intake request
File a request into a project intake queue, then accept, reject, snooze, or mark it duplicate. Pairs with reading the queue.
- Summarise logged time
Total the time logged against every work item in a project, for timesheet and capacity reporting. Pairs with logging time on an individual work item.
- Track an initiative
Create and update workspace initiatives, and attach the projects and epics that roll up into them.
- Triage the intake queue
Read the intake queue for a project and accept, reject, or convert submitted requests into work items.
- Update a work item
Change any subset of a work item — state, priority, dates, description, assignees, labels. Only the fields passed are modified.