What is the key difference between Hubd and Teamwork MCP?

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

How do I install Hubd or Teamwork 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 Hubd and Teamwork MCP free or paid?

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

Which MCP server has more tools and community activity?

Hubd lists 6 tools with 2 views and 2 GitHub stars. Teamwork MCP lists 5 tools with 2 views and 24 GitHub stars.

Can I use both Hubd and Teamwork 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

Hubd vs Teamwork MCP

In-depth architectural comparison of the Hubd and Teamwork 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

Hubd

Workplace & Productivity · Local stdio

Quality: 53/100 (Good) | Auth: other

Teamwork MCP

Workplace & Productivity · Local stdio

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

Verdict Summary: Choose Hubd if you need specialized Workplace & Productivity tools running via a local process. Choose Teamwork 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 Hubd when:

You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
You have access to required keys: HUBD_AGENT, HUBD_DIR.
Primary tools included: MCP server over stdio and HTTP, CLI for hub initialization, status, briefs, and audits, Plain Markdown and JSONL data storage.

Explore Hubd Details

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.

Feature & Specification Comparison

Specification	Hubd bzdOS Workplace & Productivity	Teamwork MCP teamwork Workplace & Productivity
Summary	Files-first project hub for teams of humans and AI agents: shared journal, cross-project tasks, agent queues, and a read-only kanban. MCP server + CLI, zero dependencies.	Project and resource management platform that keeps your client projects on track, makes managing resources a breeze, and keeps your profits on point.
Category & Scope	Workplace & Productivity

Tools & Capabilities Breakdown

Hubd Tools (6)

MCP server over stdio and HTTP

CLI for hub initialization, status, briefs, and audits

Plain Markdown and JSONL data storage

Shared journal and cross-project task tracking

Agent queues with garbage collection

Read-only local kanban

Teamwork MCP Tools (5)

HTTP and STDIO transport interfaces

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).

Hubd Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "bzdos-hubd": {
      "command": "npx",
      "args": [
        "-y",
        "degit"
      ],
      "env": {
        "HUBD_AGENT": "YOUR_HUBD_AGENT_HERE",
        "HUBD_DIR": "YOUR_HUBD_DIR_HERE"
      }
    }
  }
}

Teamwork MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "teamwork-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/inspector"
      ],
      "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"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Hubd More alternatives to Teamwork MCP Workplace & Productivity category hub