mcp-kaneo
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KANEO_TOKEN | Yes | Kaneo API token | |
| KANEO_BASE_URL | Yes | Kaneo API URL (e.g., https://your-kaneo-instance.com/api) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workspacesA | List all accessible workspaces |
| list_projectsB | List all projects in a workspace |
| list_columnsA | List all columns in a project |
| list_tasksB | List tasks in a project with columns and pagination |
| searchC | Search tasks, projects, or comments |
| get_taskB | Get details of a specific task |
| create_taskB | Create a new task in a project |
| update_taskA | Update one or more task fields (partial update). Provide at least one update field. |
| delete_taskC | Delete a task |
| create_subtaskA | Create a subtask linked to a parent. Status inherits from parent unless specified. |
| list_subtasksB | List subtasks of a parent task |
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 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.