Laver MCP vs Planka
A side-by-side look at the Laver MCP and Planka MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Laver MCP for product management work as a local process; choose Planka 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 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.
Choose Planka when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PLANKA_BASE_URL, PLANKA_AGENT_EMAIL, PLANKA_AGENT_PASSWORD. - You want tools like
planka_get_structure, planka_get_board, planka_create_card.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 53/100 · Good | 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 | LAVER_API_KEYLAVER_API_KEY_FILELAVER_API_URL | PLANKA_BASE_URLPLANKA_AGENT_EMAILPLANKA_AGENT_PASSWORD |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 11 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 49 | 15 |
| Full listing | View Laver MCP | View Planka |
Tools & capabilities
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
Planka tools 15
planka_get_structureGet projects, boards, and lists hierarchyplanka_get_boardGet a board with all cards, lists, and labelsplanka_create_cardCreate a card (optionally with tasks)planka_update_cardUpdate card propertiesplanka_move_cardMove card to different list/positionplanka_get_cardGet card details with tasks/commentsplanka_delete_cardDelete a cardplanka_create_tasksAdd tasks (checklist items) to a cardplanka_update_taskUpdate task name or completionplanka_delete_taskDelete a taskplanka_manage_labelsCreate/update/delete board labelsplanka_set_card_labelsAdd/remove labels from a card- +3 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.
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"
}
}
}
}
Planka
{
"mcpServers": {
"planka": {
"command": "npx",
"args": [
"-y",
"@gogogadgetbytes/planka-mcp"
],
"env": {
"PLANKA_BASE_URL": "YOUR_PLANKA_BASE_URL_HERE",
"PLANKA_AGENT_EMAIL": "YOUR_PLANKA_AGENT_EMAIL_HERE",
"PLANKA_AGENT_PASSWORD": "YOUR_PLANKA_AGENT_PASSWORD_HERE"
}
}
}
}
Frequently asked questions
Laver MCP is categorized under Product Management and uses a local stdio subprocess. Planka belongs to Product Management and uses a local stdio subprocess. Pick Laver MCP for product management work and Planka 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.
Laver MCP has no declared pricing — check the project's own site. Planka 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 laver-mcp and planka as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Laver MCP has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Planka has 53/100 (Good) with 0 views, 0 installs and 11 GitHub stars.