Craaft vs Laver MCP
A side-by-side look at the Craaft and Laver MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
CraaftProduct ManagementRead and update your craaft kanban boards: add and move cards, comment, and tick off checklists.45FairAuth: not declaredVerdict: choose Craaft for product management work; 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?
CChoose Craaft when
- You need dedicated capabilities in the Product Management domain.
- You want tools like
list_projects, get_board, get_card.
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 | C Craaft | |
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 45/100 · Fair | 53/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | LAVER_API_KEYLAVER_API_KEY_FILELAVER_API_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 74 | 49 |
| Full listing | View Craaft | View Laver MCP |
Tools & capabilities
Craaft tools 74
list_projectsList all accessible Kanban projectsget_boardGet a board's columns and cards (descriptions omitted)get_cardGet a single card by ID, including descriptionget_card_detailCard plus comments, events, checklist and attachments in one callsearch_cardsCross-project card search (description is a ≤180-char snippet)create_cardCreate a card at the bottom of a column, with optional metadata (assigned to you unless you name someone)update_cardUpdate a card's title, description, column, position, priority, assignee, tags, etc.move_cardMove a card to another column or boarddelete_cardPermanently delete a cardadd_commentAdd a comment to a card (supports @mentions)get_commentsList comments on a cardget_focusGet focus overview: due cards, attention cards, hygiene counters- +62 more on 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.
Craaft
No confirmed install command for Craaft yet — follow the setup steps linked from its listing page rather than a guessed package name.
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
Craaft is categorized under Product Management and uses an install path we have not confirmed yet. Laver MCP belongs to Product Management and uses a local stdio subprocess. Pick Craaft 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. Craaft has no confirmed install command yet — follow its own setup instructions.
Craaft 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 craaft and laver-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Craaft has a quality signal of 45/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Laver MCP has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.