Does Teamwork.com have an MCP server?
Teamwork.com maintains an official MCP server.
Available on paid plans only, and an admin must switch it on in Settings.
- Access
- Remote server
- Endpoint
- https://mcp.ai.teamwork.com
- Repository
- Teamwork/mcp
- Maintainer
- Teamwork.com
- License
- MIT
- Language
- Go
- Stars
- 26
- Last commit
- today
- Category
- Workplace & Productivity
Teamwork.com MCP server
Project site: mcp.ai.teamwork.com
A remote server run by Teamwork.com itself — nothing to install. Documented at support.teamwork.com.
Hosted by the vendor — no install, connect over HTTP with OAuth or a token.
Add it from the terminal, then restart your session:
claude mcp add --transport http teamwork https://mcp.ai.teamwork.comAdd --scope user to make it available in every project.
- Open Settings → Connectors
- Click Add custom connector
- Paste
https://mcp.ai.teamwork.com - Finish the sign-in prompt, then enable it in the chat's tools menu
Add to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for
every project:
{
"mcpServers": {
"teamwork": {
"url": "https://mcp.ai.teamwork.com"
}
}
}A green dot in Settings → MCP means it connected.
Add to .vscode/mcp.json:
{
"servers": {
"teamwork": {
"type": "http",
"url": "https://mcp.ai.teamwork.com"
}
}
}Then pick the server from the tools menu in Copilot's agent mode.
- Enable Developer mode under Settings → Apps & Connectors → Advanced
- Choose Create and paste
https://mcp.ai.teamwork.com - Complete sign-in, then enable the connector in a new chat
Does Teamwork.com have an official MCP server?
Yes. Teamwork.com maintains an official MCP server, hosted at https://mcp.ai.teamwork.com. The source lives at Teamwork/mcp on GitHub.
How do I connect Teamwork.com to Claude?
Add https://mcp.ai.teamwork.com as a custom connector under Settings → Connectors in Claude Desktop or claude.ai, or run "claude mcp add --transport http teamwork https://mcp.ai.teamwork.com" in Claude Code.
Do I need to install anything to use the Teamwork.com MCP server?
No. It is a remote server hosted by Teamwork.com, so your MCP client connects to it over HTTP. You authenticate with the vendor rather than installing a package.
How is this verdict verified?
Published to the MCP Registry under Teamwork.com's verified namespace com.teamwork; hosted endpoint mcp.ai.teamwork.com answers MCP initialize (200) and is documented at support.teamwork.com and in the Teamwork/mcp repo. GitHub metadata is refreshed every six hours.
Published to the MCP Registry under Teamwork.com's verified namespace com.teamwork; hosted endpoint mcp.ai.teamwork.com answers MCP initialize (200) and is documented at support.teamwork.com and in the Teamwork/mcp repo.
- github data refreshed 2026-09-29, then every 6 hours
- vendor docs verified on 2026-09-29
Spotted something out of date? Tell us — corrections ship same-day.