What is the key difference between Teamwork MCP and Temporal Cortex MCP?

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

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

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

Which MCP server has more tools and community activity?

Teamwork MCP lists 5 tools with 2 views and 25 GitHub stars. Temporal Cortex MCP lists 6 tools with 3 views and 12 GitHub stars.

Can I use both Teamwork MCP and Temporal Cortex 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 Temporal Cortex MCP

In-depth architectural comparison of the Teamwork MCP and Temporal Cortex 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: 52/100 (Good) | Auth: API Key required

Temporal Cortex MCP

Workplace & Productivity · Local stdio

Quality: 59/100 (Good) | Auth: OAuth 2.0

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

You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
You have access to required keys: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET.

Feature & Specification Comparison

Specification	Teamwork MCP teamwork Workplace & Productivity	Temporal Cortex MCP temporal-cortex Workplace & Productivity
Summary
Category & Scope	Workplace & Productivity	Workplace & Productivity

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

Temporal Cortex MCP Tools (6)

18 MCP scheduling tools across five layers

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",
        "@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"
      }
    }
  }
}

Temporal Cortex MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "temporal-cortex-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@temporal-cortex/cortex-mcp"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "YOUR_GOOGLE_CLIENT_ID_HERE",
        "GOOGLE_CLIENT_SECRET": "YOUR_GOOGLE_CLIENT_SECRET_HERE"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Teamwork MCP More alternatives to Temporal Cortex MCP Workplace & Productivity category hub