A side-by-side look at the Laver MCP and MCP Linear 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 MCP Linear for product management as a local process. You can also run both side by side in one mcpServers block.
LAVER_API_KEY, LAVER_API_KEY_FILE, LAVER_API_URL.list_workspaces, list_boards, get_board.LINEAR_API_TOKEN, LINEAR_OAUTH_ACCESS_TOKEN.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 53/100 · Good | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | LAVER_API_KEYLAVER_API_KEY_FILELAVER_API_URL | LINEAR_API_TOKENLINEAR_OAUTH_ACCESS_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 147 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 49 | Not listed |
| Full listing | View Laver MCP | View MCP Linear |
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 parsedNo tool names declared yet. Check the project README from the listing page.
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.
{
"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"
}
}
}
}
{
"mcpServers": {
"tacticlaunch-mcp-linear": {
"command": "npx",
"args": [
"-y",
"@tacticlaunch/mcp-linear"
],
"env": {
"LINEAR_API_TOKEN": "YOUR_LINEAR_API_TOKEN_HERE",
"LINEAR_OAUTH_ACCESS_TOKEN": "YOUR_LINEAR_OAUTH_ACCESS_TOKEN_HERE"
}
}
}
}