# Teamwork.com (oci · docker.io/teamwork/mcp)

The Teamwork.com official MCP server helps teams efficiently manage client projects with AI.

- Trust score: 11/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.ai.teamwork.com`: 32/100, [markdown](https://verifymcp.io/servers/com-teamwork-mcp/mcp.md), [page](https://verifymcp.io/servers/com-teamwork-mcp/mcp)
- remote · `mcp.ai.teamwork.com`: 31/100, [markdown](https://verifymcp.io/servers/com-teamwork-mcp/mcp-2.md), [page](https://verifymcp.io/servers/com-teamwork-mcp/mcp-2)
- oci · `docker.io/teamwork/mcp`: 11/100 (this document), [markdown](https://verifymcp.io/servers/com-teamwork-mcp/docker-io-teamwork-mcp.md), [page](https://verifymcp.io/servers/com-teamwork-mcp/docker-io-teamwork-mcp)

## Channel facts

- Registry: `oci`
- Package: `docker.io/teamwork/mcp`
- Version: `v1.62.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 35/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright), so the captured schema is incomplete.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: one of the two schema captures we compare could not list the server's tools (the server declared tools, or its tool listing failed outright). Comparing them would report every tool as removed, or find nothing to compare at all.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).
- **Tool Safety**: 0/100
  - Tool safety not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Teamwork.com MCP server?

Teamwork.com runs locally as a container image, launched with docker run --rm -i -e TW_MCP_BEARER_TOKEN -e TW_MCP_LOG_FORMAT -e TW_MCP_LOG_LEVEL docker.io/teamwork/mcp:v1.62.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add com-teamwork-mcp -- docker run --rm -i -e TW_MCP_BEARER_TOKEN -e TW_MCP_LOG_FORMAT -e TW_MCP_LOG_LEVEL docker.io/teamwork/mcp:v1.62.1
```

This image reads TW_MCP_BEARER_TOKEN, TW_MCP_LOG_FORMAT and TW_MCP_LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Cursor

```json
{
  "mcpServers": {
    "com-teamwork-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "TW_MCP_BEARER_TOKEN",
        "-e",
        "TW_MCP_LOG_FORMAT",
        "-e",
        "TW_MCP_LOG_LEVEL",
        "docker.io/teamwork/mcp:v1.62.1"
      ]
    }
  }
}
```

This image reads TW_MCP_BEARER_TOKEN, TW_MCP_LOG_FORMAT and TW_MCP_LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### VS Code

```json
{
  "servers": {
    "com-teamwork-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "TW_MCP_BEARER_TOKEN",
        "-e",
        "TW_MCP_LOG_FORMAT",
        "-e",
        "TW_MCP_LOG_LEVEL",
        "docker.io/teamwork/mcp:v1.62.1"
      ]
    }
  }
}
```

This image reads TW_MCP_BEARER_TOKEN, TW_MCP_LOG_FORMAT and TW_MCP_LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Codex

```bash
codex mcp add com-teamwork-mcp -- docker run --rm -i -e TW_MCP_BEARER_TOKEN -e TW_MCP_LOG_FORMAT -e TW_MCP_LOG_LEVEL docker.io/teamwork/mcp:v1.62.1
```

This image reads TW_MCP_BEARER_TOKEN, TW_MCP_LOG_FORMAT and TW_MCP_LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-teamwork-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "TW_MCP_BEARER_TOKEN",
        "-e",
        "TW_MCP_LOG_FORMAT",
        "-e",
        "TW_MCP_LOG_LEVEL",
        "docker.io/teamwork/mcp:v1.62.1"
      ],
      "enabled": true
    }
  }
}
```

This image reads TW_MCP_BEARER_TOKEN, TW_MCP_LOG_FORMAT and TW_MCP_LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Hermes

```yaml
mcp_servers:
  com-teamwork-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "TW_MCP_BEARER_TOKEN", "-e", "TW_MCP_LOG_FORMAT", "-e", "TW_MCP_LOG_LEVEL", "docker.io/teamwork/mcp:v1.62.1"]
```

This image reads TW_MCP_BEARER_TOKEN, TW_MCP_LOG_FORMAT and TW_MCP_LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Netclaw

