BusinessMap MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BUSINESSMAP_API_KEY | Yes | Your BusinessMap API key | |
| BUSINESSMAP_SUBDOMAIN | Yes | Your BusinessMap subdomain (e.g., yourcompany) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workspacesA | List all BusinessMap workspaces |
| list_boardsA | List all BusinessMap boards |
| list_usersA | List all BusinessMap users |
| 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) |
| 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) |
| get_card_detailsC | Get detailed information about a specific card Args: card_id: The ID of the card |
| 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) |
| create_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) |
| 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) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.