com.teamwork/mcp
The Teamwork.com official MCP server helps teams efficiently manage client projects with AI.
What can you do with com.teamwork/mcp?
- 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
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport sse com-teamwork-mcp 'https://mcp.ai.teamwork.com/sse' --header 'Authorization: <API key generated from the Teamwork.com OAuth2 process: https://apidocs.teamwork.com/guides/teamwork/app-login-flow>'
{
"mcpServers": {
"com-teamwork-mcp": {
"type": "sse",
"url": "https://mcp.ai.teamwork.com/sse",
"headers": {
"Authorization": "<API key generated from the Teamwork.com OAuth2 process: https://apidocs.teamwork.com/guides/teamwork/app-login-flow>"
}
}
}
}
claude mcp add --transport http com-teamwork-mcp 'https://mcp.ai.teamwork.com' --header 'Authorization: <API key generated from the Teamwork.com OAuth2 process: https://apidocs.teamwork.com/guides/teamwork/app-login-flow>'
{
"mcpServers": {
"com-teamwork-mcp": {
"type": "http",
"url": "https://mcp.ai.teamwork.com",
"headers": {
"Authorization": "<API key generated from the Teamwork.com OAuth2 process: https://apidocs.teamwork.com/guides/teamwork/app-login-flow>"
}
}
}
}
docker.io/teamwork/mcp:v1.60.1claude mcp add com-teamwork-mcp -e 'TW_MCP_BEARER_TOKEN=<your tw_mcp_bearer_token>' -e 'TW_MCP_LOG_FORMAT=<TW_MCP_LOG_FORMAT>' -e 'TW_MCP_LOG_LEVEL=<TW_MCP_LOG_LEVEL>' -- docker run -i --rm docker.io/teamwork/mcp:v1.60.1
{
"mcpServers": {
"com-teamwork-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/teamwork/mcp:v1.60.1"
],
"env": {
"TW_MCP_BEARER_TOKEN": "<your tw_mcp_bearer_token>",
"TW_MCP_LOG_FORMAT": "<TW_MCP_LOG_FORMAT>",
"TW_MCP_LOG_LEVEL": "<TW_MCP_LOG_LEVEL>"
}
}
}
}
Environment variables
TW_MCP_BEARER_TOKENrequired secret API key generated from the Teamwork.com OAuth2 process: https://apidocs.teamwork.com/guides/teamwork/app-login-flowTW_MCP_LOG_FORMATChoose log output format between 'text' or 'json'. Default is 'text'.TW_MCP_LOG_LEVELChoose log level between 'debug', 'info', 'warn' or 'error'. Default is 'info'.
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
Teamwork MCP Server
Model Context Protocol server for Teamwork.com integration with Large Language Models
📌 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:
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:
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.
Quick start:
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
# Run all tests
go test ./...
# Run specific package tests
go test ./internal/twprojects/
MCP Inspector
For debugging purposes, use the MCP Inspector tool:
NODE_EXTRA_CA_CERTS=letsencrypt-stg-root-x1.pem npx @modelcontextprotocol/inspector node build/index.js
[!IMPORTANT] Note: The
NODE_EXTRA_CA_CERTSenvironment 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
Frequently asked questions
What is com.teamwork/mcp?
The Teamwork.com official MCP server helps teams efficiently manage client projects with AI.
How do I install com.teamwork/mcp?
It runs as a remote server. In Claude Code: claude mcp add --transport sse com-teamwork-mcp 'https://mcp.ai.teamwork.com/sse' --header 'Authorization: <API key generated from the Teamwork.com OAuth2 process: https://apidocs.teamwork.com/guides/teamwork/app-login-flow>'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does com.teamwork/mcp need an API key?
Yes. It expects TW_MCP_BEARER_TOKEN, Authorization, which you set in its configuration.
Is com.teamwork/mcp open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains com.teamwork/mcp?
It is published by teamwork. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.