Laver MCP

What laver-mcp MCP server does

The laver-mcp MCP server exposes Laver workspaces through MCP tools. Agents can discover workspaces and boards, inspect board structure, list or search tickets, read comments and activity, and search across boards, tickets, wiki pages, and comments. Ticket data includes subtasks and a version value that is needed for certain writes.

Writing tools cover ticket creation and updates, column changes, comments, subtasks, archiving, deletion, ticket relationships, and board status management. Agents can create boards from the crm or sales-leads templates, add or reorder columns, and link tickets with blocking relationships. Wiki content is available through the workspace search and wiki-tree operations described in the project documentation.

How it works

Each tool call is forwarded to the same public REST API used by the Laver web application. The process keeps no local state and does not maintain a cache. API errors, including conflicts, are returned from Laver so an agent can re-read current data and retry when appropriate.

For incremental board monitoring, call list_tickets with updated_since set to the previous response's server_time. Workspace-wide triage is available through list_workspace_tickets, which can filter for overdue or unassigned tickets and supports free-text filtering. Results can be narrowed with options such as include_tasks: false, include_descriptions: false, status, limits, wiki depth, or a parent page UUID to reduce context usage.

Ticket updates and moves require the current ticket version. Custom fields are addressed by field UUID, and an update replaces the complete custom-field object. Status reordering requires the full current UUID list; stale data can produce a 409. Comments do not require a version, while comment editing and deletion are limited to the API key owner's comments.

Setup and configuration

Create a workspace-scoped API key in Laver under Admin → API keys. The key acts with the permissions of the person who created it. Run the published package with a standard MCP stdio configuration:

{
  "mcpServers": {
    "laver": {
      "command": "npx",
      "args": ["-y", "@laver/mcp"],
      "env": { "LAVER_API_KEY": "your key here" }
    }
  }
}

LAVER_API_KEY supplies the credential. LAVER_API_KEY_FILE can instead point to a file containing the key or to a .env-style file with a LAVER_API_KEY assignment. LAVER_API_URL changes the API host and defaults to https://api.laver.app; it must use HTTPS unless the host is localhost.

Clients load MCP tools when they start. After adding the server, start a new session or reconnect the client's MCP connection before expecting the tools to appear.

Tools and capabilities

• Discover workspaces, boards, statuses, labels, members, custom fields, tickets, comments, and ticket flow.
• Search workspace boards, tickets, wiki pages, and comments.
• Create, update, move, archive, and permanently delete tickets.
• Add, edit, reorder, and remove subtasks.
• Post, edit, delete, and mark comments as read.
• Create boards, manage status columns, and link or unlink tickets.
• Follow board changes with updated_since and triage overdue or unassigned work.

Limitations and notes

Archived tickets remain recoverable for 30 days, but deleting a ticket from the trash is permanent. Deleted subtasks cannot be recovered. A status cannot be deleted unless it is empty, and each board must retain one status column. Unlinking a ticket pair removes every link type between them.

list_workspace_tickets is limited to one page, with 50 results by default and 200 at most. Ticket-flow totals can be affected by overlapping work, and gaps indicate disagreement between recorded history and the current column. There is no MCP tool for Laver's server-sent event stream; following changes requires another tool call.