mcp-kaiten (Spring AI)
mcp-kaiten
A Kaiten MCP server built on Spring AI with SSE transport, reachable over a local port
- 2 ★ on the repository
- Last commit
- GPL-3.0
Extended access
Why this level
- A Kaiten token with workspace access is passed via environment variables
- The tool set and its permissions are not documented in the README
Install
- Works in
- Services
Manual install
export KAITEN_API_URL="https://YOUR_SPACE.kaiten.ru/api/v1"
export KAITEN_API_TOKEN="<your Kaiten token>"
./mvnw spring-boot:runCommand from the README. Default port is 8080, change it with SERVER_PORT.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- A Kaiten token with workspace access is passed via environment variables
- The tool set and its permissions are not documented in the README
This is third-party code. Review the repository files before installing.
What it does
The server runs a Spring Boot app that talks to Kaiten over REST and exposes tools to an agent through MCP over an SSE endpoint. The Kaiten space URL and API token come from environment variables, and the port can be changed if 8080 is busy. The README walks through a manual smoke test: opening the SSE subscription, sending initialize, confirming readiness and calling tools/list with curl.
Who it is for. For Java and Spring developers who want a Kaiten MCP server in a familiar stack.
Good fit when
- Your project already runs on Spring and you want an MCP server on the same stack
- You need SSE transport instead of stdio
- A basic set of Kaiten tools is enough
Not a fit when
- You need a wide set of Kaiten tools: cards, checklists, tags, time logs
- You don't want to build and run a Java app just for one MCP server
Example request
Connect to the Kaiten MCP server on port 8080 and list the available toolsMCP
- Transport
- sse
- Authentication
- not required
Environment variables
KAITEN_API_URLrequired- Base API URL of your Kaiten space
KAITEN_API_TOKENrequired, secret- Kaiten access token
SERVER_PORT- Server port, defaults to 8080
Limitations
A single-author project with few stars and no releases; the README documents the startup and smoke-test procedure but not a concrete tool list. Requires Java and the Maven wrapper. KAITEN_API_URL and KAITEN_API_TOKEN are mandatory, without them the app refuses to start.
How to disable. Stop the Spring Boot process and remove the server from your MCP client config.
FAQ
What transport does the server use?
SSE: the client subscribes to /mcp/sse and posts JSON-RPC messages to /mcp/message with the sessionId from the subscription.
Discussion
No questions or reviews yet.
Related
All Kaiten toolsAn MCP server for Kaiten with 36 tools: cards, checklists, time tracking and day planning, local or remote with OAuth
MCP server for Kaiten
mcp_server_for_kaiten
A simple Python MCP server for CRUD operations on Kaiten spaces, boards and cards
Kaiten MCP (tyunn)
Kaiten MCP
An MCP server and CLI for Kaiten with per-project settings and access limited to chosen spaces and boards
kaiten-mcp (ViktorOgnev)
kaiten-mcp
An MCP server for Kaiten with 246 tools across 27 modules: cards, Service Desk, automations, audit and charts
kaiten-mcp (Go)
kaiten-mcp
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
A Kaiten MCP server with a full tool set for cards, time logs, boards, comments and checklists, installed with one npx command
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| mcp-kaiten (Spring AI) (this card) | no | not required | 2 | |
| Kaiten MCP Server | no | API key | 33 | with adjustable response detail |
| Kaiten MCP | no | not required | 20 | boards and cards |
| kaiten-mcp (ViktorOgnev) | no | OAuth | 6 | 246 tools and Service Desk |
README in short
The English README covers a quick start via environment variables and mvnw, notes that KAITEN_API_URL and KAITEN_API_TOKEN are mandatory, and gives four curl steps for a manual check: the SSE subscription, initialize, notifications/initialized and calling tools.