bhokan-mcp

The official Model Context Protocol server for Bhokan. Point an MCP client at it — Claude Desktop, GitHub Copilot, Cursor, Codex, or any other — and it can read your boards, create and move cards, tick off checklists, and manage labels and members on your behalf, with the same permissions your API key has.

What you need

• Node.js 18 or newer.
• A Bhokan API key. Create one in Bhokan under Settings → API. The key is shown once, when it is created, and starts with bhokan_.
• A workspace on a plan that includes the REST API and the MCP server. Both are plan capabilities; a request into a workspace whose plan lacks either is refused with a message saying which.

The key belongs to you, not to a workspace, so one key reaches every workspace you are a member of. What the assistant can do in each one is exactly what you can do there.

Running it

No install step is needed. Your MCP client starts the server itself with:

pnpm dlx bhokan-mcp

The server is a stdio process: it reads requests from the client on standard input and never opens a port. Two environment variables tell it where to go and who you are:

| Variable | Value | | ------------------ | ----------------------------------------------- | | BHOKAN_BASE_URL | https://bhokan.com | | BHOKAN_API_TOKEN | Your API key, for example bhokan_a1b2c3d4e5f6 |

If you prefer a global install, pnpm add -g bhokan-mcp puts a bhokan-mcp command on your path that takes the same two variables.

Connecting a client

Every stdio-capable MCP client takes the same three things: the command, its arguments, and the two variables. Where they go differs by client.

Claude Desktop

Edit claude_desktop_config.json. On macOS it lives in ~/Library/Application Support/Claude/, on Windows in %APPDATA%\Claude\.

{
  "mcpServers": {
    "bhokan": {
      "command": "pnpm",
      "args": ["dlx", "bhokan-mcp"],
      "env": {
        "BHOKAN_BASE_URL": "https://bhokan.com",
        "BHOKAN_API_TOKEN": "bhokan_a1b2c3d4e5f6"
      }
    }
  }
}

Restart Claude Desktop and the Bhokan tools appear in the tools menu.

GitHub Copilot in VS Code

Open the Command Palette, run MCP: Open User MCP Configuration, and add:

{
  "servers": {
    "bhokan": {
      "type": "stdio",
      "command": "pnpm",
      "args": ["dlx", "bhokan-mcp"],
      "env": {
        "BHOKAN_BASE_URL": "https://bhokan.com",
        "BHOKAN_API_TOKEN": "bhokan_a1b2c3d4e5f6"
      }
    }
  }
}

Copilot uses the tools in Agent mode.

Cursor, Codex and others

Use the same command, arguments and variables in whatever shape your client's configuration takes. If the client asks for a "type", it is stdio.

What it is good for

The assistant sees your workspaces the way you do, so you can talk about them by name. A few things people ask for:

• "Which cards on the Website board are due this week and still not done?"
• "Add a card to Inbox on the Support board: customer cannot export a CSV. Label it bug, due Friday."
• "Move everything from Review to Done on the Onboarding board."
• "Put a checklist on the Launch card with: freeze content, run the smoke test, tell the team."
• "Who is on the Design workspace, and which of them are admins?"
• "Make a board called Hiring in the Ops workspace with the lists Applied, Interview, Offer, Hired."
• "Summarise the comments on the Pricing page card."

The tools

Forty-six tools, grouped by what they touch. Names are stable and each one is described to the client, so the assistant picks them itself.

| Area | What the assistant can do | | ---------- | ------------------------------------------------------------------------------------------------------------- | | Workspaces | List yours, find one by name or slug, create, rename, delete, search across a workspace, check a slug is free | | Boards | List, find by name or slug, read with its lists and cards, create, update, delete | | Lists | Create, rename, delete | | Cards | Create, read in full, update or move, delete, duplicate, read the activity history | | On a card | Add, edit and delete comments; put a label on or take it off; assign or unassign a member | | Checklists | Create, rename and delete checklists; add, tick, edit and delete their items | | Labels | Read, create, recolour or rename, delete | | Members | Invite by email, remove, change a role, create and revoke invite links |

Anything the assistant does is done as you, and shows up in the card's activity history under your name.

When something goes wrong

• The server exits at once and the client reports it as disconnected: one of the two variables is missing. The error names which.
• Every request fails with 401: the key is wrong or has been revoked. Create a new one under Settings → API.
• Requests into one workspace fail with 403: that workspace's plan does not include the REST API or the MCP server; the message says which.
• 429 responses: you have hit the per-minute allowance for the workspace's plan. The message says what the allowance is.

License and support

Proprietary — all rights reserved. © Bhokan. See the LICENSE file that ships with the package.

Questions and problems: [email protected].