Teamwork.com

com.teamwork由 teamwork.com 發布官方發布者v1.62.2更新於 Nov 6, 2026

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

概覽

AI 產生的概覽

Teamwork.com 官方 MCP 伺服器,讓 AI 助理建立、讀取與更新專案、任務、工單、空間與聊天對話。

可以做什麼
  • 管理專案與任務:建立、讀取與更新 Teamwork.com 專案、任務、標籤與計時器
  • 處理 Teamwork Desk 中的支援工單與客戶
  • 操作 Teamwork Spaces:空間與頁面
  • 讀取並在 Teamwork Chat 對話中傳送訊息
  • 可將整組工具限制為唯讀操作
適用情境
適合已在 Teamwork.com 管理客戶專案的團隊,希望助理不必切換應用程式就能查詢或更新任務、工單、頁面與聊天。它是官方整合,比非官方封裝更合適。
執行需求
需要 Teamwork.com 站台與 API 憑證:透過 Teamwork.com OAuth2 應用程式登入流程取得的 bearer token,以 TW_MCP_BEARER_TOKEN 或 Authorization 標頭提供。可作為遠端端點使用,也可用 Docker 映像在本機執行;從原始碼建置需 Go 1.27 以上版本。可選用 TW_MCP_LOG_FORMAT 與 TW_MCP_LOG_LEVEL。
安裝前請注意
bearer token 可存取你的 Teamwork.com 站台,請將 TW_MCP_BEARER_TOKEN 與 Authorization 標頭視為機密。工具涵蓋專案、Desk、Spaces 與 Chat 的建立與更新操作,助理可能改動真實業務資料;若只需查詢,請啟用唯讀模式。專案、工單與聊天內容會傳送給模型供應商。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Teamwork.com,將其新增到工作區。
  2. 連接 Authorization token 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable,透過 SSE。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/com.teamwork%2Fmcp/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

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

來源:README.md,提交 4b68d04

工具

0
該伺服器需要 API 金鑰等憑證,因此 SourceWeft 無法在沒有憑證的情況下讀取其工具,也未收錄。

版本歷史

19
  1. v1.62.2最新Nov 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

評分

已滿足適用檢查項的 60%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Teamwork 整合