Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
The Teamwork.com official MCP server helps teams efficiently manage client projects with AI.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
TW_MCP_BEARER_TOKEN, TW_MCP_LOG_FORMAT, TW_MCP_LOG_LEVEL, Authorization标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"teamwork": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"TW_MCP_BEARER_TOKEN",
"-e",
"TW_MCP_LOG_FORMAT",
"-e",
"TW_MCP_LOG_LEVEL",
"docker.io/teamwork/mcp:v1.62.2"
],
"env": {
"TW_MCP_BEARER_TOKEN": "your-value",
"TW_MCP_LOG_FORMAT": "your-value",
"TW_MCP_LOG_LEVEL": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport sse teamwork https://mcp.ai.teamwork.com/sse --header 'Authorization: your-value'claude mcp add teamwork --env TW_MCP_BEARER_TOKEN=your-value --env TW_MCP_LOG_FORMAT=your-value --env TW_MCP_LOG_LEVEL=your-value -- docker run -i --rm -e TW_MCP_BEARER_TOKEN -e TW_MCP_LOG_FORMAT -e TW_MCP_LOG_LEVEL docker.io/teamwork/mcp:v1.62.2运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"teamwork": {
"url": "https://mcp.ai.teamwork.com/sse",
"headers": {
"Authorization": "your-value"
}
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"teamwork": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"TW_MCP_BEARER_TOKEN",
"-e",
"TW_MCP_LOG_FORMAT",
"-e",
"TW_MCP_LOG_LEVEL",
"docker.io/teamwork/mcp:v1.62.2"
],
"env": {
"TW_MCP_BEARER_TOKEN": "your-value",
"TW_MCP_LOG_FORMAT": "your-value",
"TW_MCP_LOG_LEVEL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"teamwork": {
"type": "sse",
"url": "https://mcp.ai.teamwork.com/sse",
"headers": {
"Authorization": "your-value"
}
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"teamwork": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"TW_MCP_BEARER_TOKEN",
"-e",
"TW_MCP_LOG_FORMAT",
"-e",
"TW_MCP_LOG_LEVEL",
"docker.io/teamwork/mcp:v1.62.2"
],
"env": {
"TW_MCP_BEARER_TOKEN": "your-value",
"TW_MCP_LOG_FORMAT": "your-value",
"TW_MCP_LOG_LEVEL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
TW_MCP_LOG_FORMAT envTW_MCP_LOG_LEVEL envAuthorization 机密 必填 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 teamwork.com 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
在 600 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:TW_MCP_BEARER_TOKEN, Authorization
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(1.62.2)于今天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, SSTracker free youth training
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Free youth sports drills, practice plans and age-group answers for parents and coaches.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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](docs/usage/README.md) for tokens, enabling MCP, and client configuration examples.
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.
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.
See the auto-generated [Tool Reference](docs/tool-reference.md) 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](https://teamwork.github.io/mcp/).
This project provides three different ways to interact with the Teamwork.com MCP server:
Production-ready HTTP server for cloud deployments and multi-client support.
📖 [Full HTTP Server Documentation](cmd/mcp-http/README.md)
Quick start:
TW_MCP_SERVER_ADDRESS=:8080 go run cmd/mcp-http/main.go
Direct STDIO interface for desktop applications and development environments.
📖 [Full STDIO Server Documentation](cmd/mcp-stdio/README.md)
Quick start:
TW_MCP_BEARER_TOKEN=your-token go run cmd/mcp-stdio/main.go
Command-line tool for testing and debugging MCP server functionality.
📖 [Full HTTP CLI Documentation](cmd/mcp-http-cli/README.md)
Quick start:
go run cmd/mcp-http-cli/main.go -mcp-url=https://mcp.example.com list-tools
# Run all tests
go test ./...
go test ./internal/twprojects/
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.
├── 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