Skip to main content
Glama
JonatanCosta

plane-local-mcp

by JonatanCosta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PLANE_API_KEYYesAPI key do Plane
PLANE_BASE_URLYesURL base da instância (sem /api)
PLANE_WORKSPACE_SLUGYesSlug do workspace

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_instance_infoA

Retorna a configuração do Plane conectado (base_url, workspace, edition assumida).

list_projectsB

Lista projetos do workspace configurado.

retrieve_projectC

Recupera um projeto pelo UUID.

list_statesC

Lista estados (colunas) de um projeto.

list_labelsB

Lista labels de um projeto.

list_modulesB

Lista modules de um projeto.

list_cyclesC

Lista cycles de um projeto.

list_issuesC

Lista issues de um projeto (API /issues/).

retrieve_issueA

Recupera uma issue pelo UUID do projeto e da issue.

get_issue_by_identifierA

Recupera uma issue pelo identificador humano (ex.: CKTPC-838).

list_issue_childrenC

Lista filhos de uma issue/épico pelo identificador (ex.: CKTPC-838).

update_issueA

Edita título, descrição, prioridade e/ou status de uma issue (ex.: CKTPC-844).

  • description: texto simples (convertido para HTML).

  • description_html: HTML do editor do Plane (tem precedência sobre description).

  • state_id ou state_name: move a issue de status (use list_states para descobrir).

  • priority: urgent|high|medium|low|none.

add_issue_to_cycleA

Adiciona uma issue a um cycle. Informe cycle_id ou cycle_name (ex.: Payment Sprint - 23).

remove_issue_from_cycleC

Remove uma issue de um cycle. Informe cycle_id ou cycle_name.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.3/5.0

Scored across 14 tools

Disambiguation4/5

Each tool targets a distinct resource or action, but the pair retrieve_issue and get_issue_by_identifier both retrieve a single issue, differing only by lookup key. This minor overlap is clarified by descriptions, so most tools are unambiguous.

Naming Consistency4/5

Names follow a verb_noun pattern with snake_case throughout, but verbs are inconsistent (list, get, retrieve, update, add, remove). This is readable but not as uniform as using the same verb for the same operation.

Tool Count5/5

With 14 tools, the server covers issues, cycles, states, labels, modules, and projects without feeling bloated. This is well-scoped for a project management integration.

Completeness3/5

The surface has strong read and update coverage for issues and cycles, but notably lacks a create_issue tool or any deletion capability. Agents cannot create new issues, so the lifecycle is incomplete.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources