Zephyr Scale MCP vs Teamwork MCP

In-depth architectural comparison of the Zephyr Scale 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.

Which MCP Server Should You Choose?

Choose Zephyr Scale MCP when:

• You need dedicated capabilities in the Workplace & Productivity domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Zephyr Scale 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.
• Primary tools included: HTTP and STDIO transport interfaces, Bearer token and OAuth2 authentication, Extensible toolset architecture for Teamwork.com operations.

Explore Teamwork MCP Details

Feature & Specification Comparison

Specification	Zephyr Scale MCP Workplace & Productivity	Teamwork MCP teamwork Workplace & Productivity
Summary	Zephyr Scale on self-hosted Jira Server/DC: test cases, cycles, executions, plans and attachments	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

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

{
  "mcpServers": {
    "zephyr-scale-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "zephyr-scale-mcp"
      ]
    }
  }
}

{
  "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"
      }
    }
  }
}

Related MCP Server Comparisons