Introduction
Businessmap now provides native MCP (Model Context Protocol) support, enabling seamless integrations with AI tools such as Cursor, Claude Desktop, Claude Code CLI and others.
This new capability gives teams a unified and structured way to interact with Businessmap through AI agents, automations, and external systems that rely on MCP.
Customers have been increasingly requesting AI interoperability, and the new MCP server lays the groundwork for deeper native integrations—both customer-driven and internally built.
What Is the Businessmap MCP Server?
The Businessmap MCP Server exposes a standardized interface for external AI tools, enabling them to read, search, create, and update work items (cards) in a safe and structured way.
Important: For security and privacy, Businessmap does not share or transfer any data to third-party AI services (such as Azure OpenAI by Microsoft) when clients use the MCP Server.
It allows AI systems to:
Retrieve card information
Manage cards (create, update, move)
Work with subtasks
Manage comments
Interpret complex prompts that combine multiple steps (e.g., “Create a card, add a comment, then move it to In Progress.”)
Note: As of V12.04, Businessmap supports a second MCP Server which covers the Docs functionality.
Supported Functional Areas (businessmap-cards)
The MCP server organizes functionality into four major categories:
1. Card Information
| Method | Description |
|---|---|
| get_card_details | Returns full details for a specific card (title, description, custom fields, etc.). |
| get_card_comments | Retrieves all comments associated with a card. |
| get_card_flow_history | Shows the card’s movement across boards/workflows/columns with timing details. |
| get_card_blocked_times | Shows full blocking history, including when and where blocks occurred. |
| get_card_change_history | Chronological history of all edits made to the card. |
| get_card_logged_time | Time logged on the card and its subtasks. |
| get_card_children_hierarchy | Retrieves the hierarchical structure of the card’s children. |
| get_card_links | Lists all card links: parents, children, relatives, predecessors, successors. |
2. Card Management
| Method | Description |
|---|---|
| search_cards | Search for cards based on multiple criteria (see full list below). |
| create_card | Creates a new card with specified details. |
| update_card_details | Updates fields of an existing card. |
| move_card | Moves a card to a different column, workflow, or board. |
3. Subtasks
| Method | Description |
|---|---|
| get_card_subtasks | Retrieves all subtasks for a card. |
| add_card_subtask | Adds a new subtask. |
| update_subtask | Updates an existing subtask. |
| delete_card_subtask | Removes a subtask from a card. |
4. Comments
| Method | Description |
|---|---|
| add_card_comment | Adds a comment to a card. |
| update_card_comment | Edits an existing comment. |
| delete_card_comment | Deletes a comment. |
Card Search Criteria
The search_cards method supports advanced filtering across multiple categories:
Location & Structure
board_names
workflow_names
column_names
lane_names
Text Search
title
description
custom_id
People
owner_usernames
Time Filters
created_at_from / to
deadline_from / to
Card Characteristics
priority_names (Critical, High, Average, Low)
size_min / size_max
is_blocked
type_names
Metadata
tag_names
sticker_names
Examples:
“Show all critical cards in Board X.”
“Find cards with deadlines this month.”
“Show all blocked cards assigned to John.”
“Search for cards tagged Urgent in In Progress.”
“Find all cards sized 5–10 in the Development workflow.”
Supported Functional Areas (businessmap-docs)
The MCP server supports the following methods:
1. Search & navigation:
| Method | Description |
|---|---|
| search_docs | AI-powered semantic search through document content. Supports filtering by doc_ids or parent_doc_id to narrow scope. Only searches docs marked as indexed for AI. |
| get_docs_text_title_search | Searches for documents by title using keyword matching. Returns documents whose titles contain all query words. Use to find a document by name and get its doc_id. |
| get_doc_hierarchy | Returns all child/descendant/successors documents under a given doc_id, useful for inspecting (exploring) document trees. |
| list_docs | Lists shared documents with optional filters: parent_doc_ids, is_archived, is_important, for_welcome, show_in_main_doc_list, doc_ids). Returns metadata only (doc_id, title, parent_doc_id, etc.), no content. |
| list_personal_docs | Lists the current user's personal documents with metadata (title, position, timestamps), ordered by position. |
2. Content (batch):
| get_doc_content_batch | Returns full plain-text content of up to 50 documents by their doc_ids. Use when you need full text. |
| get_docs_for_boards_batch | Returns documents added to specific boards (by board_ids and / or board_names). The request is limited up to 500 boards. |
3. Create & edit – shared documents:
| create_doc | Creates a shared document. Required parameters: title. Optional parameters: content, parent_doc_id, show_in_main_doc_list. |
| update_doc | Updates a shared document by doc_id. Can change title, content, parent_doc_id, show_in_main_doc_list. |
| archive_doc | Archives a document and all its successors. Can be performed by the document Owner only. |
| unarchive_doc | Unarchives a document and its successors. Can be performed by the document Owner only. |
4. Personal documents:
| create_personal_doc | Creates a personal document. Required parameters: title. Optional parameters: content, position. |
| update_personal_doc | Updates a personal document. Only the document author can update. |
Supported Functional Areas (workspaces)
The MCP server supports the following methods:
| get_workspaces | Retrieves a list of workspaces. Optional parameters: name, type (used as filters). |
| create_workspace | Creates a new workspace. Required parameters: name (1–100 chars). Optional parameters: type (1=team, default; 2=management). |
| update_workspace | Updates a workspace. Identify by workspace_id (priority) or workspace_name. If multiple workspaces match the name, an error with the matching ids is returned. Required parameters: name (new name). |
Supported Functional Areas (boards)
The MCP server supports the following methods:
| create_board | Creates a new board in a workspace. Required parameters: name. Provide workspace_id and/or workspace_name (workspace_id has priority). Optional parameters: description, with_cards_workflow (default 1), with_initiatives_workflow (default 1), with_timeline_workflow (default 0), type (1=board only for now). Only owners or workspace managers can create boards. |
| update_board | Updates a board. Identify by board_id (priority) or board_name. If multiple boards match the name, an error with the matching ids is returned. Provide name (new name) and/or description to update. |
Supported Functional Areas (workflows)
The MCP server supports the following methods:
| create_workflow | Creates a new workflow on a board. Identify the board by board_id or board_name. Required parameters: type (0=cards, 1=initiatives, 2=timeline). Optional parameters: name (default names apply by type). |
| update_workflow | Updates a workflow. Identify by workflow_id (priority), or by workflow_name combined with board_id or board_name. Provide name and/or position to update. |
| link_related_workflow | Links a workflow from another board to a target board as a related workflow. Target board: board_id or board_name. Workflow to link: workflow_id, or source_board_id/source_board_name combined with workflow_name. You must be a workspace manager of both boards. Optional parameters: position. |
Supported Functional Areas (columns)
The MCP server supports the following methods:
| create_column | Creates a new column in a workflow. Identify the workflow by workflow_id, or by workflow_name with board_id or board_name (auto-resolved if the board has a single workflow). For a sub-column, provide parent_column_id or parent_column_name. Required parameters: name. Optional parameters: section (1=Backlog, 2=Requested, 3=In Progress, 4=Done), position (default 0). |
| update_column | Updates a column. Identify by column_id (priority), or by board/workflow plus column_name (column_name alone works if unique on the board). Set a new parent by parent_column_id (priority) or parent_column_name. Provide name, section, parent and/or position to update. |
Supported Functional Areas (lanes)
The MCP server supports the following methods:
| create_lane | Creates a new lane in a workflow. Identify the workflow by workflow_id, or by workflow_name with board_id or board_name (auto-resolved if the board has a single workflow). For a sub-lane, provide parent_lane_id or parent_lane_name. Required parameters: name. Optional parameters: position (default end). |
| update_lane | Updates a lane. Identify by lane_id (priority), or by workflow_id/workflow_name and lane_name. Set a new parent by parent_lane_id (priority) or parent_lane_name. Provide name, parent and/or position to update. |
Quick setup (batch)
The MCP server supports the following methods:
| create_workspaces_and_boards | Creates one or more workspaces together with their boards and full board structure (workflow renames, default-column renames, extra columns and lanes) in a single batch call — far more efficient than calling create_workspace, create_board, create_column and create_lane separately. Supports nesting up to 3 levels for columns and lanes, and AI Canvas boards (type=2, name only). Required parameters: workspaces. Maximum: 3 workspaces, 10 boards per workspace, 5 workflows per board, 10 columns and 10 lanes per workflow. |
| create_boards_in_workspace | Creates one or more boards with their structure in an existing workspace in a single batch call. Useful for adding multiple boards at once or resuming after a partial failure. Required parameters: workspace_id, boards. Maximum: 3 boards per call, 5 workflows per board, 10 columns and 10 lanes per workflow. |
| configure_board_structure | Configures the structure of an existing board (workflow renames, default-column renames, extra columns and lanes) in a single batch call. Use default_columns to rename the built-in Requested/In Progress/Done columns; use columns/lanes for additional ones. Added columns can be activity (1) or queue (2) type; columns and lanes can be nested up to 3 levels. Required parameters: board_id, workflows. Maximum: 5 workflows, 10 columns and 10 lanes per workflow. |
Installing and Configuring the Businessmap MCP Server
To configure the connection between Businessmap and your AI client, use one of the two guides below:
Remote MCP Guide (Recommended)
Local MCP Guide (Developers only)
Good to Know
Each AI tool (Cursor, Claude Desktop, Claude Code) can introspect the MCP server itself, meaning the full list of tools and their parameters can be discovered directly from within the AI assistant—no need to manually browse an API reference.
MCP enables complex AI workflows, such as multi-step card operations, performed in a single prompt.
The configuration is lightweight: only a subdomain and API key are required.
To use the MCP server, you need to have the Security control "Enable AI" on: