Teamwork.com

Q: Is Teamwork.com a remote or a local server?

Remote. Teamwork.com hosts it at https://mcp.ai.teamwork.com, and it speaks Streamable HTTP. There's nothing to install.

listing.by

Manage Teamwork.com projects, tasks, time logs and people, plus Desk, Spaces and Chat, from your AI assistant.

state.auth.longStreamable HTTP

listing.connect

listing.explain.oauth

https://mcp.ai.teamwork.com

listing.note.oauth

act.add_to act.add_to act.add_to

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

listing.can

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

listing.tools

listing.notools.oauth

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

listing.setup.h

listing.setup.oauth

Claude Code

Run this in a terminal, in your project folder:

claude mcp add --transport http teamwork https://mcp.ai.teamwork.com

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

Open Settings → Connectors and click Add custom connector.
Name it Teamwork.com and paste this URL:

https://mcp.ai.teamwork.com

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

Open the connector form on claude.ai. This button fills in the name and URL for you:

Add to claude.ai a11y.new_tab

Check that the URL reads https://mcp.ai.teamwork.com and click Add.
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

On chatgpt.com, open Settings → Security and login and turn on Developer mode.
Go to chatgpt.com/plugins and click + to create an app for a remote MCP server.
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 a11y.new_tab

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.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 a11y.new_tab

Or from a terminal:

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

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

Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):

mcp_config.json

{
  "mcpServers": {
    "teamwork": {
      "serverUrl": "https://mcp.ai.teamwork.com"
    }
  }
}

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

codex mcp add teamwork --url https://mcp.ai.teamwork.com
codex mcp login teamwork

Or edit ~/.codex/config.toml directly:

config.toml

[mcp_servers.teamwork]
url = "https://mcp.ai.teamwork.com"

Gemini CLI

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.

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

listing.faq

Can I paste mcp.tc/i/teamwork into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://mcp.ai.teamwork.com, so your client talks to Teamwork.com directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.

Does Teamwork.com need an API key or a sign-in?

Yes, you need a Teamwork.com account. The first time your client connects, it opens Teamwork.com's sign-in page. The token goes straight to the server's own URL, never through mcp.tc.

Is Teamwork.com a remote or a local server?

Remote. Teamwork.com hosts it at https://mcp.ai.teamwork.com, and it speaks Streamable HTTP. There's nothing to install.

What can Teamwork.com do?

You can create, read and update projects and tasks, work with tags and timers for time tracking and handle Desk tickets and customers.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Who wrote this page?

mcp.tc's robot read Teamwork.com's own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can't confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

listing.em.h

listing.em.lead listing.em.how

listing.em.badge

Markdown

[![Teamwork.com on mcp.tc](https://mcp.tc/i/teamwork/badge.svg)](https://mcp.tc/i/teamwork)

HTML

<a href="https://mcp.tc/i/teamwork"><img src="https://mcp.tc/i/teamwork/badge.svg" alt="Teamwork.com on mcp.tc" height="20"></a>

listing.em.badge_note

listing.em.widget

HTML

<script src="https://mcp.tc/w/teamwork.js" async></script>

listing.em.widget_note

iframe

HTML

<iframe src="https://mcp.tc/embed/teamwork" title="Teamwork.com on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

listing.em.iframe_note