```json
{
  "McpServers": {
    "com-teamwork-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "TW_MCP_BEARER_TOKEN",
        "-e",
        "TW_MCP_LOG_FORMAT",
        "-e",
        "TW_MCP_LOG_LEVEL",
        "docker.io/teamwork/mcp:v1.62.1"
      ]
    }
  }
}
```

This image reads TW_MCP_BEARER_TOKEN, TW_MCP_LOG_FORMAT and TW_MCP_LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Other

```json
{
  "mcpServers": {
    "com-teamwork-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "TW_MCP_BEARER_TOKEN",
        "-e",
        "TW_MCP_LOG_FORMAT",
        "-e",
        "TW_MCP_LOG_LEVEL",
        "docker.io/teamwork/mcp:v1.62.1"
      ]
    }
  }
}
```

This image reads TW_MCP_BEARER_TOKEN, TW_MCP_LOG_FORMAT and TW_MCP_LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 11, 0)

- [functional] Package version: v1.62.0 → v1.62.1

### 2026-11-04 (score 11, 0)

- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [security] Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional] Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [functional] Package version: v1.60.3 → v1.62.0
- [functional] Package version: v1.60.3 → v1.61.0

### 2026-11-03 (score 11, 0)

- [functional] Package version: v1.60.1 → v1.60.3
- [functional] Package version: v1.60.1 → v1.60.2

### 2026-10-30 (score 11, 0)

- [functional] Package version: v1.60.0 → v1.60.1

### 2026-10-26 (score 11, 0)

- [functional] Package version: v1.51.3 → v1.60.0

### 2026-10-23 (score 11, 0)

- [functional] Package version: v1.51.2 → v1.51.3

### 2026-10-14 (score 11, +4)

- [security] Stability: Stability not yet verified: one of the two schema captures we compare could not list the server's tools (the server declared tools, or its tool listing failed outright). Comparing them would report every tool as removed, or find nothing to compare at all.
- [security] Tool safety: Tool safety not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).
- [functional improvement] MCP protocol: unverified → pass
- [functional] Tool coverage: Tool coverage not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).
- [functional] Schema quality: Schema quality not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright), so the captured schema is incomplete.

### 2026-10-13 (score 7, +1)

- [security regression] Provenance: unverified → fail
- [functional regression] License: unverified → fail
- [functional improvement] Maintenance: unverified → pass

## MCP tools (0)

The sandbox run completed and this package exposed no tools.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/com-teamwork-mcp/docker-io-teamwork-mcp#diagnostics

## Score history

- 2026-11-05: 11
- 2026-11-04: 11
- 2026-11-03: 11
- 2026-11-02: 11
- 2026-11-01: 11
- 2026-10-31: 11
- 2026-10-30: 11
- 2026-10-29: 11
- 2026-10-28: 11
- 2026-10-27: 11
- 2026-10-26: 11
- 2026-10-25: 11
- 2026-10-24: 11
- 2026-10-23: 11
- 2026-10-22: 11
- 2026-10-21: 11
- 2026-10-20: 11
- 2026-10-19: 11
- 2026-10-18: 11
- 2026-10-17: 11
- 2026-10-16: 11
- 2026-10-15: 11
- 2026-10-14: 11
- 2026-10-13: 7
- 2026-10-12: 6
- 2026-10-10: 7
- 2026-10-07: 7
- 2026-10-04: 11
- 2026-10-03: 11
- 2026-10-02: 11

## Common questions

### What is the Teamwork.com MCP server?

Teamwork.com is an MCP server listed in the public MCP registry as com.teamwork/mcp. The Teamwork.com official MCP server helps teams efficiently manage client projects with AI. This page covers its container image (docker.io/teamwork/mcp).

### Is the Teamwork.com MCP server safe to use?

Teamwork.com scores 11 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Teamwork.com MCP server expose?

Teamwork.com exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.

### Is the Teamwork.com MCP server still maintained?

Teamwork.com is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Docker Hub: https://hub.docker.com/r/teamwork/mcp
- Repository: https://github.com/teamwork/mcp
- Website: https://www.teamwork.com/ai/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-teamwork-mcp/docker-io-teamwork-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-teamwork-mcp/docker-io-teamwork-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-teamwork-mcp/docker-io-teamwork-mcp