Skip to main content
Glama
README.md
# @aixlab/kanbn-mcp

An [MCP (Model Context Protocol)](https://modelcontextprotocol.io) server for the [Kan](https://kan.bn) Kanban API. Allows AI assistants like Claude, Cursor, and others to interact with your Kan boards directly.

## Installation

### Via npx (recommended – no installation needed)

```bash
npx @aixlab/kanbn-mcp
```

### Global install

```bash
npm install -g @aixlab/kanbn-mcp
kanbn-mcp
```

## Configuration

The server requires the following environment variables:

| Variable | Description |
|---|---|
| `API_BASE_URL` | Base URL of your Kan instance (e.g. `https://kan.example.com/api`) |
| `BEARER_TOKEN_AUTHORIZATION` | Your Kan API key |

You can set these in a `.env` file or pass them directly as environment variables.

## Usage with Claude Desktop

Add this to your `claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "kan": {
      "command": "npx",
      "args": ["-y", "@aixlab/kanbn-mcp"],
      "env": {
        "API_BASE_URL": "https://kan.example.com/api",
        "BEARER_TOKEN_AUTHORIZATION": "your-api-key-here"
      }
    }
  }
}
```

## Usage with VS Code (GitHub Copilot)

Add this to your `.vscode/mcp.json`:

```json
{
  "servers": {
    "kan": {
      "command": "npx",
      "args": ["-y", "@aixlab/kanbn-mcp"],
      "env": {
        "API_BASE_URL": "https://kan.example.com/api",
        "BEARER_TOKEN_AUTHORIZATION": "your-api-key-here"
      }
    }
  }
}
```

## License

MIT

TDQS

B3.2/5.0

Scored across 78 tools

Disambiguation5/5

Tools are clearly grouped by resource (board, card, checklist, etc.) with distinct actions. Even closely related tools like the various member invitation tools have descriptions that clearly differentiate them. No ambiguous overlap.

Naming Consistency5/5

Uses a consistent [category]-[action] pattern (e.g., card-create, board-byId). Even nested categories like import-github-getProjects follow the pattern. Only minor variation like health-health is still predictable within its own group.

Tool Count4/5

78 tools is high but justified by the comprehensive coverage of a kanban/project management system (boards, cards, checklists, permissions, webhooks, imports, etc.). Each tool has a clear purpose, though some consolidation might be possible.

Completeness4/5

Covers most CRUD operations and many domain-specific actions (comments, checklists, labels, permissions, webhooks, imports). Minor gaps like a dedicated card move tool are missing, but card update can change list position. Overall very thorough.

Maintenance

ActivitySlowing
ResponsivenessNo issues