Kaiten vs Laver MCP
A side-by-side look at the Kaiten and Laver MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Kaiten for product management work as a local process; choose Laver MCP for product management as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Kaiten when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
KAITEN_API_TOKEN, KAITEN_WORKSPACE_SLUG, KAITEN_BASE_URL.
Choose Laver MCP when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
LAVER_API_KEY, LAVER_API_KEY_FILE, LAVER_API_URL. - You want tools like
list_workspaces, list_boards, get_board.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 36/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | KAITEN_API_TOKENKAITEN_WORKSPACE_SLUGKAITEN_BASE_URL | LAVER_API_KEYLAVER_API_KEY_FILELAVER_API_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 49 |
| Full listing | View Kaiten | View Laver MCP |
Tools & capabilities
Kaiten tools
No tool names declared yet. Check the project README from the listing page.
Laver MCP tools 49
list_workspacesWhere to start when you have no uuidslist_boardsThe boards in a workspaceget_boardA board with its status columns, labels, members and ticketslist_ticketsTickets on a board, filterable, paged — `updated_since` is how you follow a boardlist_workspace_ticketsTriage across every board at once — `overdue`, `unassigned`, or free textget_ticketOne ticket in full, its subtasks, **including its `version`get_ticket_commentsComments and activity historyget_ticket_flowHow long the ticket has spent in each columnlist_custom_fieldsA board's custom field definitions — the uuids `update_ticket` writes againstlist_labelsEvery label in the workspace, not only the ones already used on one boardsearchBoards, tickets, wiki pages and comments across a whole workspace at oncecreate_ticketstatus` takes the column name, or pass `status_uuid`; markdown in `description` is parsed- +37 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Kaiten
{
"mcpServers": {
"kaiten": {
"command": "uvx",
"args": [
"kaiten-mcp"
],
"env": {
"KAITEN_API_TOKEN": "YOUR_KAITEN_API_TOKEN_HERE",
"KAITEN_WORKSPACE_SLUG": "YOUR_KAITEN_WORKSPACE_SLUG_HERE",
"KAITEN_BASE_URL": "YOUR_KAITEN_BASE_URL_HERE"
}
}
}
}
Laver MCP
{
"mcpServers": {
"laver-mcp": {
"command": "npx",
"args": [
"-y",
"@laver/mcp"
],
"env": {
"LAVER_API_KEY": "YOUR_LAVER_API_KEY_HERE",
"LAVER_API_KEY_FILE": "YOUR_LAVER_API_KEY_FILE_HERE",
"LAVER_API_URL": "YOUR_LAVER_API_URL_HERE"
}
}
}
}
Frequently asked questions
Kaiten is categorized under Product Management and uses a local stdio subprocess. Laver MCP belongs to Product Management and uses a local stdio subprocess. Pick Kaiten for product management work and Laver MCP for product management.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Kaiten has no declared pricing — check the project's own site. Laver MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add kaiten and laver-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Kaiten has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Laver MCP has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.