What is the key difference between Teamwork MCP and Openproject Codex Plugin?

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

How do I install Teamwork MCP or Openproject Codex Plugin 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 Openproject Codex Plugin free or paid?

Teamwork MCP operates under a BYOK (Pay Provider Direct) model (API Key required). Openproject Codex Plugin 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. Openproject Codex Plugin lists 6 tools with 4 views and 0 GitHub stars.

Can I use both Teamwork MCP and Openproject Codex Plugin 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 Openproject Codex Plugin

In-depth architectural comparison of the Teamwork MCP and Openproject Codex Plugin 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

Openproject Codex Plugin

Workplace & Productivity · Local stdio

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

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

Feature & Specification Comparison

Specification	Teamwork MCP teamwork Workplace & Productivity	Openproject Codex Plugin alex13slem 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.	Write-capable MCP server for OpenProject API v3 with Community Edition support. Search, create, update, assign, prioritize, and comment on work packages. Published as io.github.alex13slem/openproject in the official MCP Registry and installable with npx -y openproject-codex-plugin.
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

Openproject Codex Plugin Tools (6)

41 OpenProject API v3 tools

Read and write project and work-package operations

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

Openproject Codex Plugin Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "alex13slem-openproject-codex-plugin": {
      "command": "npx",
      "args": [
        "-y",
        "openproject-codex-plugin"
      ],
      "env": {
        "OPENPROJECT_URL": "YOUR_OPENPROJECT_URL_HERE",
        "OPENPROJECT_API_TOKEN": "YOUR_OPENPROJECT_API_TOKEN_HERE"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Teamwork MCP More alternatives to Openproject Codex Plugin Workplace & Productivity category hub Canonical compare URL