Kanban MCP server
{
"mcpServers": {
"kanbanthing": {
"type": "http",
"url": "https://www.kanbanthing.com/mcp"
}
}
}{
"mcpServers": {
"kanbanthing": {
"type": "http",
"url": "https://www.kanbanthing.com/mcp"
}
}
}{
"mcpServers": {
"kanbanthing": {
"type": "http",
"url": "https://www.kanbanthing.com/mcp"
}
}
}{
"servers": {
"kanbanthing": {
"type": "http",
"url": "https://www.kanbanthing.com/mcp"
}
}
}{
"mcpServers": {
"kanbanthing": {
"type": "http",
"url": "https://www.kanbanthing.com/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 0.1.0
What it does
An MCP server that creates and manages KanbanThing kanban boards through a command line interface. It allows developers and AI agents to programmatically control shared kanban boards with columns, cards, due dates, and multiple views, requiring only a board link and password.
- Automate board updates from scripts or AI agents by creating and moving cards with JSON output from CLI commands.
- Build kanban workflows into applications that need to track tasks across columns without requiring user accounts or API keys.
- Generate board state reports or integrate board data into other tools using the CLI's JSON output format.
Tools this server exposes
| Tool | Does |
|---|---|
| board_create | Create a new kanban board with a name and password, returning a shareable link. |
| board_list | List columns and cards on a board given its link and password. |
| card_create | Add a new card to a column with optional description, color, and due date. |
| card_move | Move a card between columns or within the backlog. |
| card_update | Edit a card's description, color, or due date. |
| card_delete | Remove a card from the board. |
| column_create | Add a new column to the board. |
| column_rename | Change the name of an existing column. |
| column_reorder | Rearrange the order of columns on the board. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.