mcp-kaiten (Spring AI)
mcp-kaiten
A Kaiten MCP server built on Spring AI with SSE transport, reachable over a local port
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
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
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.
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 toolsLimitations
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.
MCP
- Transport
- sse
- Authentication
- not required
| Environment variables | |
|---|---|
| KAITEN_API_URL required | Base API URL of your Kaiten space |
| KAITEN_API_TOKEN required, secret | Kaiten access token |
| SERVER_PORT | Server port, defaults to 8080 |
Security check
- A Kaiten token with workspace access is passed via environment variables
- The tool set and its permissions are not documented in the README
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.
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.
Related
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Skills for real engineers by Matt Pocock
Skills For Real Engineers
Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Reference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything