SkillFoxx

Kaiten connector for Cursor plugin

Kaiten MCP Server — Cursor variant

A plugin and MCP connector for Kaiten built for Cursor: read boards and cards, create tasks and checklists, local stdio with no open ports

  • 0 ★ on the repository
  • Last commit
  • MIT
Plugin

Broad access

Why this level

  • Creates and updates cards and comments on a real board
  • The remote mode, if misconfigured, can expose Kaiten access from outside
All reasons and checks
Russian stack

stillfrozen/kaiten-cursor-connectorAuthor:Stillfrozen

Install

Works in
Services

In your terminal, with SkillFoxx CLI

npx skillfoxx add plugins/kaiten-mcp-server-cursor-variant

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.

  • Creates and updates cards and comments on a real board
  • The remote mode, if misconfigured, can expose Kaiten access from outside

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

What it does

The package bundles a .claude-plugin with a kaiten-cursor-mcp skill and a matching Node.js MCP server. Read tools show boards, board structure, filtered cards (active only by default), a full card with description, comments and checklists, blockers, time logs, external links, sprints and backlog analytics. Write tools create a card, update its fields, add and edit comments, and create a checklist and its items. The recommended mode is local stdio: Cursor launches the built Node.js process and passes the token via environment variables in mcp.json, with no network port. There is also an optional remote mode with full OAuth 2.1, but the author explicitly advises against exposing it to the internet for team use.

Who it is for. For Cursor users on Kaiten who want a local connector with no network port and a ready skill guide.

Good fit when

  • You work in Cursor and want to keep the Kaiten token only in mcp.json with no server
  • You need backlog analytics and a default split between active and archived cards
  • A ready skill with hints on conditions and token storage is useful

Not a fit when

  • You need a server for Claude Code or another client: the README is Cursor-focused, though the MCP protocol itself is universal
  • You need a shared team deployment: the author explicitly advises against the public remote mode for regular use

Example request

Show my Kaiten boards and backlog analytics for board 1390917

Limitations

Requires building from source (npm install, npm run build), no npm package. It is a fork of an earlier Claude-oriented variant mentioned in the README without a link. Single author, no stars. The remote OAuth mode is harder to set up and not recommended by the author for regular use.

How to disable. Remove the kaiten entry from ~/.cursor/mcp.json and delete the skills/kaiten-cursor-mcp folder if the skill was installed.

FAQ

Does the local mode need an open port?

No, Cursor launches the process directly and talks to it over stdin/stdout, with no server or port.

Does it show archived cards?

Not by default, list tools use condition: 1 (active); pass condition: 2 explicitly for the archive.

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

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

MCP serverBroad access33
Russian stack

A remote Kaiten MCP server for Claude with full OAuth 2.1: read-only boards, cards, sprints and backlog analytics

MCP serverExtended access

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

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

README in short

The README recommends the local stdio mode as the main path for a Mac-based team and describes an optional remote Railway deployment with OAuth 2.1, PKCE, a preshared token and an owner password as a second factor. It lists read and write tools, the condition behavior for active versus archived cards, environment variables, and a detailed security section covering CSRF protection, constant-time comparisons and security headers.

README badge

Original SKILL.md

---
title: "Kaiten (Cursor MCP connector)"
tags:
  - проект/workspace
  - подпроект/tools
  - тип/guide
  - область/tech
---
# Kaiten (Cursor MCP connector)

## When to use this skill

- Kaiten boards, cards, sprints, backlog, blockers, comments, acceptance criteria.
- User asks to create, update, or read full content of a card.

Prefer MCP tools when the kaiten server is connected. Do not curl the Kaiten API with KAITEN_TOKEN from the shell.

## Active vs archived (default: active)

- condition: 1 — on the board (active). Default for list-cards, search-cards, get-sprint-cards.
- condition: 2 — archived. Use only when the user asks for archive.
- state (queued / inProgress / done) is separate from condition.

## API token

Put KAITEN_HOST and KAITEN_TOKEN in ~/.cursor/mcp.json → mcpServers.kaiten.env. Never commit. Token needs write access for mutation tools.

Report a problem