SkillFoxx

Kaiten MCP: 51 tools for cards

kaiten-mcp

A local Node.js 24 stdio server for finding and editing Kaiten cards, checklists, comments and custom fields from Codex and Claude Code

  • 0 ★ on the repository
  • Last commit
  • MIT
MCP server

Broad access

Why this level

  • Can delete and archive cards, changes apply immediately
  • The token gives user-level rights across the whole Kaiten company
All reasons and checks
Russian stack

2chevskii/kaiten-mcpAuthor:2chevskii

Install

Services

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/2chevskii-kaiten-mcp

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Can delete and archive cards, changes apply immediately
  • The token gives user-level rights across the whole Kaiten company

This is third-party code. Review the repository files before installing.

What it does

The server connects an agent to a Kaiten company with an API token and exposes 51 tools with the `kaiten_` prefix. The agent finds cards by owner, member, responsible user, deadline, tag and state and reads descriptions, comments, checklists, external links and parent references. The same tools create, edit, move, archive, restore and delete cards, manage comments, members, tags and links, build checklists and attach child cards. Custom fields are first looked up by name together with their options and directory records, then values are written to the card. It runs over stdio only: the client launches the process through `npx`. One configuration entry serves one company.

Who it is for. Teams on cloud or on-premise Kaiten who want to run cards from an agent chat, including sprint boards and support queues.

Good fit when

  • In the morning you need overdue cards of one assignee on the support board and the reason each is blocked
  • Before a retro you want a card read together with its comments and checklists and summarized
  • A release card has to be created with a ready checklist for testing, docs and rollout
  • A task is split into subtasks by linking existing cards as children of the parent

Not a fit when

  • You need Kaiten documents, attachments, time tracking or webhooks: this server does not cover them
  • You need to edit custom-field definitions or directories: you can only assign values
  • The agent host runs a Node.js older than 24: the server will not start there

Example request

Find my overdue cards on the Support board and show what blocks them

MCP

Transport
stdio
Authentication
API key

Environment variables

KAITEN_ORIGIN required
Company origin such as https://company.kaiten.ru without an API path
KAITEN_TOKEN required, secret
Kaiten API token used for all requests
KAITEN_TIMEOUT_MS
Timeout per operation in milliseconds, default 30000

Limitations

It needs Node.js 24 or newer and `npx` on the client PATH. Tools apply changes at once with the token owner permissions and there are no automatic retries: after a write timeout the author advises opening the card to confirm the edit did not land before repeating it. Documents, attachments, time tracking, automations, administration and webhooks are out of scope. Field definitions and directories are read only. One configuration entry is tied to one company, so several companies need separate entries with distinct names. The project is young and has no stars yet.

How to disable. Remove the server with `claude mcp remove kaiten` or `codex mcp remove kaiten` and revoke the token in your Kaiten profile.

FAQ

How many tools does the server expose?

Fifty-one, all with the `kaiten_` prefix. After connecting, the client should list them, which doubles as a connection check.

Which environment variables are required?

`KAITEN_ORIGIN` with the company address without an API path and `KAITEN_TOKEN` are required. The optional `KAITEN_TIMEOUT_MS` sets the operation timeout, 30000 ms by default.

Can two companies be connected?

Yes, add two entries with different names, each with its own token and its own `KAITEN_ORIGIN`.

Does it work with Claude Desktop?

Any client that launches a local stdio process works. The README has ready commands for Codex and Claude Code, and configuration file examples are in the setup guide.

What if the server does not connect?

Check the Node.js version and `npx` availability on the client PATH first, then open the troubleshooting section of the documentation.

Discussion

No questions or reviews yet.

All Kaiten tools
Russian stack

An MCP server for Kaiten: cards, comments, spaces and boards with control over response verbosity

MCP serverBroad access33

Kaiten MCP

kaiten-mcp

Russian stack

Swift MCP server for Kaiten: spaces, boards, columns, lanes, cards, comments and custom properties

MCP serverBroad access20
Russian stack

An MCP server for Kaiten with 36 tools: cards, checklists, time tracking and day planning, local or remote with OAuth

MCP serverBroad access1
Russian stack

A Kaiten MCP server with a full tool set for cards, time logs, boards, comments and checklists, installed with one npx command

MCP serverExtended access
Russian stack

A single-file FastMCP server for Kaiten: 22 tools for cards, comments, checklists and time tracking

MCP serverBroad access1

README in short

The README describes 51 tools by task: card search, context, editing, checklists, custom fields. It then gives install commands for Codex and Claude Code, a connection check, sample requests, a variable table, a warning that changes apply at once and a list of what is not covered. A separate two-language docs site has a tool reference and a workflow guide.

README badge

Report a problem