Vibe Kanban MCP

Control the local vibe-kanban MCP server to list orgs/projects/issues, create/update issues, manage workspaces, and find dashboard ports on macOS.

Security Scan

The skill's instructions match its stated purpose (controlling a local vibe-kanban MCP and probing local dashboard ports), but there are small incoherences (registry metadata doesn't declare required binaries) and the runtime examples include running npx to fetch/launch code — so review before use.

Purpose & Capability

SKILL.md describes exactly the claimed functionality (mcporter calls to a local vibe-kanban MCP and macOS port discovery). However the registry metadata lists no required binaries/env vars while the docs explicitly require mcporter, a running vibe-kanban instance, and optionally lsof/netstat/jq. This metadata mismatch is an inconsistency the author should have declared.

Instruction Scope

Instructions are narrowly scoped to running mcporter RPC calls, inspecting local processes (ps, lsof/netstat), and curling localhost ports to verify the UI. They do not ask for external credentials or exfiltrate data; the commands operate on local services and ports as required for the stated goal.

Install Mechanism

No install spec is present (instruction-only), so nothing is automatically downloaded or written by the platform. The SKILL.md contains an example of configuring mcporter to run 'npx ... vibe-kanban@latest', which would fetch code at runtime via npm if the user follows that example — this is a user-side action, not an automatic install described in the skill manifest.

Credentials

The skill declares no required environment variables or credentials and its instructions do not reference secrets. Required artifacts (mcporter, vibe-kanban process) are proportionate to the task. No unrelated service credentials are requested.

Persistence & Privilege

The skill does not request always: true and has no install-time persistence. It is instruction-only and does not modify other skills or global agent settings. Autonomous invocation is allowed (platform default) but not combined with other high-risk factors.

What to consider before installing

This skill appears to do what it says: it gives shell commands to control a locally running vibe-kanban MCP and to find/verify dashboard ports. Before installing or using it, note two things: (1) the registry metadata omits required binaries (mcporter and a running vibe-kanban) even though the SKILL.md requires them—verify those prerequisites yourself; (2) the example mcporter config uses 'npx ... vibe-kanban@latest', which will download and run code from npm if you follow it—only run that if you trust the package source. Because this is an instruction-only skill, nothing is automatically installed by the platform, but the provided commands will inspect local processes (ps, lsof/netstat) and probe localhost ports (curl), which is expected for this purpose but does expose process/port information on your machine. If you are unsure, run the listed commands manually and inspect any packages (e.g., the vibe-kanban npm package) before executing them.

Source repo: https://github.com/DevBD1/openclaw-skill-vibe-kanban-mcp

Prereqs / setup check

You need all three:

1. mcporter installed and on PATH
2. vibe-kanban installed and running locally (dashboard + MCP)
3. An mcporter config entry named vibe_kanban (so mcporter call vibe_kanban.* works)

Quick checks:

command -v mcporter
mcporter config get vibe_kanban --json
mcporter list vibe_kanban --schema

If vibe_kanban is missing, add it as a stdio server (example):

mcporter config add vibe_kanban --command npx --arg -y --arg vibe-kanban@latest --arg --mcp

If the dashboard is running but you don’t know the port(s):

ps aux | rg -i 'vibe[- ]kanban'
/usr/sbin/lsof -nP -p <pid> -a -iTCP -sTCP:LISTEN

Notes:

• jq is helpful for scripting (jq -r .issue_id) but not required.

Quick start (mcporter)

mcporter config get vibe_kanban --json
mcporter list vibe_kanban --schema
mcporter call vibe_kanban.list_organizations --args '{}' --output json

Notes:

• vibe_kanban is typically stdio (e.g., npx -y vibe-kanban@latest --mcp). The web dashboard listens on separate local ports.
• Prefer --output json for calls you will parse.

Common workflows

List orgs → projects → issues

# orgs
mcporter call vibe_kanban.list_organizations --args '{}' --output json

# projects in an org
mcporter call vibe_kanban.list_projects --args '{"organization_id":"<org_uuid>"}' --output json

# issues in a project
mcporter call vibe_kanban.list_issues --args '{"project_id":"<project_uuid>","limit":50,"offset":0}' --output json

Create an issue and put it in “To do”

create_issue returns issue_id. Then set the workflow state with update_issue.

ISSUE_ID=$(mcporter call vibe_kanban.create_issue \
  --args '{"project_id":"<project_uuid>","title":"My task","description":"Details","priority":"high"}' \
  --output json | jq -r .issue_id)

mcporter call vibe_kanban.update_issue \
  --args "{\"issue_id\":\"$ISSUE_ID\",\"status\":\"To do\"}" \
  --output json

Bulk-create 5 tasks quickly:

for t in "Task 1" "Task 2" "Task 3" "Task 4" "Task 5"; do
  ISSUE_ID=$(mcporter call vibe_kanban.create_issue \
    --args "{\"project_id\":\"<project_uuid>\",\"title\":\"$t\"}" \
    --output json | jq -r .issue_id)
  mcporter call vibe_kanban.update_issue \
    --args "{\"issue_id\":\"$ISSUE_ID\",\"status\":\"To do\"}" \
    --output json >/dev/null
done

Start a workspace session linked to an issue

Get repo IDs (for repos: [{repo_id, base_branch}]):

mcporter call vibe_kanban.list_repos --args '{}' --output json

Start a workspace session and link it at creation using issue_id:

mcporter call vibe_kanban.start_workspace_session --args '{
  "title": "ISS-123 My task",
  "executor": "CODEX",
  "repos": [{"repo_id":"<repo_uuid>","base_branch":"main"}],
  "issue_id": "<issue_uuid>"
}' --output json

If you already have both IDs, link later:

mcporter call vibe_kanban.link_workspace \
  --args '{"workspace_id":"<workspace_uuid>","issue_id":"<issue_uuid>"}' \
  --output json

Find the local vibe-kanban dashboard port (macOS)

The port is ephemeral. Find it from the process:

ps aux | rg -i 'vibe[- ]kanban'
# then
/usr/sbin/lsof -nP -p <pid> -a -iTCP -sTCP:LISTEN

Verify which port is the actual UI:

curl -sS -D - http://127.0.0.1:<port>/ -o /dev/null | head

Pitfall:

• You may see two listening ports; one can return 502 Bad Gateway with a “Dev server unreachable …” message.
• lsof/netstat might not be on PATH; use /usr/sbin/lsof and /usr/sbin/netstat.