mcp-kaneo
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-kaneo create a task called 'Update API docs' with medium priority"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-kaneo
MCP server for Kaneo task management API. Lets your AI coding assistant manage tasks, projects, labels, and comments in Kaneo.
Features
Tasks: Create, read, update, delete tasks
Projects: List and manage projects
Labels: Create, update, delete labels; attach/detach from tasks
Comments: Add and list comments on tasks
Search: Search tasks, projects, and workspaces
Workspaces: List workspaces and organizations
Task Relations: Create subtask relations (links to Kaneo's native subtasks)
Related MCP server: Kanboard MCP Server
Requirements
Installation
Using npx (recommended)
npx @fastman/mcp-kaneoUsing npm
npm install -g @fastman/mcp-kaneo
npx @fastman/mcp-kaneoConfiguration
Environment Variables
Variable | Required | Description |
| Yes | Kaneo API URL (e.g., |
| Yes | Kaneo API token |
| No | Comma-separated toolset names (default: |
Toolsets
The server organizes tools into groups. By default only the core toolset is registered, keeping context size minimal.
Toolset | Tools | Description |
| 11 | Task lifecycle, listing, search, subtasks |
| 14 | Labels, comments, task relations |
| 7 | Workspace and project CRUD |
| 6 | Field-specific task update tools (deprecated) |
Configuration examples:
# Default: core only (11 tools)
npx @fastman/mcp-kaneo
# Core + labels and comments
KANEO_TOOLSETS=core,collaboration npx @fastman/mcp-kaneo
# All non-legacy tools
KANEO_TOOLSETS=all npx @fastman/mcp-kaneo
# Everything including legacy field-specific updates
KANEO_TOOLSETS=all,legacy npx @fastman/mcp-kaneoThe all alias expands to core,collaboration,admin (excludes legacy).
Codex
Add the server with the Codex CLI:
codex mcp add kaneo \
--env KANEO_BASE_URL=https://your-kaneo-instance.com/api \
--env KANEO_TOKEN=your-token \
-- npx -y @fastman/mcp-kaneoThis stores the environment values in Codex's configuration. To keep the token
out of the configuration file, export the variables before starting Codex and
add the following to ~/.codex/config.toml (or .codex/config.toml in a trusted
project):
[mcp_servers.kaneo]
command = "npx"
args = ["-y", "@fastman/mcp-kaneo"]
env_vars = ["KANEO_BASE_URL", "KANEO_TOKEN", "KANEO_TOOLSETS"]For local development, build the project and replace the command and arguments:
[mcp_servers.kaneo]
command = "node"
args = ["/absolute/path/to/mcp-kaneo/dist/index.js"]
env_vars = ["KANEO_BASE_URL", "KANEO_TOKEN", "KANEO_TOOLSETS"]Run codex mcp list to verify the configuration. In the Codex terminal UI, use
/mcp to confirm that the server is active and its tools are available.
OpenCode
Add to your ~/.config/opencode/opencode.json:
{
"mcp": {
"kaneo": {
"type": "local",
"command": ["npx", "-y", "@fastman/mcp-kaneo"],
"environment": {
"KANEO_BASE_URL": "https://your-kaneo-instance.com/api",
"KANEO_TOKEN": "${KANEO_TOKEN}"
}
}
}
}Or for local development:
{
"mcp": {
"kaneo": {
"type": "local",
"command": ["node", "/path/to/mcp-kaneo/dist/index.js"],
"environment": {
"KANEO_BASE_URL": "https://your-kaneo-instance.com/api",
"KANEO_TOKEN": "your-token"
}
}
}
}Claude Code
claude mcp add kaneo --scope user npx @fastman/mcp-kaneoCline
Add to your MCP settings:
{
"mcpServers": {
"kaneo": {
"command": "npx",
"args": ["-y", "@fastman/mcp-kaneo"]
}
}
}Cursor
Go to Cursor Settings → MCP → New MCP Server:
{
"command": "npx",
"args": ["-y", "@fastman/mcp-kaneo"]
}Tools
Core (default)
list_workspaces- List all accessible workspaceslist_projects- List projects in a workspacelist_columns- List columns in a projectlist_tasks- List tasks in a project with columns and paginationsearch- Search tasks, projects, or commentsget_task- Get task detailscreate_task- Create a new taskupdate_task- Update one or more task fields (partial update)delete_task- Delete a taskcreate_subtask- Create a subtask linked to a parent (inherits parent status by default)list_subtasks- List subtasks for a parent task
Collaboration (KANEO_TOOLSETS=collaboration)
list_labels- List workspace labelscreate_label- Create a new labelupdate_label- Update label name/colordelete_label- Delete a labelattach_label- Attach label to taskdetach_label- Detach label from tasklist_task_labels- List labels on a taskadd_comment- Add comment to tasklist_comments- List comments on taskedit_comment- Edit a commentdelete_comment- Delete a commentcreate_task_relation- Create a relation between taskslist_task_relations- List all relations for a taskdelete_task_relation- Delete a task relation
Admin (KANEO_TOOLSETS=admin)
get_workspace- Get workspace detailsupdate_workspace- Update a workspacedelete_workspace- Delete a workspaceget_project- Get project detailscreate_project- Create a new projectupdate_project- Update a projectdelete_project- Delete a project
Legacy (KANEO_TOOLSETS=legacy)
Field-specific task update tools preserved for migration. Use update_task instead.
update_task_title- Update task titleupdate_task_description- Update task descriptionupdate_task_status- Update task statusupdate_task_priority- Update task priorityupdate_task_assignee- Update task assigneeupdate_task_due_date- Update task due date
Usage Examples
Create a task
Create a task in kaneo called "Fix login bug" with high priorityUpdate multiple fields
Update task #123: set priority to urgent and move to in-progressCreate a subtask
Create a subtask "Fix the login validation" for parent task #123List subtasks
List all subtasks for task #123Add a label (requires collaboration toolset)
Create a label called "bug" with color #ef4444 and attach it to the taskUpdate task status
Move the task "Fix login bug" to in-progressDevelopment
# Install dependencies
npm install
# Build
npm run build
# Test
npm test
# Run locally
npm startLicense
MIT
Available Tools
11 toolscreate_subtaskA
Create a subtask linked to a parent. Status inherits from parent unless specified.
Inputs: title (required), parentTaskId (required), status, priority, +1 more.
create_taskB
Create a new task in a project
Inputs: title (required), status (required), priority (required), projectId (required), +1 more.
delete_taskC
Delete a task
Inputs: taskId (required).
get_taskB
Get details of a specific task
Inputs: taskId (required).
list_columnsA
List all columns in a project
Inputs: projectId (required).
list_projectsB
List all projects in a workspace
Inputs: workspaceId (required).
list_subtasksB
List subtasks of a parent task
Inputs: parentTaskId (required).
list_tasksB
List tasks in a project with columns and pagination
Inputs: projectId (required).
list_workspacesA
List all accessible workspaces
Inputs: workspaceId.
searchC
Search tasks, projects, or comments
Inputs: query (required), type, limit, projectId, +1 more.
update_taskA
Update one or more task fields (partial update). Provide at least one update field.
Inputs: taskId (required), title, status, userId, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
Most tools have a clear resource+action split, and task CRUD operations are distinct. The only real ambiguity is between list_tasks and list_subtasks, since it is not stated whether project-level task listing includes subtasks.
All tool names use snake_case with consistent list_/get_/create_/update_/delete_ prefixes. 'search' is the only bare verb, but it is a conventional and easily understood exception.
Eleven tools is well-scoped for a task-management server: it covers hierarchy traversal, task CRUD, subtask operations, and search without unnecessary duplication.
The task lifecycle is complete with create, read, update, and delete, and the listing/search tools cover common lookup needs. The main gaps are the lack of explicit subtask update/delete operations and no create/update/delete for projects or columns, though these may be workable or out of scope.
Maintenance
Related MCP Connectors
Headless task management for bots, apps and AI agents. Remote MCP server, OAuth or access token.
Official Todoist MCP server. Manage tasks and projects. Hosted, no API key needed.
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA minimal MCP server that enables AI assistants to manage a kanban issue board. It provides tools for listing, creating, updating, and deleting issues with support for both local development and team deployments.10-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that exposes Kanboard API functionality to Large Language Models (LLMs), enabling AI assistants to interact with Kanboard project management system.15 PyPI2MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for kanban-tui, a terminal-based task manager, that exposes task, board, and column management commands for AI agents to interact with.65 PyPI287MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that enables AI agents to manage tasks, boards, lists, and comments on a Kanban-style project management system through JSON-RPC methods.14 npm2AGPL 3.0