vibe-kanban-mcp
Vibe Kanban via MCPorter — Skill
This skill teaches agents to operate Vibe Kanban entirely through MCPorter CLI commands. MCPorter bridges MCP servers to the terminal so any agent with shell access can drive Vibe Kanban without editor-integrated MCP support.
All tool calls follow the pattern:
mcporter call vibe_kanban.<tool_name> param=value ...
Source:
crates/mcp/src/task_server/tools/
Last updated: 2026-03-09
Quick navigation
| What you need | Reference file |
|---|---|
| MCPorter setup, call syntax, executors, workflows | references/overview.md |
list_organizations, list_org_members, list_projects |
references/organizations-projects.md |
| Create / list / get / update / delete issues | references/issues.md |
| Assignees, tags, issue relationships | references/issues.md |
Workspaces, start_workspace_session, link_workspace |
references/workspaces-sessions.md |
| Repositories and script management | references/repos.md |
Tool module summary
| Module | Tools | Description |
|---|---|---|
organizations |
2 | Organisation & member listing |
remote_projects |
1 | Project listing |
remote_issues |
5 | Issue CRUD |
issue_assignees |
3 | Assignee management |
issue_tags |
4 | Tag management |
issue_relationships |
2 | Issue relationships |
workspaces |
3 | Local workspace CRUD |
repos |
4+ | Repository & script management |
task_attempts |
2 | Workspace session start & link |
context |
N | ID resolution and context-related guidance |
How to use this skill
-
Ensure MCPorter is available — see
references/overview.mdfor installation and Vibe Kanban server registration. -
Identify what the user wants to do — pick the closest workflow from the table above and read the matching reference file.
-
Always pass IDs explicitly —
project_id,organization_id, andworkspace_idmust be provided in every call. Resolve them first by calling the corresponding list tools. -
Follow the workflow examples — each reference file contains end-to-end MCPorter command sequences. Always resolve IDs by calling list tools before using them in create/update/delete calls.
-
Pick the right executor — when calling
start_workspace_session, the executor string must match one of the supported values.
Full list:references/overview.md→ "Supported Executors".