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

Clockify MCP 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 Clockify MCP 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 Clockify MCP and Teamwork MCP free or paid?

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

Which MCP server has more tools and community activity?

Clockify MCP lists 6 tools with 1 views and 1 GitHub stars. Teamwork MCP lists 5 tools with 2 views and 25 GitHub stars.

Can I use both Clockify MCP 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

Clockify MCP vs Teamwork MCP

In-depth architectural comparison of the Clockify MCP 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

Clockify MCP

Workplace & Productivity · Local stdio

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

Teamwork MCP

Workplace & Productivity · Local stdio

Quality: 52/100 (Good) | Auth: API Key required

Verdict Summary: Choose Clockify MCP 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 Clockify 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: CLOCKIFY_API_KEY.
Primary tools included: 112 tools across 18 Clockify domains, Read-only access by default, Optional time-tracking and full write access modes.

Explore Clockify MCP 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.

Feature & Specification Comparison

Specification	Clockify MCP tracegazer Workplace & Productivity	Teamwork MCP teamwork Workplace & Productivity
Summary	Clockify time-tracking MCP server: 112 tools across 18 domains (time entries, projects, reports, invoices, scheduling, time-off, approvals). Read-only by default, opt-in writes, OpenTelemetry.	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

Tools & Capabilities Breakdown

Clockify MCP Tools (6)

112 tools across 18 Clockify domains

Read-only access by default

Optional time-tracking and full write access modes

Report generation and PDF, CSV, or XLSX export

OpenTelemetry support

Claude Desktop MCPB bundle

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

Clockify MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "tracegazer-clockify-mcp": {
      "command": "uvx",
      "args": [
        "clockify-mcp"
      ],
      "env": {
        "CLOCKIFY_API_KEY": "YOUR_CLOCKIFY_API_KEY_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

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

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