laver-mcp

Purpose

Laver MCP Server provides AI agents with tools to read and operate boards, tickets, and workspace Wiki in Laver (laver.app). It connects to the same public REST API as the web app, and each tool is a thin call to the API; the server itself has no local state, no cache, and no second implementation.

Main capabilities

Tickets and boards

• list_workspace_tickets is a standup-style read: no board_uuidrequired, it can answer "what is overdue" and "what has no assignee," defaults to 50 per page and up to 200, with no cursor.
• get_ticket_flow derives data from move records in ticket history;gaps points out cases where the history and current column are inconsistent.
• You can pass the list_tickets returned last time as server_time to updated_since to track board changes.
• Board structure tools include get_board(can pass include_tasks: false to narrow the return) and two reorder tools; reordering requires the complete list.
• Tags are workspace-level shared objects, and renaming affects all boards; the uuid it returns can be used as the update_ticket for label_uuids.

Comments, attachments, and subtasks

• Comment writes are not version-controlled; later writes overwrite earlier ones; only the author can edit or delete, and other people's comments appear as the same 404 as nonexistent ones.
• mark_comments_read is the only call that marks as read, marking up to the latest comment that existed at the time.
• For attachments,get_ticket reports attachment_total; binary content does not cross tool boundaries, only text, CSV, and images smaller than 4 MB are returned inline, and the rest requires save_to to write to a path on the machine running the server; uploads are read from that machine via file_path . Images are returned as MCP image blocks.

Wiki

• The toolset includes list_wikis、search_wiki、get_wiki_tree、get_wiki_page、get_wiki_page_version、append_wiki_page、update_wiki_page、create_wiki_page and restore_wiki.
• After archiving a Wiki, it and all its subpages disappear from list_wikis ; passing archived: true allows viewing;restore_wiki can unarchive an entire Wiki at once.
• append_wiki_page appends to the end of the page without taking a version, and if two agents append at the same time both can preserve their text;update_wiki_page replaces the page content and requires getting the version from get_wiki_page , and if someone else writes in the meantime it returns 409 and the current version.
• There is no tool to delete a page.

Automation rules

• Rules consist of triggers, optional conditions, and up to twenty actions, and are stored on the board.
• Rules created through tools take effect immediately; a rule is a long-term authorization that runs under the identity of the key's corresponding user, and revoking the key does not stop the rule; only disabling or deleting the rule does.
• update_automation passing enabled: false can immediately stop an abnormal rule while preserving history; deleting destroys the history as well.

Public links

• list_published_links lists what the workspace currently has publicly exposed on the internet, including share tokens, publishers, times, and visitor counts. It is available only to workspace owners or admins; regular members get 403. There is no tool to take a link offline.

Usage

Create a workspace-scoped API key in Laver's Admin → API keys. The key acts as its creator, cannot exceed the creator's permissions, and can be revoked without affecting their account. The environment variable LAVER_API_URL can override the API host; the default https://api.laver.app；LAVER_API_KEY_FILE is a replacement for LAVER_API_KEY , pointing to a file containing only the key or containing LAVER_API_KEY=… line's .env style file.LAVER_API_URL must be https (except localhost). The repository root's .mcp.json has this server registered, reading the secret from the gitignored .env . It runs the published package npx -y @laver/mcp. When editing, if it points to the working copy, it must be changed back before committing. The client only connects to the MCP server at startup; executing claude mcp add during runtime will not retroactively inject tools; a new session or reconnection is required.

Applicable Scenarios

Suitable for teams that want AI agents to participate in the Laver project management process, such as reading tickets needed for stand-ups, tracking changes by kanban, reading and appending to the team Wiki, viewing the list of public links, etc.

Limitations

• Not yet provided: notifications (limited by the backend plugin session_only , secret access returns 401), separately listing subtasks, kanban templates, attachment thumbnails, recent locations, kanban analytics, Wiki pages associated with kanban, command scoreboard, manual automation trigger button, ticket history and copy/loop, Sprint (blocked at the same place as notifications).
• Comments are not version-controlled; later writes overwrite earlier ones.
• Attachments are only inlined for text, CSV, and images smaller than 4 MB; the rest must be written to a file path.
• No tools for deleting Wiki pages, taking public links offline, or restoring Wiki historical versions.