Teamwork.com MCP (official, remote)
Score = points from 5 automated checks. Not a quality or security rating. Methodology
- Install20/20
- Handshake5/30
- Maintenance25/25
- Docs10/15
- License10/10
Vendor-hosted
Transport (tested 2026-10-31): Streamable HTTP
Score 70/100 · Tools — · Token cost — · Compare · Last tested 2026-10-31 · Server version 1.60.1 · Remote endpoint https://mcp.ai.teamwork.com (streamable-http) · Repo teamwork/mcp
Summary: Teamwork.com MCP (official, remote) requires credentials or a backing service before it will list tools.
Evidence summary
- Handshake
- auth-gated
- Tools listed
- —
- Context cost
- Not measured ranking
- Login
- Needs OAuth sign-in
- Tested
- 2026-10-31
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | Endpoint https://mcp.ai.teamwork.com reachable over streamable-http (HTTP 200) in 0.1s; no install step for remote servers. |
| handshake | auth-gated | 5 | Needs credentials: vendor-hosted, OAuth sign-in required. MCP initialize completed without sign-in (protocol 2025-06-18, server Teamwork.com 1.60.1), but tools/list was refused: HTTP 401 with OAuth challenge (WWW-Authenticate resource_metadata https://mcp.ai.teamwork.com/.well-known/oauth-protected-resource; metadata lists authorization server https://teamwork.com). We do not sign in; not counted as working until a credentialed test exists. |
| maintenance | pass | 25 | Repo pushed 0 days before test; 28 GitHub stars. |
| docs | partial | 10 | README over 3,000 chars; install instructions present. Automated check of the package's own README (vendor repo README (github.com/teamwork/mcp)). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Not yet tested (no tools/list response without credentials).
What we tested and what we didn't
Tested on 2026-10-31
- Install from the registry (remote endpoint: connection only)
- We connected with no credentials: MCP initialize completed, but our tools/list request answered HTTP 401 and asked for sign-in, so it never returned a tool list and we list no tools (Method details:
initializesucceeded;tools/listanswered 401) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that it is safe to give it access to your data.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
No tool list: this server did not list tools without credentials in our test, so tool changes are not tracked.
Raw test record (JSON)
{
"name": "teamwork-remote",
"version": null,
"registry": "remote",
"status": "auth-gated",
"tested": "2026-10-31",
"tools_count": null,
"tools_schema_tokens_est": null,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"Endpoint https://mcp.ai.teamwork.com reachable over streamable-http (HTTP 200) in 0.1s; no install step for remote servers."
],
"handshake": [
"auth-gated",
5,
"Needs credentials: vendor-hosted, OAuth sign-in required. MCP `initialize` completed without sign-in (protocol 2025-06-18, server Teamwork.com 1.60.1), but `tools/list` was refused: HTTP 401 with OAuth challenge (WWW-Authenticate resource_metadata https://mcp.ai.teamwork.com/.well-known/oauth-protected-resource; metadata lists authorization server https://teamwork.com). We do not sign in; not counted as working until a credentialed test exists."
],
"maintenance": [
"pass",
25,
"Repo pushed 0 days before test; 28 GitHub stars."
],
"docs": [
"partial",
10,
"README over 3,000 chars; install instructions present. Automated check of the package's own README (vendor repo README (github.com/teamwork/mcp))."
],
"license": [
"pass",
10,
"MIT (OSI-approved)."
]
}
}Install
https://mcp.ai.teamwork.com
Tools listed
Not available (handshake did not complete without credentials).
Quick config
{
"mcpServers": {
"teamwork-com-mcp-official-remote": {
"type": "http",
"url": "https://mcp.ai.teamwork.com"
}
}
}Add to config Opens the config generator with this server selected.
Setup
Without credentials it said (verbatim): Needs credentials: vendor-hosted, OAuth sign-in required. MCP `initialize` completed without sign-in (protocol 2025-06-18, server Teamwork.com 1.60.1), but `tools/list` was refused: HTTP 401 with OAuth challenge (WWW-Authenticate resource_metadata https://mcp.ai.teamwork.com/.well-known/oauth-protected-resource; metadata lists authorization server https://teamwork.com). We do not sign in; not counted as working until a credentialed test exists.
- Install. No install step: it is a remote server at https://mcp.ai.teamwork.com.
- Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools. In our test it did not list tools without credentials.
{
"mcpServers": {
"teamwork-com-mcp-official-remote": {
"type": "http",
"url": "https://mcp.ai.teamwork.com"
}
}
}Not tested with credentials We have not tested this with real credentials.
Test history
No dated events yet.
Related: MCP servers that need an OAuth sign-in · How to secure AI API keys
FAQ
Is Teamwork.com MCP (official, remote) deprecated?
No. teamwork-remote was not deprecated or archived when we last tested it on 2026-10-31.
What replaces Teamwork.com MCP (official, remote)?
Nothing; Teamwork.com MCP (official, remote) is not deprecated as of 2026-10-31.
Does Teamwork.com MCP (official, remote) need an API key?
Not an API key: it needs an OAuth sign-in. Without signing in, the endpoint returned HTTP 401 with an OAuth challenge and did not list tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.