SkillFoxx

Kaiten MCP Tools: read cards and attachments, 37 tools

kaiten-mcp-tools

A read-only npm package with 37 tools for cards, boards, documents and time tracking that downloads original attachments for the agent to analyze

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

Minimal access

Why this level

  • Read only, but downloaded attachments stay on disk after exit
  • The token exposes company cards, documents and files to the agent
All reasons and checks
Russian stack

vitalysolovyovdev/kaiten-mcp-toolsAuthor:VitalySolovyovDev

Install

Services

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/kaiten-mcp-tools

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

Other ways to install

Access and checks

How we review

Minimal accessThe tool runs nothing and makes no network calls.

  • Read only, but downloaded attachments stay on disk after exit
  • The token exposes company cards, documents and files to the agent

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

What it does

The TypeScript server reads Kaiten through `GET` and never creates, changes or deletes data. It has 37 separate tools: cards by `card_id` or any link form, spaces and boards, discussions, documents, directories, sprints and time tracking. What sets it apart is file handling: original attachments are downloaded to `KAITEN_DOWNLOAD_DIR` under safe unique names and the agent analyzes them itself, whether a screenshot, a table or a PDF. The token comes from `KAITEN_API_TOKEN` or a `KAITEN_API_TOKEN_FILE`, which keeps the secret out of the client config. Directories are cached for a minute while cards are always read fresh. The transport is `stdio` and the package ships to npm with `npm-shrinkwrap.json`.

Who it is for. Analysts and tech leads who need an agent to work through tasks together with screenshots and attachment files without any edit rights.

Good fit when

  • A bug is described by a screenshot in a card and the agent must see the file itself, not just its name
  • A card link from chat turns into a request: the server accepts `/id`, `/c/id` and board URLs
  • The token secret must stay out of the client config and lives in a separate file
  • Kaiten sits behind a corporate certificate authority and TLS checks must stay on

Not a fit when

  • The agent has to create and move cards: the server cannot
  • Attachment files must not touch the work machine disk: originals stay in the directory after exit
  • You need an HTTP transport: only `stdio` is available

Example request

Open the card from this link, download the screenshot from its attachments and say which error it shows

MCP

Transport
stdio
Authentication
key is optional

Environment variables

KAITEN_BASE_URL required
Full address of the Kaiten instance
KAITEN_API_TOKEN secret
API token, or a token file instead
KAITEN_API_TOKEN_FILE
Path to the token file
KAITEN_DOWNLOAD_DIR
Directory for downloaded original attachments

Limitations

The server is read only and cannot edit Kaiten. It needs Node.js 22.15 or newer. Downloaded attachments stay in `KAITEN_DOWNLOAD_DIR` after the server exits and the user or the system cleans them up. One process serves one Kaiten instance and one token source. Private file hosts must be allowed explicitly through `KAITEN_ATTACHMENT_ALLOWED_HOSTS` and the token is not sent there. The original size is capped at 20 MiB by default. There are no stars and the version is 0.2.0.

How to disable. Remove the server from the client configuration, revoke the token in your Kaiten profile and clear `KAITEN_DOWNLOAD_DIR`.

FAQ

How do I connect it?

Add `npx -y kaiten-mcp-tools@0.2.0` to the client config with `KAITEN_BASE_URL` and either `KAITEN_API_TOKEN` or `KAITEN_API_TOKEN_FILE`. The README has examples for Claude Desktop, Cursor and Codex.

How do I check the connection?

Ask the agent to call `get_current_user`, then `get_card` with a link. The `--help` and `--version` commands work without a token.

What about a corporate certificate?

Set `NODE_EXTRA_CA_CERTS` to a PEM file path before Node.js starts. TLS verification stays on.

Does the server cache data?

Directories and structural metadata are cached for 60 seconds and `KAITEN_CACHE_TTL_MS=0` turns the cache off. Cards, comments, sprints, time and files are read fresh.

What happens on 429 and network failures?

Transient network errors, 429 and some 5xx responses are retried automatically and other errors are returned to the agent.

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 Go binary with no writes: 23 read tools for Kaiten, every request is a GET, wired into Codex, Claude Code and Claude Desktop

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

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: cards, comments, spaces and boards with control over response verbosity

MCP serverBroad access33
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 document walks through a first run: Node.js, a token in the profile, ready configs for Claude Desktop, Cursor and Codex and a check with `get_current_user` and `get_card`. Then come the environment settings with limits and the list of 37 tools with the rule to pass exactly one of `url` or `card_id`. An English version, README.en.md, is included.

README badge

Report a problem