SkillFoxx

kaiten-mcp

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

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

Broad access

Why this level

  • Tools create, move, archive and delete cards in a live Kaiten workspace
  • The remote mode encrypts and stores teammates' personal tokens on a third-party Vercel deployment
All reasons and checks
Russian stack

aimuzov/kaiten-mcpAuthor:Aleksey Imuzov

Install

Services

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/aimuzov-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.

  • Tools create, move, archive and delete cards in a live Kaiten workspace
  • The remote mode encrypts and stores teammates' personal tokens on a third-party Vercel deployment

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

What it does

The project is a monorepo with a shared core and two connection modes. The local stdio server installs as the kaiten-mcp npm package and gives an agent 36 kaiten_* tools: spaces, boards, cards with full CRUD, comments, checklists, tags, members, time tracking and flexible card search. It includes ready day-planning tools: today's tasks, overdue cards and a one-call day plan. If the token is not set in advance, the server asks for it via the MCP elicitation mechanism on the first Kaiten call. The second mode, a Next.js app in apps/web, deploys to Vercel and becomes a remote server with OAuth 2.1 and PKCE: each teammate connects via a shared URL and enters their own Kaiten token, which is encrypted with JWE.

Who it is for. For Kaiten teams who want a full set of card management tools and convenient team access without handing out tokens in config files.

Good fit when

  • You need full card operations: creating, moving, checklists, time logs, tags and members
  • You want a ready day plan built from overdue and current tasks
  • You need a team-wide remote connection without a shared token in a config file

Not a fit when

  • You only need simple read operations with no writes
  • You cannot deploy the Next.js app to Vercel for the remote mode

Example request

Build me a plan for today: what is overdue and what needs to happen first

MCP

Transport
stdio, http
Authentication
key is optional

Environment variables

KAITEN_API_URL
Kaiten API base URL, e.g. https://domain.kaiten.ru/api/latest
KAITEN_API_TOKEN secret
Personal Kaiten API token; if unset, the server asks for it on first call
AUTH_SECRET secret
OAuth token encryption key for the remote Vercel mode

Limitations

0 stars, a single author. The remote mode requires deploying to Vercel and setting AUTH_SECRET to encrypt tokens; without it OAuth connections are impossible. In local mode without preset environment variables the token is requested interactively, but only if the client supports elicitation.

How to disable. Remove the kaiten-mcp server from your MCP client config; for the remote mode also remove the connector in Claude Desktop and stop the Vercel deployment.

FAQ

Do I need to put the token in the config beforehand?

No, if the client supports elicitation the server asks for the token on first Kaiten call and never writes it to disk.

Why is the remote mode better for a team?

Each teammate enters their own Kaiten token via OAuth 2.1 instead of reusing one shared token from a config.

Discussion

No questions or reviews yet.

All Kaiten tools
Russian stack

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

MCP serverBroad access
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

An MCP server for Kaiten with 246 tools across 27 modules: cards, Service Desk, automations, audit and charts

MCP serverBroad access6
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 and CLI for Kaiten with per-project settings and access limited to chosen spaces and boards

MCP serverExtended access

Comparison with similar tools

Cards that share the main search query, and how they differ.

ToolOfficialAuthenticationRepository starsMain difference
kaiten-mcp (this card)nokey is optional1
Kaiten MCP ServernoAPI key33with adjustable response detail
Kaiten MCPnonot required20boards and cards
kaiten-mcp (ViktorOgnev)noOAuth6246 tools and Service Desk

README in short

The bilingual README describes two usage modes: a local stdio server from npm and a remote Vercel server with OAuth 2.1 and PKCE. It lists a table of 36 tools by group, all environment variables, interactive token requests via elicitation, connection instructions for Cowork, Claude Code and Claude Desktop, and the three-package monorepo architecture. MIT licensed.

README badge

Report a problem