kaneo (minimalist kanban) fork to experiment adding a tangled integration
github.com/usekaneo/kaneo
feat(docs): add mcp docs
+97
+96
apps/docs/core/integrations/mcp.mdx
+96
apps/docs/core/integrations/mcp.mdx
···
1
+
---
2
+
title: MCP
3
+
description: Connect Kaneo to MCP clients like Cursor and Claude Desktop using the official Kaneo MCP server.
4
+
---
5
+
6
+
Kaneo ships an official MCP server package, `@kaneo/mcp`, so you can manage workspaces, projects, tasks, comments, and labels from MCP-compatible tools.
7
+
8
+
The server runs locally over stdio and authenticates with Kaneo using device authorization.
9
+
10
+
## Prerequisites
11
+
12
+
- Node.js 20 or newer
13
+
- A running Kaneo API
14
+
- Access to the Kaneo web app to approve device login
15
+
16
+
By default, self-hosted Kaneo allows both `kaneo-cli` and `kaneo-mcp` as device auth client IDs.
17
+
18
+
## Install and register
19
+
20
+
Use the recommended interactive installer:
21
+
22
+
```bash
23
+
npx @kaneo/mcp
24
+
```
25
+
26
+
The installer lets you choose where to register the server configuration:
27
+
28
+
- Cursor (user-wide)
29
+
- Cursor (project-level)
30
+
- Claude Desktop
31
+
- Custom JSON config path
32
+
33
+
You can also run the explicit install command:
34
+
35
+
```bash
36
+
kaneo-mcp install --target cursor-user -y
37
+
```
38
+
39
+
Use `--help` to see all available targets and flags:
40
+
41
+
```bash
42
+
kaneo-mcp install --help
43
+
```
44
+
45
+
## Point to a self-hosted instance
46
+
47
+
When generating config, pass your Kaneo base URL:
48
+
49
+
```bash
50
+
kaneo-mcp install --target cursor-user -y --api-url https://kaneo.example.com
51
+
```
52
+
53
+
Or set it via environment variable:
54
+
55
+
| Variable | Description |
56
+
| --- | --- |
57
+
| `KANEO_API_URL` | Kaneo API origin. Default: `http://localhost:1337`. Do not include `/api`. |
58
+
| `KANEO_MCP_CLIENT_ID` | Device auth client ID. Default: `kaneo-mcp`. |
59
+
60
+
If you override `KANEO_MCP_CLIENT_ID`, make sure it is included in [`DEVICE_AUTH_CLIENT_IDS`](/core/installation/environment-variables).
61
+
62
+
## Authentication flow
63
+
64
+
On the first tool call that needs Kaneo access, the MCP server:
65
+
66
+
1. Requests a device code from Kaneo
67
+
2. Prints a verification URL and user code
68
+
3. Opens the browser when possible
69
+
4. Polls until you approve sign-in
70
+
5. Stores credentials in `~/.config/kaneo-mcp/credentials.json`
71
+
72
+
## Available tools
73
+
74
+
Current MCP tools include:
75
+
76
+
- Session: `whoami`, `list_workspaces`
77
+
- Projects: `list_projects`, `get_project`, `create_project`, `update_project`
78
+
- Tasks: `list_tasks`, `get_task`, `create_task`, `update_task`, `move_task`, `update_task_status`
79
+
- Comments: `list_task_comments`, `create_task_comment`
80
+
- Labels: `list_workspace_labels`, `create_label`, `attach_label_to_task`, `detach_label_from_task`
81
+
82
+
## Run manually for debugging
83
+
84
+
To run the stdio server directly:
85
+
86
+
```bash
87
+
npx @kaneo/mcp serve
88
+
```
89
+
90
+
When running from source in this monorepo:
91
+
92
+
```bash
93
+
pnpm --filter @kaneo/mcp run build
94
+
pnpm --filter @kaneo/mcp run start
95
+
```
96
+