# Teamwork.com MCP server
> Manage Teamwork.com projects, tasks, time logs and people, plus Desk, Spaces and Chat, from your AI assistant.
- Listing: https://mcp.tc/i/teamwork
- Connect: use the server's own URL `https://mcp.ai.teamwork.com` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Productivity & Projects](https://mcp.tc/c/productivity)
- Vendor: Teamwork.com
- Homepage:
- Docs:
- Repository:
- Package: oci `docker.io/teamwork/mcp:v1.51.0`
## About
Connects an assistant to Teamwork.com so it can work with client projects, tasks, time tracking and people. The server also exposes tools for Teamwork Desk (tickets, customers), Spaces (spaces, pages) and Chat (conversations, messages). A read-only mode can limit it to read operations.
Runs as a hosted streamable HTTP endpoint at https://mcp.ai.teamwork.com (an SSE endpoint is also available) with OAuth sign-in. A bearer token in the Authorization header is also accepted. A local Docker image, teamwork/mcp, runs the server over STDIO or HTTP and needs a bearer token.
## What it can do
- Create, read and update projects and tasks
- Work with tags and timers for time tracking
- Handle Desk tickets and customers
- Read and edit Spaces and pages
- Read and send Chat conversations and messages
- Restrict the server to read-only operations
## Example prompts
- "List my open Teamwork tasks due this week"
- "Create a task in the Website Redesign project and assign it to Sam"
- "Log 2 hours on the onboarding task for today"
- "Show the latest Desk tickets from our biggest customer"
## Install
### Claude Code
1. Run this in a terminal, in your project folder:
```bash
claude mcp add --transport http teamwork https://mcp.ai.teamwork.com
```
2. Start Claude Code, type `/mcp`, pick **teamwork** and choose **Authenticate**. A browser window opens for the Teamwork.com sign-in.
Add `--scope user` to make it available in every project, not just this one.
### Claude Desktop
1. Open **Settings → Connectors** and click **Add custom connector**.
2. Name it **Teamwork.com** and paste this URL:
```url
https://mcp.ai.teamwork.com
```
3. Click **Add**, then **Connect**, and sign in when Teamwork.com asks.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
### claude.ai
1. Open the connector form on claude.ai. This button fills in the name and URL for you:
[Add to claude.ai]() (opens connector settings)
2. Check that the URL reads `https://mcp.ai.teamwork.com` and click **Add**.
3. Click **Connect** and sign in when Teamwork.com asks.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.
### ChatGPT
1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**.
2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.
3. Paste `https://mcp.ai.teamwork.com` as the server URL and choose **OAuth**. ChatGPT sends you to Teamwork.com to sign in.
Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.
### Cursor
[Add to Cursor]() (opens Cursor)
Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):
`mcp.json`:
```json
{
"mcpServers": {
"teamwork": {
"url": "https://mcp.ai.teamwork.com"
}
}
}
```
Cursor shows **Needs login** next to the server. Click it to sign in.
### VS Code
[Install in VS Code]() (opens VS Code)
Or from a terminal:
```bash
code --add-mcp '{"name":"teamwork","type":"http","url":"https://mcp.ai.teamwork.com"}'
```
Or commit it to the repo in `.vscode/mcp.json`:
`.vscode/mcp.json`:
```json
{
"servers": {
"teamwork": {
"type": "http",
"url": "https://mcp.ai.teamwork.com"
}
}
}
```
VS Code asks you to sign in the first time the server starts.
### Devin Desktop
1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):
`mcp_config.json`:
```json
{
"mcpServers": {
"teamwork": {
"serverUrl": "https://mcp.ai.teamwork.com"
}
}
}
```
2. Refresh the MCP server list in Cascade and sign in when asked.
Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.
### Codex
```bash
codex mcp add teamwork --url https://mcp.ai.teamwork.com
codex mcp login teamwork
```
Or edit `~/.codex/config.toml` directly:
`config.toml`:
```toml
[mcp_servers.teamwork]
url = "https://mcp.ai.teamwork.com"
```
### Gemini CLI
```bash
gemini mcp add --transport http teamwork https://mcp.ai.teamwork.com
```
Then, inside Gemini CLI, run `/mcp auth teamwork` to sign in.
This adds it to the current project. Add `-s user` to use it everywhere.
### Any client
Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.
```json
{
"mcpServers": {
"teamwork": {
"type": "http",
"url": "https://mcp.ai.teamwork.com"
}
}
}
```
Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.
Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.ai.teamwork.com`.
## Details
- Server version: 1.51.0
- MCP protocol version: 2026-07-28
- Last checked: 2026-10-03 (reachable, asks for credentials)
- Listed: 2026-10-03
- Updated: 2026-10-03
---
Source: https://mcp.tc/i/teamwork (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report