MCP server

Bhokan has a Model Context Protocol (MCP) server. Connect it to an assistant that speaks MCP — Claude Desktop, GitHub Copilot, Cursor, Codex and others — and the assistant can read your boards, create and move cards, tick off checklists and manage labels and members, using your account and nothing more than your account can do. The server runs on your own machine. Your assistant starts it, talks to it over standard input and output, and it calls Bhokan’s REST API on your behalf with your API key. Nothing is stored in between.

Before you start

An API key. Go to Settings → API and create one. It is shown once, when it is created, and starts with bhokan_.
Node.js 18 or newer on the machine where your assistant runs.
A workspace on a plan that includes the MCP server. Both the REST API and the MCP server are plan capabilities, so an assistant reaching into a workspace whose plan lacks either is refused with a message saying which. The key still works everywhere else.

A key belongs to you, not to a workspace, so one key reaches every workspace you are a member of. In each one the assistant has your role and your permissions, and everything it does is recorded in the activity history under your name.

Setting up

There is no install step. Your assistant runs the server itself with pnpm dlx bhokan-mcp, and two environment variables tell the server where Bhokan is and who you are.

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

Claude Desktop

Open claude_desktop_config.json — on macOS it lives in ~/Library/Application Support/Claude/, on Windows in %APPDATA%\Claude\ — and add Bhokan to mcpServers:

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

Restart Claude Desktop. The Bhokan tools appear in the tools menu of a new conversation.

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 other assistants

Every assistant that supports stdio MCP servers takes the same three things: the command pnpm, the arguments dlx bhokan-mcp, and the two variables. Where they go differs by product; if it asks for a server type, answer stdio.

Keep the key out of anything you share. The configuration file holds it in plain text, and whoever has it can act as you in every workspace you belong to. If a key leaks, revoke it under Settings → API and create a new one.

What you can ask for

The assistant sees your workspaces, boards and lists by name, so you can talk about them the way you would to a colleague.

“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.”

What the assistant can do

The server offers 46 tools. Each one is described to the assistant, so it picks the right ones on its own.

Area	Actions
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

Deleting and removing are on that list. An assistant only does what you ask, but it does it without a confirmation dialog, so ask for what you mean.

Rate limits

Each workspace’s plan sets how many API requests a minute it allows, counted across every key and assistant that reaches into it. An assistant that works through a long list of cards can use that allowance quickly; when it runs out, requests fail with 429 until the minute passes, and the message says what the allowance is.

When something goes wrong

The assistant says the server disconnected at once. One of the two variables is missing. The server’s 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.
Requests fail with 429. The workspace’s per-minute allowance is used up. Wait a minute, or ask for less at a time.

The server is published on npm as bhokan-mcp.

Get Started

Import

Integrations

Before you start

Setting up

Claude Desktop

GitHub Copilot in VS Code

Cursor, Codex and other assistants

What you can ask for

What the assistant can do

Rate limits

When something goes wrong

​Before you start

​Setting up

​Claude Desktop

​GitHub Copilot in VS Code

​Cursor, Codex and other assistants

​What you can ask for

​What the assistant can do

​Rate limits

​When something goes wrong

Before you start

Setting up

Claude Desktop

GitHub Copilot in VS Code

Cursor, Codex and other assistants

What you can ask for

What the assistant can do

Rate limits

When something goes wrong