Planka V2

Created By

goldpulpy7 days ago

Connect Claude, Cursor, Codex, and other MCP clients directly to your Planka v2.x boards.

# planka

# kanban

Overview Content Tools Comments

Overview

Planka v2.x MCP

Connect Claude, Cursor, Codex, and other MCP clients directly to your Planka v2.x boards.

Give your AI agents structured, secure access to projects, boards, cards, tasks, comments, labels, and workflows through the Model Context Protocol (MCP).

IMPORTANT

Built specifically for Planka v2.x. This MCP is not compatible with Planka v1.x.

Why Planka MCP?

Planka provides an excellent web interface for human users. AI agents, however, need structured access to projects, boards, cards, tasks, comments, and workflows.

This MCP server exposes the Planka v2 API through the Model Context Protocol (MCP), allowing Claude, Cursor, Codex, and other AI agents to interact with Planka using natural language.

Supported Planka Versions

Planka Version	Status
2.0.0-rc.2	✅ Tested
2.1.1	✅ Tested
Newer 2.x	⚠️ Expected to work

Features

Full project and board management
Complete card lifecycle management
Task Lists and tasks support
Comments, labels, and assignments
Card time tracking
Project and board summaries
MCP-native tool interface
Support for major MCP clients
Self-hosted and cloud Planka support

Example Conversations

Project Setup

User

Create a project called "Website Redesign" with boards "Backlog", "In Progress", and "Done".

Assistant

✓ Created project "Website Redesign"
✓ Created board "Backlog"
✓ Created board "In Progress"
✓ Created board "Done"

Project setup completed successfully.

Task Creation

User

Create a card "Implement authentication" in the Backlog board with tasks:

Design login flow

Implement JWT authentication

Add password reset

Write tests

Assistant

✓ Created card "Implement authentication"
✓ Created task list
✓ Added 4 tasks

Workflow Automation

User

Find all overdue cards assigned to me, move them to "Blocked", add a comment explaining why, and generate a project summary.

Assistant

✓ Found 7 overdue cards
✓ Moved cards to "Blocked"
✓ Added explanatory comments
✓ Generated updated project summary

Available Tools

Tool Name	Actions	Description
`project_board_manager`	`get_projects` · `create_project` · `get_project` · `update_project` · `delete_project` · `get_boards` · `create_board` · `get_board` · `update_board` · `delete_board` · `get_board_summary` · `get_project_summary`	Projects and boards, including aggregate summaries
`list_manager`	`get_all` · `create` · `get_one` · `update` · `delete`	Kanban lists within a board
`card_manager`	`get_all` · `create` · `get_one` · `update` · `move` · `duplicate` · `delete` · `create_with_tasks` · `get_details`	Cards, including one-shot creation with a task checklist
`stopwatch`	`start` · `stop` · `get` · `reset`	Time tracking on a card
`label_manager`	`get_all` · `create` · `update` · `delete` · `add_to_card` · `remove_from_card`	Board labels and their assignment to cards
`task_list_manager`	`get_all` · `create` · `get_one` · `update` · `delete`	Task Lists inside a card (Planka v2.0 entity)
`task_manager`	`get_all` · `create` · `batch_create` · `get_one` · `update` · `delete` · `complete_task`	Individual tasks, including bulk creation
`comment_manager`	`get_all` · `create` · `get_one` · `update` · `delete`	Comments on a card
`membership_manager`	`get_all` · `create` · `get_one` · `update` · `delete`	Board-level membership and roles (`editor` / `viewer`)
`card_membership_manager`	`get_all` · `get_users` · `create` · `delete`	Assign/remove card members by ID, email, or username

Configure Your MCP Client

Every MCP-compatible client uses the same underlying command - only the config file location (and occasionally the JSON wrapper) differs. See Client Configuration Examples below for your specific tool.

The core config block is always:

{
  "command": "npx",
  "args": ["-y", "@goldpulpy/planka-v2-mcp@latest"],
  "env": {
    "PLANKA_BASE_URL": "https://your-planka-instance.com",
    "PLANKA_AGENT_EMAIL": "agent@yourdomain.com",
    "PLANKA_AGENT_PASSWORD": "your-secure-password",
    "PLANKA_IGNORE_SSL": "true"
  }
}

TIP

Set PLANKA_IGNORE_SSL to "true" only for self-signed certs in trusted/local environments - leave it unset in production.

Verify the Connection

Ask your agent something read-only first, e.g. "List my Planka projects." If you get a real response back, you're wired up correctly.

Client Configuration Examples

Most MCP clients share the exact same mcpServers JSON shape - only the config file location differs. Clients with a different format (Codex, Continue, Zed) get their own block below.

Standard mcpServers clients - Claude Desktop, Claude Code, Cursor, Windsurf, Cline, Antigravity

{
  "mcpServers": {
    "planka-mcp": {
      "command": "npx",
      "args": ["-y", "@goldpulpy/planka-v2-mcp@latest"],
      "env": {
        "PLANKA_BASE_URL": "https://your-planka-instance.com",
        "PLANKA_AGENT_EMAIL": "agent@yourdomain.com",
        "PLANKA_AGENT_PASSWORD": "your-secure-password",
        "PLANKA_IGNORE_SSL": "true"
      }
    }
  }
}

Drop this block into the relevant config file:

Client	Config file
Claude Desktop	macOS: `~/Library/Application Support/Claude/claude_desktop_config.json` · Windows: `%APPDATA%\Claude\claude_desktop_config.json`
Claude Code (CLI)	`.mcp.json` in your project root (or `claude mcp add`, see below)
Cursor	`~/.cursor/mcp.json` (global) or `.cursor/mcp.json` (project)
Windsurf	`~/.codeium/windsurf/mcp_config.json`
Cline (VS Code)	`cline_mcp_settings.json`, via Cline → MCP Servers → Configure MCP Servers (add `"disabled": false, "autoApprove": []` to the server entry)
Antigravity	Via Settings → MCP Servers → Add Server, or its config file directly

NOTE

Claude Code also supports adding the server via a one-liner instead of hand-editing JSON:

claude mcp add planka-mcp \
  --env PLANKA_BASE_URL=https://your-planka-instance.com \
  --env PLANKA_AGENT_EMAIL=agent@yourdomain.com \
  --env PLANKA_AGENT_PASSWORD=your-secure-password \
  --env PLANKA_IGNORE_SSL=true \
  -- npx -y @goldpulpy/planka-v2-mcp@latest

Restart the client after saving.

Codex CLI

Edit ~/.codex/config.toml:

[mcp_servers.planka-mcp]
command = "npx"
args = ["-y", "@goldpulpy/planka-v2-mcp@latest"]

[mcp_servers.planka-mcp.env]
PLANKA_BASE_URL = "https://your-planka-instance.com"
PLANKA_AGENT_EMAIL = "agent@yourdomain.com"
PLANKA_AGENT_PASSWORD = "your-secure-password"
PLANKA_IGNORE_SSL = "true"

Or add it in one line:

codex mcp add planka-mcp -- npx -y @goldpulpy/planka-v2-mcp@latest

then set the PLANKA_* variables in the generated [mcp_servers.planka-mcp.env] block.

Continue (VS Code / JetBrains extension)

Add to ~/.continue/config.yaml:

mcpServers:
  - name: planka-mcp
    command: npx
    args:
      - -y
      - "@goldpulpy/planka-v2-mcp@latest"
    env:
      PLANKA_BASE_URL: https://your-planka-instance.com
      PLANKA_AGENT_EMAIL: agent@yourdomain.com
      PLANKA_AGENT_PASSWORD: your-secure-password
      PLANKA_IGNORE_SSL: "true"

Zed

Edit ~/.config/zed/settings.json (macOS/Linux) or %APPDATA%\Zed\settings.json (Windows), or open it via Cmd+Shift+P → "zed: open settings":

{
  "context_servers": {
    "planka-mcp": {
      "source": "custom",
      "command": "npx",
      "args": ["-y", "@goldpulpy/planka-v2-mcp@latest"],
      "env": {
        "PLANKA_BASE_URL": "https://your-planka-instance.com",
        "PLANKA_AGENT_EMAIL": "agent@yourdomain.com",
        "PLANKA_AGENT_PASSWORD": "your-secure-password",
        "PLANKA_IGNORE_SSL": "true"
      }
    }
  }
}

"source": "custom" is required for manually-added servers (as opposed to ones installed via a Zed extension). Zed reloads the server automatically after saving - no editor restart needed.

Any other MCP-compatible client

The server is a standard stdio MCP server - any client that supports the command / args / env shape will work. Point it at:

npx -y @goldpulpy/planka-v2-mcp@latest

with the four PLANKA_* environment variables set as shown above.

Environment Variables

Variable	Required	Default	Description
`PLANKA_BASE_URL`	✅	-	Full URL of your Planka instance
`PLANKA_AGENT_EMAIL`	✅	-	Login email for the dedicated agent user
`PLANKA_AGENT_PASSWORD`	✅	-	Password for the agent user
`PLANKA_IGNORE_SSL`	❌	`false`	Skip SSL verification - self-signed/local certs only

Security

Authentication is performed using a dedicated Planka user account.
Credentials are supplied through environment variables only.
The MCP server does not persist board data outside the running process.
SSL certificate verification is enabled by default.
PLANKA_IGNORE_SSL=true should only be used in trusted local or self-hosted environments.

Troubleshooting

The client can't see any tools / connection fails silently

Confirm PLANKA_BASE_URL has no trailing slash and is reachable from the machine running the MCP server (not just your browser).
Check that the agent user can log in with those exact credentials through Planka's normal web UI first.

SSL / certificate errors

If your instance uses a self-signed certificate, set "PLANKA_IGNORE_SSL": "true". Avoid this in production - prefer a valid certificate instead.

Cards are created but checklists/subtasks aren't showing

Make sure the card type is "project" (the default). Cards created as "story" type don't expose Task Lists in the same way.

This project focuses exclusively on the MCP interface. For Planka server setup itself, see the official Planka documentation.

Try in Playground

Server Config

{
  "mcpServers": {
    "planka-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@goldpulpy/planka-v2-mcp@latest"
      ],
      "env": {
        "PLANKA_BASE_URL": "https://your-planka-instance.com",
        "PLANKA_AGENT_EMAIL": "agent@yourdomain.com",
        "PLANKA_AGENT_PASSWORD": "your-secure-password",
        "PLANKA_IGNORE_SSL": "true"
      }
    }
  }
}

Project Info

Created At

7 days ago

Updated At

7 days ago

Author Name

goldpulpy

Star

Language

License

Recommend Servers

View All

Serper MCP Server

@garymengcom

A Serper MCP Server

Python

a year ago

Time

@modelcontextprotocol

A Model Context Protocol server that provides time and timezone conversion capabilities. This server enables LLMs to get current time information and perform timezone conversions using IANA timezone names, with automatic system timezone detection.

5 months ago