Teamwork.com

com.teamworkPublished by teamwork.comOfficial publisherv1.62.2Updated Nov 6, 2026

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

VerifiedSSEWeb executableProductivity & WorkflowCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Official Teamwork.com MCP server that lets an AI assistant create, read and update projects, tasks, tickets, spaces and chat conversations.

What you can do
  • Manage projects and tasks: create, read and update Teamwork.com projects, tasks, tags and timers
  • Handle support tickets and customers in Teamwork Desk
  • Work with Teamwork Spaces: spaces and pages
  • Read and post in Teamwork Chat conversations and messages
  • Optionally restrict the whole toolset to read-only operations
When to use it
Useful when a team already runs client projects on Teamwork.com and wants an assistant to look up or update tasks, tickets, pages and chat without switching apps. It is the official integration, so it is the natural choice over unofficial wrappers.
Requirements
A Teamwork.com site and API credentials: a bearer token from the Teamwork.com OAuth2 app login flow, supplied as TW_MCP_BEARER_TOKEN or an Authorization header. Can be used as a remote endpoint or run locally from the Docker image; the source build needs Go 1.27 or later. Optional TW_MCP_LOG_FORMAT and TW_MCP_LOG_LEVEL settings.
Before you install
The bearer token grants access to your Teamwork.com site, so treat TW_MCP_BEARER_TOKEN and the Authorization header as secrets. Tools cover create and update operations across projects, Desk, Spaces and Chat, so the assistant can change real business data; enable read-only mode if you only want lookups. Project, ticket and chat content is sent to the model provider.

Installation

In SourceWeft

  1. Open Teamwork.com in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.teamwork%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "teamwork-com": {
      "type": "sse",
      "url": "https://mcp.ai.teamwork.com/sse",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

Teamwork MCP Server

Model Context Protocol server for Teamwork.com integration with Large Language Models

[Go Report Card] [Go] [MCP]

📌 Are you a Teamwork.com user wanting to connect AI tools to your Teamwork.com site right now? Jump straight to the Usage Guide for tokens, enabling MCP, and client configuration examples.

📖 Overview

This MCP (Model Context Protocol) server enables seamless integration between Large Language Models and Teamwork.com. It provides a standardized interface for LLMs to interact with Teamwork.com projects, allowing AI agents to perform various project management operations.

🤖 What is MCP?

Model Context Protocol (MCP) is an open protocol that standardizes how applications provide context to LLMs. This server describes all the actions available in Teamwork.com (tools) in a way that LLMs can understand and execute through AI agents.

✨ Features

  • Multiple Transport Modes: HTTP and STDIO interfaces for different deployment scenarios
  • Secure Authentication: Bearer token and OAuth2 integration with Teamwork.com
  • Tool Framework: Extensible toolset architecture for adding new capabilities
  • Production Ready: Comprehensive logging, monitoring, and observability
  • Read-Only Mode: Optional restriction to read-only operations for safety

See the auto-generated Tool Reference for every create/read/update operation exposed across Projects, Desk, Spaces, and Chat, or browse the same catalogue with per-tool descriptions and a search filter at teamwork.github.io/mcp.

🚀 Available Servers

This project provides three different ways to interact with the Teamwork.com MCP server:

📡 HTTP Server

Production-ready HTTP server for cloud deployments and multi-client support.

📖 Full HTTP Server Documentation

Quick start:

bash
TW_MCP_SERVER_ADDRESS=:8080 go run cmd/mcp-http/main.go

💬 STDIO Server

Direct STDIO interface for desktop applications and development environments.

📖 Full STDIO Server Documentation

Quick start:

bash
TW_MCP_BEARER_TOKEN=your-token go run cmd/mcp-stdio/main.go

🛠️ HTTP CLI

Command-line tool for testing and debugging MCP server functionality.

📖 Full HTTP CLI Documentation

Quick start:

bash
go run cmd/mcp-http-cli/main.go -mcp-url=https://mcp.example.com list-tools

📋 Prerequisites

  • Go 1.27 or later
  • Valid Teamwork.com API credentials (bearer token or OAuth2 setup)

🧪 Development & Testing

Running Tests

bash
# Run all testsgo test ./...
# Run specific package testsgo test ./internal/twprojects/

MCP Inspector

For debugging purposes, use the MCP Inspector tool:

bash
NODE_EXTRA_CA_CERTS=letsencrypt-stg-root-x1.pem npx @modelcontextprotocol/inspector node build/index.js

[!IMPORTANT] Note: The NODE_EXTRA_CA_CERTS environment variable is required when using OAuth2 authentication with the Let's Encrypt certification authority. Download the certificate here.

🏗️ Architecture

├── cmd/│   ├── mcp-http/          # HTTP server implementation│   ├── mcp-stdio/         # STDIO server implementation│   ├── mcp-http-cli/      # CLI tool for testing via HTTP│   ├── mcp-test/          # Walks tool handlers against a real site│   ├── mcp-tokens/        # Token-cost report for the tool surface│   └── docs-gen/          # Generates the tool reference (Markdown + GitHub Pages)├── pkg/                   # Importable by other MCP servers built on this one│   ├── auth/              # Authentication helpers (bearer & OAuth2 token handling)│   ├── cli/               # -toolsets flag parsing│   ├── config/            # Configuration management (env, flags), MCP server setup│   ├── helpers/           # Shared utility functions (errors, link helpers, tool parsing)│   ├── request/           # HTTP request primitives / Teamwork API wiring│   ├── testutil/          # Product-neutral test mocks│   ├── toolsets/          # Tool framework and registration logic│   └── twctx/             # Per-request values derived from the bearer token├── internal/              # This server's own tools, not importable elsewhere│   ├── twprojects/        # Teamwork project/domain tools (tasks, tags, timers, etc.)│   ├── twdesk/            # Teamwork Desk tools (tickets, customers, etc.)│   ├── twspaces/          # Teamwork Spaces tools (spaces, pages, etc.)│   └── twchat/            # Teamwork Chat tools (conversations, messages)├── examples/              # Usage & integration examples (LangChain Node/Python)├── docs/usage/            # End-user setup & connection guide├── Makefile               # Common developer tasks├── Dockerfile             # Container build configuration├── CODE_OF_CONDUCT.md     # Community guidelines├── CONTRIBUTING.md        # Contribution guide└── SECURITY.md            # Security policy

Source: README.md at commit 4b68d04

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

19
  1. v1.62.2LatestNov 6, 2026
  2. v1.62.1Nov 5, 2026
  3. v1.62.0Nov 5, 2026
  4. v1.60.3Nov 4, 2026
  5. v1.60.1Oct 30, 2026
  6. v1.60.0Oct 26, 2026
  7. v1.51.3Oct 23, 2026
  8. v1.51.2Oct 12, 2026
  9. v1.51.1Oct 6, 2026
  10. v1.51.0Oct 1, 2026
  11. v1.49.0Sep 30, 2026
  12. v1.48.2Sep 28, 2026
  13. v1.48.1Sep 26, 2026
  14. v1.48.0Sep 25, 2026
  15. v1.47.0Sep 25, 2026
  16. v1.46.0Sep 23, 2026
  17. v1.45.0Sep 23, 2026
  18. v1.44.0Sep 21, 2026
  19. v1.43.2Sep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Teamwork integrations

Teamwork

ai.b77Official publisher

Remote MCP server for AI-first project management: plan epics, assign prioritized tasks and track team time from an assistant.

Streamable HTTPWeb executableAuth
Productivity & WorkflowCredential requiredOct 24, 2026