Kanboard MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_AUTH | No | Authentication mode: none, bearer or github. | none |
| MCP_HOST | No | HTTP bind address. The Docker image uses 0.0.0.0. | 127.0.0.1 |
| MCP_PORT | No | HTTP bind port. | 8000 |
| FASTMCP_HOME | No | Where OAuth state is stored. The Docker image uses /data. | ~/.local/share/fastmcp |
| KANBOARD_URL | Yes | Kanboard base URL; /jsonrpc.php is appended if missing. | |
| MCP_BASE_URL | No | Public URL of this server, used for github authentication. | |
| MCP_TRANSPORT | No | Transport mode: stdio or http. | stdio |
| GITHUB_CLIENT_ID | No | GitHub OAuth app client ID. | |
| KANBOARD_TIMEOUT | No | Request timeout in seconds. | 20 |
| MCP_BEARER_TOKEN | No | Shared secret for bearer authentication (32+ characters). | |
| KANBOARD_USERNAME | No | Your username for a personal access token, or jsonrpc for an application token. | jsonrpc |
| KANBOARD_API_TOKEN | Yes | Kanboard API token. | |
| KANBOARD_VERIFY_SSL | No | Set false for self-signed certificates. | true |
| MCP_JWT_SIGNING_KEY | No | Optional key for tokens the server issues. | |
| GITHUB_CLIENT_SECRET | No | GitHub OAuth app client secret. | |
| KANBOARD_DEFAULT_USER_ID | No | Comment author when using the application token. | |
| MCP_ALLOWED_GITHUB_USERS | No | Comma-separated GitHub logins allowed to connect. | |
| MCP_ALLOW_UNAUTHENTICATED | No | Set to true to allow serving HTTP on a non-loopback address without authentication when a proxy in front handles auth. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Tools for a self-hosted Kanboard instance.
Call list_projects first to find project IDs; get_board shows columns and open tasks.
Priority: higher number = more important (Kanboard default range 0-3).
Use search_tasks with Kanboard filter syntax (e.g. 'status:open assignee:me due:<=today').
Use get_task to read the full context (comments, subtasks, attachments) before summarising.
Log progress with add_comment; move work across the board with move_task.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_meA | Show which Kanboard user/API mode this server is connected as. |
| list_projectsA | List Kanboard projects (ID, name, board URL). Start here to find project IDs. |
| get_boardA | Show a project's board: each column with its open tasks, in order. |
| list_tasksB | List tasks in a project, optionally filtered by status and column. |
| search_tasksA | Search tasks with Kanboard's filter syntax across one or all projects. |
| get_overdue_tasksA | List open tasks whose due date has passed. |
| list_project_usersA | List users that can be assigned tasks in a project, as {user_id: name}. |
| get_taskB | Get everything about a task: details, tags, subtasks, comments and attachments. Use this to summarise or review a task's progress. |
| get_task_fileA | Read a task attachment: images are returned as images, text files as text. |
| create_taskC | Create a task. Defaults to the project's first column. |
| update_taskB | Update task fields. Only the fields you pass are changed. |
| move_taskA | Move a task to another column of its board (e.g. 'In progress', 'Done'). |
| close_taskA | Close (complete) a task. It can be reopened with reopen_task. |
| reopen_taskB | Reopen a closed task. |
| add_commentB | Add a comment (Markdown supported) to a task, e.g. a progress log entry. |
| create_subtaskC | Add a subtask (checklist item) to a task. |
| update_subtaskC | Change a subtask's status or title. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
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).
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.
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.
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.