kaiten-connector

Kaiten MCP Server — Cursor variant

Remote MCP server that connects Cursor (the Mac IDE) to Kaiten project management. Deploy your own instance, add it to ~/.cursor/mcp.json, and work with your boards, cards, sprints, and backlog directly from Cursor's chat.

Русская пошаговая установка (stdio, рекомендуется): docs/INSTALL.ru.md

Forked from the Claude variant. This Cursor build adds full card read/write for local stdio use. Optional remote deploy (Railway) still supports OAuth 2.1 + DCR.

What you can do

Read

Tool	Description
list-boards	List all spaces and boards, optionally filter by name
get-board	Board structure: columns, subcolumns, lanes (with IDs for create-card)
list-cards	List cards with filters; defaults to active only (condition=1)
search-cards	Text search across boards; defaults to active cards
get-card	Full card: description, comments, checklists/AC text, members, properties, files, time logs
get-card-comments	Comments only
get-card-blockers	Blocker details
get-card-time-logs	Time logs with comment text
get-card-external-links	External links with descriptions
list-sprints	Sprints
get-sprint-cards	Cards in a sprint
get-current-user	Current user id + role
backlog-analytics	Board analytics (active cards)

Write

Tool	Description
create-card	Create card (title, board_id, column_id; auto lane_id if omitted)
update-card	Patch card fields (title, description, column, state, archive, tags, members, …)
create-card-comment	Add comment
update-card-comment	Edit comment
create-checklist	New checklist on card
add-checklist-item	Add AC / checklist line
update-checklist-item	Edit item text or checked state

Active vs archived

list-cards, search-cards, and get-sprint-cards default to condition: 1 (on the board). Pass condition: 2 for archived cards only.

Local use and secrets

• Recommended: stdio mode — Cursor runs dist/stdio-entry.js; put KAITEN_HOST and KAITEN_TOKEN in ~/.cursor/mcp.json env only (never commit).
• API token needs write permission in Kaiten if you use mutation tools.
• Card text is returned as stored in Kaiten (no scrub layer).

Quick start

Local stdio mode (recommended for personal use)

The simplest way to run the connector — no server, no OAuth, no open port. Cursor launches the Node.js process directly, passes your credentials via env vars, and talks to it over stdin/stdout.

1. Build

cd kaiten-cursor-connector
npm install
npm run build

2. Get your Kaiten API token

Kaiten profile > Settings > API keys > create a new token.

Your Kaiten host is the full domain from your browser URL bar, e.g. mycompany.kaiten.ru.

3. Add to ~/.cursor/mcp.json

Where the API key lives: the env block inside ~/.cursor/mcp.json is the right place. It stays on your machine, is never committed to git, and Cursor passes it to the process automatically on every start. Do not hardcode it in the project's .env file.

{
  "mcpServers": {
    "kaiten": {
      "command": "node",
      "args": ["/absolute/path/to/kaiten-cursor-connector/dist/stdio-entry.js"],
      "env": {
        "KAITEN_HOST": "mycompany.kaiten.ru",
        "KAITEN_TOKEN": "your-kaiten-api-token"
      }
    }
  }
}

Reload Cursor. Open Settings → MCP — the kaiten server should show a green dot. No browser consent page, no passwords.

You can then ask things like:

• "Show my Kaiten boards"
• "What cards are in sprint 45230?"
• "Backlog analytics for board 1390917"
• "Time logs for card 62693325"

---

Remote / team deployment (Railway)

1. Get your Kaiten API token

Kaiten profile > Settings > API keys > create a new token. Your Kaiten host is the full domain from your browser URL bar, e.g. mycompany.kaiten.ru.

2. Deploy to Railway

1. Create a new project on railway.app > Deploy from GitHub Repo
2. Connect this repo (fork it first if needed)
3. Go to the service > Variables tab > add via Raw Editor:

KAITEN_HOST=mycompany.kaiten.ru
KAITEN_TOKEN=your-kaiten-api-token
MCP_PRESHARED_TOKEN=<openssl rand -hex 32>
OWNER_PASSWORD=<openssl rand -base64 24>
PORT=3000