Skip to main content
Glama

Kanboard MCP Server

An MCP server that lets Claude create, update and track tasks on your self-hosted Kanboard, from Claude Code, Claude Desktop, claude.ai or the Claude mobile apps.

It talks to Kanboard only through its JSON-RPC API, so it works with any Kanboard instance you can reach over HTTP (localhost, LAN or a public URL) and with any Kanboard database backend.

Tools

Tool

What it does

list_projects

Projects with IDs and board links

get_board

Columns of a project with their open tasks

list_tasks

Tasks in a project, filtered by open / closed / all and column

search_tasks

Kanboard filter syntax (assignee:me status:open due:<=today), one or all projects

get_overdue_tasks

Overdue tasks, for you or for one project

get_task

Details, tags, subtasks, comments and attachment list

get_task_file

Read an attachment: images come back as images, text files as text

create_task / update_task

Title, description, priority, column, assignee, due date, tags

move_task

Move a task to another column (by name)

close_task / reopen_task

Complete or reopen

add_comment

Add a progress note (Markdown)

create_subtask / update_subtask

Checklist items and their status

list_project_users

Assignable users

get_me

Which Kanboard user and API mode the server is using

Read-only tools are annotated as such, so Claude clients can auto-approve them and ask before writes.

Related MCP server: kanban-mcp

1. Get a Kanboard API token

You can use either kind of token:

  • Personal access token (recommended): Kanboard → My profile → API → generate a token. Set KANBOARD_USERNAME to your login name. Actions run as you and follow your project permissions.

  • Application token: Kanboard → Settings → API. Set KANBOARD_USERNAME=jsonrpc. It has full access to every project. Set KANBOARD_DEFAULT_USER_ID so comments have an author.

The two are easy to mix up: the application token used with your own username fails with 401 Unauthorized.

Also set Kanboard's Settings → Application settings → Application URL to the address you open Kanboard at; otherwise the task links Claude shows you point to http://localhost/....

2. Use it from Claude Code on the same machine (stdio)

No clone needed. uv fetches and runs the server:

claude mcp add --scope user kanboard \
  --env KANBOARD_URL=http://localhost:8080 \
  --env KANBOARD_USERNAME=your-username \
  --env KANBOARD_API_TOKEN=your-token \
  -- uvx --from git+https://github.com/b-ak/kanboard-mcp-server kanboard-mcp

--scope user makes the server available in every project; without it, it is registered for the current folder only.

Claude Desktop's claude_desktop_config.json takes the same command:

{
  "mcpServers": {
    "kanboard": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/b-ak/kanboard-mcp-server", "kanboard-mcp"],
      "env": {
        "KANBOARD_URL": "http://localhost:8080",
        "KANBOARD_USERNAME": "your-username",
        "KANBOARD_API_TOKEN": "your-token"
      }
    }
  }
}

3. Use it from claude.ai and the Claude mobile apps (remote HTTP)

claude.ai and the mobile apps connect from Anthropic's cloud, so the server must:

  1. run where it can reach Kanboard (e.g. on the same Raspberry Pi),

  2. be reachable at a public HTTPS URL (Cloudflare Tunnel, Tailscale Funnel or a reverse proxy),

  3. require login. GitHub OAuth is built in and limited to the GitHub accounts you list.

Claude (web / mobile / Code) ──HTTPS──▶ tunnel/proxy ──▶ kanboard-mcp :8000 ──▶ Kanboard

docs/deployment.md walks through the whole setup step by step: Kanboard token, GitHub OAuth App, Docker Compose, Cloudflare Tunnel, connecting Claude, verification and troubleshooting.

Once it's running at https://kanboard-mcp.example.com:

  • claude.ai / mobile: Settings → Connectors → Add custom connector, URL https://kanboard-mcp.example.com/mcp, then sign in with GitHub. Connectors you add on claude.ai are also available in the Claude mobile apps.

  • Claude Code: claude mcp add --scope user --transport http kanboard https://kanboard-mcp.example.com/mcp, then run /mcp to sign in.

4. Tell Claude when to use it

Connecting gives Claude the tools, not the habits. Put your rules (which project, when to create, move, comment or close tasks, what to ask first) in your project's CLAUDE.md or a claude.ai Project's instructions. Start from docs/claude-md-template.md.

Configuration

All settings are environment variables. See .env.example. The CLI also accepts --env-file, --transport, --host and --port.

Variable

Default

Description

KANBOARD_URL

required

Kanboard base URL; /jsonrpc.php is appended if missing

KANBOARD_USERNAME

jsonrpc

Your username (personal token) or jsonrpc (application token)

KANBOARD_API_TOKEN

required

API token

KANBOARD_DEFAULT_USER_ID

Comment author when using the application token

KANBOARD_VERIFY_SSL

true

Set false for self-signed certificates

KANBOARD_TIMEOUT

20

Request timeout in seconds

MCP_TRANSPORT

stdio

stdio or http

MCP_HOST / MCP_PORT

127.0.0.1 / 8000

HTTP bind address (Docker image uses 0.0.0.0)

MCP_AUTH

none

none, bearer or github

MCP_BEARER_TOKEN

Shared secret for bearer (32+ chars)

MCP_BASE_URL

Public URL of this server, for github

GITHUB_CLIENT_ID / GITHUB_CLIENT_SECRET

GitHub OAuth app credentials

MCP_ALLOWED_GITHUB_USERS

Comma-separated GitHub logins allowed to connect

MCP_JWT_SIGNING_KEY

derived

Optional key for tokens the server issues

FASTMCP_HOME

~/.local/share/fastmcp

Where OAuth state is stored (/data in Docker)

The server refuses to serve HTTP on a non-loopback address without authentication, unless you set MCP_ALLOW_UNAUTHENTICATED=true because a proxy in front of it already handles auth.

Development

uv sync
uv run pytest
uv run ruff check . && uv run ruff format --check .
uv run kanboard-mcp --env-file .env                      # stdio
uv run kanboard-mcp --env-file .env --transport http     # http on 127.0.0.1:8000
npx @modelcontextprotocol/inspector                      # optional: browse the tools

License

Apache-2.0

Available Tools

17 tools
add_commentB

Add a comment (Markdown supported) to a task, e.g. a progress log entry.

Inputs: content (required), task_id (required). Returns: result

close_taskA

Close (complete) a task. It can be reopened with reopen_task.

Inputs: task_id (required). Returns: result

create_subtaskC

Add a subtask (checklist item) to a task.

Inputs: title (required), task_id (required), user_id, time_estimated. Returns: result

create_taskC

Create a task. Defaults to the project's first column.

Inputs: title (required), project_id (required), tags, column, +4 more. Returns: object

get_boardA
Read-only

Show a project's board: each column with its open tasks, in order.

Inputs: project_id (required). Returns: object

get_meA
Read-only

Show which Kanboard user/API mode this server is connected as.

Inputs: no named parameters. Returns: object

get_overdue_tasksA
Read-only

List open tasks whose due date has passed.

Inputs: project_id. Returns: result

get_taskB
Read-only

Get everything about a task: details, tags, subtasks, comments and attachments.

Use this to summarise or review a task's progress.

Inputs: task_id (required), max_comments. Returns: object

get_task_fileA
Read-only

Read a task attachment: images are returned as images, text files as text.

Inputs: file_id (required).

list_projectsA
Read-only

List Kanboard projects (ID, name, board URL). Start here to find project IDs.

Inputs: include_inactive. Returns: result

list_project_usersA
Read-only

List users that can be assigned tasks in a project, as {user_id: name}.

Inputs: project_id (required). Returns: object

list_tasksB
Read-only

List tasks in a project, optionally filtered by status and column.

Inputs: project_id (required), column, status. Returns: result

move_taskA

Move a task to another column of its board (e.g. 'In progress', 'Done').

Inputs: column (required), task_id (required), position. Returns: object

reopen_taskB

Reopen a closed task.

Inputs: task_id (required). Returns: result

search_tasksA
Read-only

Search tasks with Kanboard's filter syntax across one or all projects.

Inputs: query (required), project_id. Returns: result

update_subtaskC

Change a subtask's status or title.

Inputs: task_id (required), subtask_id (required), title, status. Returns: result

update_taskB

Update task fields. Only the fields you pass are changed.

Inputs: task_id (required), tags, title, due_date, +3 more. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools target a clear resource+action pair (get_task, move_task, close_task, add_comment), and the create/update split is well signposted. The only real overlap is list_tasks vs search_tasks vs get_board vs get_overdue_tasks, which all return task collections, but the descriptions differentiate them by filter mechanism (status/column vs Kanboard filter syntax vs board layout vs due date).

    Naming Consistency5/5

    Every name is snake_case verb_noun: get_*, list_*, search_*, create_*, update_*, move_*, close_*, reopen_*, add_*. Verb choice is semantically consistent (get for single-item fetch, list for collections, create/update for mutations), with only trivial variance like add_comment vs create_subtask reflecting the domain.

    Tool Count4/5

    17 tools is slightly on the heavy side but each covers a distinct slice of the Kanboard domain (identity, projects, board, tasks, subtasks, comments, files, users) with little redundancy. Nothing looks like filler; it sits just above the comfortable band rather than being bloated.

    Completeness3/5

    The task lifecycle is well covered (create, update, move, close, reopen, comment, subtask, read attachment), but project management is read-only — no create_project, update_project, or archive, and there is no delete_task, delete_subtask, or delete_comment. File handling is also read-only (get_task_file with no upload), so an agent hitting those operations dead-ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers