🔄 Kanban MCP

Created By
bradrissea year ago
MCP Kanban is a specialized middleware designed to facilitate interaction between Large Language Models (LLMs) and Planka, a Kanban board application. It serves as an intermediary layer that provides LLMs with a simplified and enhanced API to interact with Planka's task management system.
Overview

What is MCP Kanban?

MCP Kanban is a specialized middleware designed to facilitate interaction between Large Language Models (LLMs) and Planka, a Kanban board application. It serves as an intermediary layer that provides LLMs with a simplified and enhanced API to interact with Planka's task management system.

How to use MCP Kanban?

To use MCP Kanban, set up a Planka Kanban board and the MCP Kanban server. Clone the repository, configure environment variables, build the server, and start the Planka containers. Access the Planka board at the specified URL and create a project to begin.

Key features of MCP Kanban?

  • Access Kanban data including projects, boards, lists, and tasks.
  • Manage workflow by moving cards between lists.
  • Track tasks by creating, updating, and completing tasks within cards.
  • Communicate progress through comments and labels.
  • Support task-oriented development using Kanban methodology.

Use cases of MCP Kanban?

  1. Enabling LLMs to manage software development tasks effectively.
  2. Facilitating collaboration between human developers and AI assistants.
  3. Streamlining task management and progress tracking in software projects.

FAQ from MCP Kanban?

  • Can MCP Kanban work with any Kanban board?

No, it is specifically designed to work with Planka.

  • Is MCP Kanban free to use?

Yes, it is open-source and available on GitHub.

  • What are the prerequisites for using MCP Kanban?

You need Docker, Git, Node.js, and npm installed on your system.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
bradrisse
Star
3
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago