What is the key difference between Teamwork MCP and Kanboard MCP?

Teamwork MCP belongs to the Workplace & Productivity category with local stdio execution, while Kanboard MCP belongs to the Workplace & Productivity category with local stdio execution.

How do I install Teamwork MCP or Kanboard MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Teamwork MCP and Kanboard MCP free or paid?

Teamwork MCP operates under a BYOK (Pay Provider Direct) model (API Key required). Kanboard MCP operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

Teamwork MCP lists 5 tools with 2 views and 25 GitHub stars. Kanboard MCP lists 6 tools with 3 views and 27 GitHub stars.

Can I use both Teamwork MCP and Kanboard MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Teamwork MCP vs Kanboard MCP

In-depth architectural comparison of the Teamwork MCP and Kanboard MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Teamwork MCP

Workplace & Productivity · Local stdio

Quality: 43/100 (Fair) | Auth: API Key required

Kanboard MCP

Workplace & Productivity · Local stdio

Quality: 47/100 (Fair) | Auth: API Key required

Verdict Summary: Choose Teamwork MCP if you need specialized Workplace & Productivity tools running via a local process. Choose Kanboard MCP if your workspace requires Workplace & Productivity integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Teamwork MCP when:

You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: TW_MCP_SERVER_ADDRESS, TW_MCP_BEARER_TOKEN, NODE_EXTRA_CA_CERTS.
Primary tools included: HTTP and STDIO transport interfaces, Bearer token and OAuth2 authentication, Extensible toolset architecture for Teamwork.com operations.

Explore Teamwork MCP Details

Choose Kanboard MCP when:

You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: KANBOARD_API_ENDPOINT, KANBOARD_API_KEY, KANBOARD_USERNAME, KANBOARD_PASSWORD.

Feature & Specification Comparison

Specification	Teamwork MCP teamwork Workplace & Productivity	Kanboard MCP bivex Workplace & Productivity
Summary	Project and resource management platform that keeps your client projects on track, makes managing resources a breeze, and keeps your profits on point.	A Model Context Protocol (MCP) server written in Go that empowers AI agents and Large Language Models (LLMs) to seamlessly interact with Kanboard. It transforms natural language commands into Kanboard API calls, enabling intelligent automation of project, task, and user management, streamlining workflows, and enhancing productivity.
Category & Scope

Tools & Capabilities Breakdown

Teamwork MCP Tools (5)

HTTP and STDIO transport interfaces

Bearer token and OAuth2 authentication

Extensible toolset architecture for Teamwork.com operations

Read-only mode for safe data access

Comprehensive logging and monitoring

Kanboard MCP Tools (6)

Kanboard API integration over JSON-RPC

Project creation, lookup, updates, and deletion

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Teamwork MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "teamwork-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "teamwork-mcp"
      ],
      "env": {
        "TW_MCP_SERVER_ADDRESS": "YOUR_TW_MCP_SERVER_ADDRESS_HERE",
        "TW_MCP_BEARER_TOKEN": "YOUR_TW_MCP_BEARER_TOKEN_HERE",
        "NODE_EXTRA_CA_CERTS": "YOUR_NODE_EXTRA_CA_CERTS_HERE"
      }
    }
  }
}

Kanboard MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "bivex-kanboard-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "bivex-kanboard-mcp"
      ],
      "env": {
        "KANBOARD_API_ENDPOINT": "YOUR_KANBOARD_API_ENDPOINT_HERE",
        "KANBOARD_API_KEY": "YOUR_KANBOARD_API_KEY_HERE",
        "KANBOARD_USERNAME": "YOUR_KANBOARD_USERNAME_HERE",
        "KANBOARD_PASSWORD": "YOUR_KANBOARD_PASSWORD_HERE"
      }
    }
  }
}

Frequently Asked Questions

Teamwork MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, Kanboard MCP belongs to Workplace & Productivity using local stdio subprocess. Select Teamwork MCP when you need capabilities focused on workplace & productivity and Kanboard MCP when you require tools for workplace & productivity.

More alternatives to Teamwork MCP More alternatives to Kanboard MCP Workplace & Productivity category hub Canonical compare URL