Laver MCP vs Framedeck MCP
A side-by-side look at the Laver MCP and Framedeck MCP 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 Framedeck 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 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 Framedeck MCP when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
FRAMEDECK_API_KEY. - You want tools like
list_boards, create_board, set_active_board.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 53/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | LAVER_API_KEYLAVER_API_KEY_FILELAVER_API_URL | FRAMEDECK_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 49 | 32 |
| Full listing | View Laver MCP | View Framedeck MCP |
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
Framedeck MCP tools 32
list_boardsList all projects/productions in Framedeckcreate_boardCreate a new project/board in Framedeckset_active_boardSet the active board/production context. Once set, other tools will use this board by default when no board is specified.get_active_boardShow which board/production is currently set as the active context.list_columnsList stages in a board. Uses active board if set and no board specified.list_labelsList all labels/tagscreate_labelCreate a new label/taglist_cardsList cards/frames with optional filters. Uses active board if set and no board specified.create_cardCreate a new card/frame. Uses active board if set, or Idea Pool as fallback for quick idea capture.update_cardUpdate an existing card/framemove_cardMove a card/frame to a different stagedelete_cardPermanently delete a card/frame- +20 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"
}
}
}
}
Framedeck MCP
{
"mcpServers": {
"lukaris-framedeck-mcp": {
"command": "npx",
"args": [
"-y",
"framedeck-mcp"
],
"env": {
"FRAMEDECK_API_KEY": "YOUR_FRAMEDECK_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Laver MCP is categorized under Product Management and uses a local stdio subprocess. Framedeck MCP belongs to Product Management and uses a local stdio subprocess. Pick Laver MCP for product management work and Framedeck 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.
Laver MCP has no declared pricing — check the project's own site. Framedeck MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. 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 lukaris-framedeck-mcp 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. Framedeck MCP has 55/100 (Good) with 2 views, 0 installs and 1 GitHub stars.