KanbiSign in

MCP server

Connect an AI agent

Kanbi exposes a Model Context Protocol server so coding agents — Claude Code, opencode, any MCP client — can read and write your boards from your editor or terminal. Auth is OAuth with a browser consent screen; there are no API keys to copy.

Endpoint

http://kanbi.nareshkhatri.site/api/mcp

Claude Code

Add the server, then run any kanbi tool (or /mcp) — Claude opens the consent screen, and after you approve the tools are live.

claude mcp add --transport http kanbi http://kanbi.nareshkhatri.site/api/mcp

opencode

Add the server to opencode.json (project) or ~/.config/opencode/opencode.json (global):

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kanbi": {
      "type": "remote",
      "url": "http://kanbi.nareshkhatri.site/api/mcp",
      "enabled": true
    }
  }
}

Then trigger the login (it also starts automatically the first time it hits the server):

opencode mcp auth kanbi

What an agent can do

Each tool wraps the same procedures the web app uses, so permissions, validation, and realtime updates apply identically. The agent acts as you, limited to the boards you can access.

  • list_projectsreadList projects you can access.
  • list_boardsreadList boards across your projects.
  • get_boardreadA board's columns, tasks, and labels.
  • search_tasksreadFull-text search across tasks.
  • get_board_contextreadColumn, label, and member ids plus valid priorities, for authoring.
  • create_taskswriteCreate one or more tasks on a board.
  • update_taskwriteUpdate fields on a task.
  • add_commentwriteAdd a comment to a task.

Scopes

Two scopes are enforced on every tool call: kanbi:read for the read tools and kanbi:write for the write tools. A read-only grant cannot create or edit anything. Add offline_access and the agent renews silently instead of reopening the browser.

Managing access

Every agent you authorize is listed under Profile → Connected apps with its scopes and when it was approved. Revoking takes effect immediately; the agent must re-authorize to reconnect.

Troubleshooting

Tools 401, or an endless re-auth loop. The token came back opaque instead of a JWT. Re-authorize with a clean token — for Claude Code, claude mcp remove kanbi then add it again.

Host mismatch. Point the agent at the same host this page is served from, so OAuth discovery, the token audience, and your browser session all line up on one origin.

Connect an AI agent · Kanbi