SkillFoxx

Read-only Kaiten MCP: 23 tools

kaiten-mcp

A Go binary with no writes: 23 read tools for Kaiten, every request is a GET, wired into Codex, Claude Code and Claude Desktop

  • 0 ★ on the repository
  • Last commit
MCP server

Minimal access

Why this level

  • Read only: every request to Kaiten is a GET
  • The token still exposes card and discussion contents to the agent
All reasons and checks
Russian stack

octavianaugust1/kaiten-mcpAuthor:OctavianAugust1

Install

Services

Manual install

curl -fsSL https://raw.githubusercontent.com/OctavianAugust1/kaiten-mcp/main/scripts/install.sh | sh

The README installer puts the binary in place and registers the server in Codex and Claude Code.

Access and checks

How we review

Minimal accessThe tool runs nothing and makes no network calls.

  • Read only: every request to Kaiten is a GET
  • The token still exposes card and discussion contents to the agent

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

What it does

The Go server reads Kaiten data through the API and gives the agent 23 tools. Every call to Kaiten is a `GET`, so it physically cannot create, change, move, archive or upload anything: each tool carries `readOnlyHint` and `idempotentHint` and API methods and paths are fixed in code. It talks to the client over `stdio`, opens no network ports and writes diagnostics to stderr. The API address and token come from environment variables or a `.env` file, and page size and request timeout are configurable. The installer for Linux and macOS downloads a prebuilt binary, verifies its checksum and registers the server in Codex and Claude Code by itself.

Who it is for. Managers and analysts who want an agent to read Kaiten tasks while any edit stays impossible, for example during a board audit.

Good fit when

  • A board status report is needed and the agent must not be given edit rights
  • A team is trying an agent for the first time and lets it into the live Kaiten in a safe mode
  • Before planning you need to find cards with a given tag and read their discussions
  • The token goes to an outside contractor and writes must be impossible even by accident

Not a fit when

  • The agent has to create, move and close cards: use a server with write tools
  • You work on Windows: the installer targets Linux and macOS and only a source build remains
  • You want a ready npm package: distribution is a binary and a script

Example request

Show all cards on the Releases board due this week and read the discussion on each

MCP

Transport
stdio
Authentication
API key

Environment variables

KAITEN_BASE_URL required
HTTPS address of the Kaiten API, for example https://example.kaiten.ru/api/v1
KAITEN_TOKEN required, secret
Kaiten bearer token
KAITEN_REQUEST_TIMEOUT
Per-attempt timeout, default 30s
KAITEN_DEFAULT_PAGE_LIMIT
Page size from 1 to 100, default 50

Limitations

The server can only read: any edit needs another tool. The installer is fetched with `curl` from the repository site and runs on Linux and macOS, `amd64` or `arm64`. It pulls a prebuilt binary from a GitHub Release, and the README itself notes this works after the first release is published, otherwise you build with Go 1.26 or newer. No license is stated in the repository. There are no stars, one author, and for Codex the author advises keeping the Kaiten variables in `~/.bashrc` above the block that exits a non-interactive shell.

How to disable. Run `claude mcp remove kaiten` or `codex mcp remove kaiten` and delete the binary `~/.local/bin/kaiten-mcp`.

FAQ

Can the server change anything in Kaiten?

No. Every request is a `GET` and each tool declares `readOnlyHint: true` and `destructiveHint: false`.

How do I set the Kaiten address?

With `KAITEN_BASE_URL` holding an HTTPS API address such as `https://example.kaiten.ru/api/v1`, with no query parameters or credentials in the string.

How do Codex and Claude Code differ on install?

The installer adds a `kaiten` server to both clients when it finds `codex` or `claude` and leaves an existing entry of the same name alone. Set `KAITEN_MCP_REGISTER_CLIENTS=0` to skip automatic registration.

Can I build it myself?

Yes, with Go 1.26 or newer: `go build -o kaiten-mcp ./cmd/kaiten-mcp`, then point the client at that binary.

How many items does one request return?

Page size is set by `KAITEN_DEFAULT_PAGE_LIMIT`, from 1 to 100, 50 by default.

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 native Go CLI and MCP server for Kaiten with safe defaults: write tools are off until explicitly enabled

MCP serverBroad access

kaiten-mcp (Go)

kaiten-mcp

Russian stack

A Go MCP server for Kaiten with readonly and full access profiles, where the tool set is set by config instead of one blanket key

MCP serverExtended 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

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

MCP serverExtended access

README in short

The documentation starts with installation: a prebuilt binary in one command or a source build. Then comes a variable table, setup for Codex CLI, Claude Code and Claude Desktop and a description of all read tools with their declared safety hints. It also states the rule for `stdout`: nothing but protocol messages may be written there.

README badge

Report a problem