Can I use Plane as a CLI?

Yes. KosmoKrator exposes a Plane CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Plane through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Plane tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Plane credentials stored?

Plane credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Plane MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Plane MCP Integration for Claude Code

Connect Plane to Claude Code through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

33 functions 19 read 14 write API key auth

Submit Plane feedback View package source

Connect Plane to Claude Code

Connect local KosmoKrator integrations to Claude Code through one scoped MCP gateway entry.

Add KosmoKrator as a stdio MCP server in the Claude Code project config and select the integrations that should be visible. The gateway is local, scoped to this integration, and starts with --write=deny so Claude Code can inspect read-capable tools without receiving write access by default.

Plane MCP Config for Claude Code

Claude Code can launch the local kosmo binary directly from the project MCP config.

{
  "mcpServers": {
    "kosmokrator-plane": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=plane",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=plane --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Plane instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Plane Tools Visible to Claude Code

Claude Code sees stable MCP tool names generated from the Plane integration catalog.

MCP tool	Source function	Type	Description
`integration__plane__plane_list_workspaces`	`plane.plane_list_workspaces`	Read	List all Plane.so workspaces the authenticated user belongs to. Returns workspace slug, name, and owner info. Use the slug to reference workspaces in other tools.
`integration__plane__plane_list_projects`	`plane.plane_list_projects`	Read	List all projects in a Plane.so workspace. Returns project ID, name, identifier, description, and status. Use the project ID to reference projects in other tools.
`integration__plane__plane_get_project`	`plane.plane_get_project`	Read	Get detailed information about a Plane.so project, including name, identifier, description, status, dates, and settings.
`integration__plane__plane_create_project`	`plane.plane_create_project`	Write	Create a new project in a Plane.so workspace. Requires a name and identifier (short code, e.g., "PROJ"). Optionally set description, cover image, project lead, and default assignee.
`integration__plane__plane_archive_project`	`plane.plane_archive_project`	Write	Archive a Plane.so project. Archived projects are hidden from active views but retain all data.
`integration__plane__plane_list_issues`	`plane.plane_list_issues`	Read	List issues in a Plane.so project. Supports filtering by state, priority, assignee, labels, and more. Returns issue ID, name, sequence ID, state, priority, assignees, labels, start/target dates, and created date.
`integration__plane__plane_search_issues`	`plane.plane_search_issues`	Read	Search issues across all projects in a Plane.so workspace. Provide a search query to find issues by name or description. Optionally filter by project, state, priority, or assignee.
`integration__plane__plane_get_issue`	`plane.plane_get_issue`	Read	Get detailed information about a single Plane.so issue, including description, state, priority, assignees, labels, dates, and relations. The issue_id may be a UUID or an issue reference like KOS-55 on Plane deployments that support it.
`integration__plane__plane_create_issue`	`plane.plane_create_issue`	Write	Create a new issue in a Plane.so project. Requires a title. Optionally set description (HTML), state, priority, assignees, labels, start/target dates, and parent issue.
`integration__plane__plane_update_issue`	`plane.plane_update_issue`	Write	Update an existing Plane.so issue. Provide only the fields you want to change — name, description, state, priority, assignees, labels, dates, or parent.
`integration__plane__plane_delete_issue`	`plane.plane_delete_issue`	Write	Delete an issue from a Plane.so project. This action is permanent and cannot be undone.
`integration__plane__plane_create_comment`	`plane.plane_create_comment`	Write	Add a comment to a Plane.so issue. The comment body should be provided in HTML format.
`integration__plane__plane_list_comments`	`plane.plane_list_comments`	Read	List all comments on a Plane.so issue. Returns comment ID, content, author, and timestamps.
`integration__plane__plane_list_cycles`	`plane.plane_list_cycles`	Read	List all cycles in a Plane.so project. Returns cycle ID, name, start/end dates, and progress info.
`integration__plane__plane_get_cycle`	`plane.plane_get_cycle`	Read	Get detailed information about a Plane.so cycle, including name, description, start/end dates, and status.
`integration__plane__plane_create_cycle`	`plane.plane_create_cycle`	Write	Create a new cycle (sprint) in a Plane.so project. Optionally set name, description, and date range.
`integration__plane__plane_add_issue_to_cycle`	`plane.plane_add_issue_to_cycle`	Write	Add an existing issue to a Plane.so cycle. The issue will be tracked within the cycle's sprint/iteration.
`integration__plane__plane_list_modules`	`plane.plane_list_modules`	Read	List all modules in a Plane.so project. Modules group related issues together (e.g., "Auth System", "Payment Integration"). Returns module ID, name, description, status, and dates.
`integration__plane__plane_get_module`	`plane.plane_get_module`	Read	Get detailed information about a Plane.so module, including name, description, status, dates, and team.
`integration__plane__plane_create_module`	`plane.plane_create_module`	Write	Create a new module in a Plane.so project. Modules group related issues together (e.g., "Auth System", "Payment Integration"). Optionally set description, status, and date range.
`integration__plane__plane_add_issue_to_module`	`plane.plane_add_issue_to_module`	Write	Add an existing issue to a Plane.so module. Modules group related issues for feature-based organization.
`integration__plane__plane_list_states`	`plane.plane_list_states`	Read	List all workflow states in a Plane.so project. Returns state UUID, name, group (backlog/unstarted/started/completed/cancelled), and color. Use state UUIDs when creating or updating issues.
`integration__plane__plane_create_state`	`plane.plane_create_state`	Write	Create a new workflow state in a Plane.so project. States represent issue statuses (e.g., "In Review", "Ready for QA"). Requires a name and group (backlog, unstarted, started, completed, cancelled). Optionally set color and description.
`integration__plane__plane_list_labels`	`plane.plane_list_labels`	Read	List all labels in a Plane.so project. Returns label UUID, name, color, and parent label. Use label UUIDs when creating or updating issues.
`integration__plane__plane_create_label`	`plane.plane_create_label`	Write	Create a new label in a Plane.so project. Labels categorize issues (e.g., "bug", "feature", "urgent"). Requires a name. Optionally set color (hex) and description. Supports hierarchical labels via parent UUID.
`integration__plane__plane_list_pages`	`plane.plane_list_pages`	Read	List all pages in a Plane.so project. Pages are Notion-like documents for notes, specs, and documentation. Returns page ID, name, description, and ownership info.
`integration__plane__plane_get_page`	`plane.plane_get_page`	Read	Get detailed content of a Plane.so page, including the full HTML description.
`integration__plane__plane_create_page`	`plane.plane_create_page`	Write	Create a new page in a Plane.so project. Pages are Notion-like documents for notes, specs, and documentation. Requires a name. Optionally set HTML content.
`integration__plane__plane_list_issue_activities`	`plane.plane_list_issue_activities`	Read	List activity/audit events on a Plane.so issue. Returns changes made to the issue (state changes, assignments, updates, comments) with who made them and when.
`integration__plane__plane_create_issue_link`	`plane.plane_create_issue_link`	Write	Attach an external link to a Plane.so issue. Provide a title and a valid URL.

Showing 30 of 33 functions. See the Plane MCP reference for the full list.

Related Plane Pages

Plane CLIUse direct JSON commands instead of MCP discovery. Plane MCPFull gateway reference and MCP tool names. KosmoKrator for Claude CodeClient-level gateway setup.