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 集成