BusinessMap MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@BusinessMap MCP Server List all my boards"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
BusinessMap MCP Server
A Model Context Protocol (MCP) server for integrating BusinessMap (formerly Kanbanize) with MCP-compatible applications.
Features
Board Management: List workspaces and boards
Card Operations: Search, view, create, and update cards
User Management: List team members
Search Capabilities: Find cards by title across boards
Related MCP server: scrumdo-mcp
Architecture
The server is organized into separate modules for maintainability:
businessmap_client.py- BusinessMap API clientbusinessmap_tools.py- MCP tool implementationsbusinessmap_mcp_server.py- Main server entry point
Available Tools
Information Tools
list_workspaces()- Get all workspaceslist_boards()- Get all boardslist_users()- Get all usersget_board_cards(board_id, limit=50)- Get cards from a specific boardget_card_details(card_id)- Get detailed card informationsearch_cards(query, board_id=None, limit=20)- Search cards by title
Management Tools
create_card(template_type, title, description="")- Create new cardsupdate_card(card_id, title=None, description=None)- Update existing cards
Setup
1. Install Dependencies
This project uses uv for dependency management.
cd businessmap-mcp-server
uv syncAlternatively, run the setup script:
./setup.sh2. Set Environment Variables
You need to configure your BusinessMap credentials:
export BUSINESSMAP_SUBDOMAIN="YOUR_SUBDOMAIN_HERE"
export BUSINESSMAP_API_KEY="your-api-key-here"Or create a .env file:
BUSINESSMAP_SUBDOMAIN=YOUR_SUBDOMAIN_HERE
BUSINESSMAP_API_KEY=your-api-key-here3. Test the Server
uv run python businessmap_mcp_server.pyClaude Code Integration
To use with Claude Code, add this server to your MCP settings:
Option 1: Using stdio transport
Add to your Claude Code settings (~/.config/claude-code/settings/default.json):
{
"mcpServers": {
"businessmap": {
"command": "python",
"args": ["/path/to/businessmap-mcp-server/businessmap_mcp_server.py"],
"env": {
"BUSINESSMAP_SUBDOMAIN": "YOUR_SUBDOMAIN_HERE",
"BUSINESSMAP_API_KEY": "your-api-key-here"
}
}
}
}Option 2: Using uv (recommended)
{
"mcpServers": {
"businessmap": {
"command": "uv",
"args": ["--directory", "/path/to/businessmap-mcp-server", "run", "python", "businessmap_mcp_server.py"],
"env": {
"BUSINESSMAP_SUBDOMAIN": "YOUR_SUBDOMAIN_HERE",
"BUSINESSMAP_API_KEY": "your-api-key-here"
}
}
}
}Usage Examples
Once configured, you can use these commands in Claude Code:
"List all my BusinessMap boards"
"Show me cards in the Development board"
"Search for cards about 'authentication'"
"Create a new card in board 3 with title 'Fix login bug'"
"Get details for card 14193"
"Update card 14193 with a new description"
API Reference
BusinessMap API Integration
This server uses BusinessMap's REST API v2. The following endpoints are supported:
GET /workspaces- List workspacesGET /boards- List boardsGET /cards- List cards (with filtering)GET /cards/{id}- Get card detailsGET /users- List usersPOST /cards- Create cardsPATCH /cards/{id}- Update cards
Security Notes
Store your API key securely
Use environment variables rather than hardcoding credentials
The API key has full access to your BusinessMap account
Consider creating a dedicated API key for this integration
Troubleshooting
Common Issues
Authentication Error: Verify your API key and subdomain are correct
Connection Error: Check your internet connection and BusinessMap service status
Permission Error: Ensure your API key has appropriate permissions
Debug Mode
Enable debug logging:
export LOG_LEVEL=DEBUG
uv run python businessmap_mcp_server.pyContributing
Feel free to extend this server with additional BusinessMap API endpoints or features.
Available Tools
9 toolscreate_cardC
Create a new card in BusinessMap
Args: title: The title of the card description: Description for the card user_id: The ID of the user to assign the card to (optional) tag_ids: List of tag IDs to assign to the card (optional)
Inputs: title (required), tag_ids (required), user_id (required), description (required). Returns: result
get_board_cardsA
Get cards from a specific board
Args: board_id: The ID of the board limit: Maximum number of cards to return (default: 50)
Inputs: board_id (required), limit. Returns: result
get_card_detailsC
Get detailed information about a specific card
Args: card_id: The ID of the card
Inputs: card_id (required). Returns: result
get_user_cardsA
Get cards assigned to a specific user
Args: user_id: The ID of the user whose cards to retrieve (if not provided, uses the current user) board_id: Optional board ID to limit search to specific board column_id: Optional column ID to limit search to specific column limit: Maximum number of cards to return (default: 50)
Inputs: limit, user_id, board_id, column_id. Returns: result
list_boardsA
List all BusinessMap boards
Inputs: no named parameters. Returns: result
list_usersA
List all BusinessMap users
Inputs: no named parameters. Returns: result
list_workspacesA
List all BusinessMap workspaces
Inputs: no named parameters. Returns: result
search_cardsA
Search for cards by title
Args: query: Search query string board_id: Optional board ID to limit search to specific board limit: Maximum number of results (default: 20)
Inputs: query (required), limit, board_id. Returns: result
update_cardA
Update an existing card in BusinessMap
Args: card_id: The ID of the card to update title: New title for the card (optional) description: New description for the card (optional)
Inputs: card_id (required), title, description. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
The tools have mostly distinct purposes: list_* enumerate top-level entities, get_* retrieve cards in different ways, and create/update_card handle mutations. The only potential confusion is between get_board_cards and get_user_cards, both returning cards but with different filters; descriptions clarify this. Search and details are clearly separate.
The naming follows a consistent verb_noun pattern with list_, get_, search_, create_, update_. However, get_board_cards and get_user_cards use get_ for what are list-like operations, and get_card_details is oddly specific; a more consistent scheme would be list_cards_by_board and list_cards_by_user.
Nine tools is well-scoped for a BusinessMap integration, covering the core entities (users, workspaces, boards, cards) without redundancy. Each tool serves a clear purpose, and the count is within the ideal range.
The card lifecycle is partially covered: read (via board, user, details, search), create, and update title/description. Missing delete_card and card state transitions (e.g., moving between columns) are notable gaps. User, workspace, and board operations are limited to listing, which may be sufficient for context.
Maintenance
Related MCP Connectors
Remote MCP for Kanban AI boards—manage projects, tasks, and comments from AI tools.
Agile project management over MCP: boards, epics, roadmap, retros, whiteboards, wiki, metrics
Kanban board for teams and coding agents: manage tasks, subtasks, sprints and wiki pages via MCP.
Read and manage your EasyKanban kanban boards: to-do summaries, create, update, and move cards.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceModel Context Protocol server for BusinessMap (Kanbanize) integration. Provides comprehensive access to BusinessMap's project management features including workspaces, boards, cards, subtasks, parent-child relationships, outcomes, custom fields, and more.1,450 npm12MIT

scrumdo-mcpofficial
AlicenseAqualityAmaintenanceConnects MCP-compatible AI tools to ScrumDo boards, enabling card, task, comment, and search operations without manual copy-pasting.45MIT- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage Kanban boards, cards, sessions, and automations through a unified MCP interface with real-time updates, supporting delegation, agent sessions, and human-in-the-loop interactions.AGPL 3.0
- FlicenseNot gradedqualityFmaintenanceEnables unified management of work items from multiple tools through a kanban, providing CRUD, status transitions, comments, links, enrichment, dispatch, and board tools via MCP.-