businessmap

BusinessMap MCP Server exposes a Model Context Protocol interface to interact with BusinessMap's Kanbanize-based project management. It provides programmatic access to workspaces, boards, cards, subtasks, and many related entities, enabling automation, data retrieval, and write-actions via MCP tools. The server ships with a rich set of capabilities described in the README, including 56 distinct tools, 5 resources, and 4 guided prompts, covering workspaces, boards, cards, subtasks, parent-child relationships, outcomes, comments, tags, stickers, predecessors, custom fields, and more. You can integrate these capabilities into your workflows, scripts, or client applications to read data, create and update items, manage relationships, and enforce access patterns through a consistent MCP interface.

Prerequisites:

• Node.js v18 or newer installed on your system
• npm (comes with Node.js) or npmx tooling if you prefer
• Internet access to fetch the MCP package from npm

Installation steps:

1. Ensure Node.js is installed:
   • node -v
   • npm -v
2. Install or run via NPX (recommended):
   • npx @edicarlos.lds/businessmap-mcp

Optional global installation:

• npm install -g @edicarlos.lds/businessmap-mcp

Configuration example (ENV variables required by the server):

• Create a .env file or export environment variables in your shell: BUSINESSMAP_API_TOKEN=your_token_here BUSINESSMAP_API_URL=https://your-account.kanbanize.com/api/v2 BUSINESSMAP_READ_ONLY_MODE=false BUSINESSMAP_DEFAULT_WORKSPACE_ID=1 LOG_LEVEL=1 PORT=3000

Run the server via NPX (no global install required): npx @edicarlos.lds/businessmap-mcp

If you prefer to configure via Claude, Cursor, VS Code, Windsurf, or Zed, follow the integration examples in the README to write your mcp.json or equivalent configuration files.

Tips and common considerations:

• Always provide BUSINESSMAP_API_TOKEN and BUSINESSMAP_API_URL to authenticate with BusinessMap.
• The server supports multiple transports; default is stdio for Claude/Cursor/VS Code integrations. If you enable HTTP transport, configure ALLOWED_ORIGINS and ALLOWED_HOSTS accordingly for security.
• Use PORT to expose the HTTP server when running in HTTP mode; otherwise, rely on the stdio-based workflows.
• If you encounter rate limits or token issues, ensure tokens have the correct scopes and that the API URL is reachable from your environment.
• For local development, keeping a .env file with proper values simplifies repeated runs.
• When sharing configurations in version control, avoid hardcoding secrets; use environment variable expansion (e.g., ${VAR}) in .mcp.json as supported by your tools.