Laver MCP vs OverlayQA MCP
A side-by-side look at the Laver MCP and OverlayQA 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 OverlayQA 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 OverlayQA MCP when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- You want tools like
scan_accessibility, scan_contrast, audit_tokens.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 53/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Free |
| Required env vars | LAVER_API_KEYLAVER_API_KEY_FILELAVER_API_URL | None listed |
| 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 | 49 | 15 |
| Full listing | View Laver MCP | View OverlayQA 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
OverlayQA MCP tools 15
scan_accessibilityRun a WCAG audit (axe-core) on any URL. Returns violations with severity, WCAG success criteria, and an overall score.scan_contrastCheck color-contrast ratios across a page. Returns the failing foreground/background element pairs.audit_tokensAudit a live URL's design-system tokens. Returns a 0-100 token-health score and findings (inconsistent font sizes, text colors, spacing, font families, border radii) with severity. Audits the live page only.scan_and_create_issuesScan a URL and auto-create an issue for every violation above a severity threshold.create_issueFile a QA issue with title, severity, type, description and optional assignee.list_issuesPage through issues filtered by status, severity, type, labels, assignee, creator, page, creation time, or active/finished/ignored state. Each issue says who filed it and whether it still needs a reply.update_issueEdit supplied issue fields, assignment, ignored state or status. Takes a UUID or display id such as OQ-12.create_projectCreate a project for a site URL.list_projectsList all projects on your team.list_labelsRead the workspace label library, assigned labels, and your permissions.create_labelCreate a reusable workspace label.set_issue_labelApply or remove one label without changing issue text or other labels.- +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"
}
}
}
}
OverlayQA MCP
{
"mcpServers": {
"overlayqa-mcp": {
"command": "npx",
"args": [
"@overlayqa/mcp@latest"
]
}
}
}
Frequently asked questions
Laver MCP is categorized under Product Management and uses a local stdio subprocess. OverlayQA MCP belongs to Product Management and uses a local stdio subprocess. Pick Laver MCP for product management work and OverlayQA 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. OverlayQA MCP is listed as free. 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 overlayqa-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. OverlayQA MCP has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.
