Agent MCP Directory

Teamwork.com: MCP server, CLI and agent surfaces

Sign-in required, tools not seen, not counted. The MCP endpoint listed for Teamwork.com at mcp.ai.teamwork.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in.

Fact sheet

CompanyTeamwork.com
Domainteamwork.com
CategoryDeveloper Tools (Ora leaderboard category)
MCP serverSign-in required (OAuth with client registration)
Ora score68, grade C; Ora scanned the domain on 21 October 2026 and the cached score was read on 5 November 2026 from Ora's leaderboard (Ora's score page for teamwork.com, a vendor-published score)
Company found throughOra's public leaderboard
Last verified4 November 2026

MCP server

Endpointhttps://mcp.ai.teamwork.com/sse
How it was foundlisted in Ora's public leaderboard
Transportsse
HTTP status401
Connected4 November 2026, 20:04 UTC
Handshake time918 ms over 2 attempts

The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools.

Connector log

4 connections on 4 November 2026, read-only methods only

  • 19:59:51Z https://mcp.ai.teamwork.com sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result initialized-no-tools (HTTP 200) 1664 ms
  • 19:59:52Z https://mcp.ai.teamwork.com/sse sent initialize result auth-required (HTTP 401) 950 ms
  • 20:04:51Z https://mcp.ai.teamwork.com sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result initialized-no-tools (HTTP 200) 4284 ms
  • 20:04:52Z https://mcp.ai.teamwork.com/sse sent initialize result auth-required (HTTP 401) 918 ms

Authentication

Auth typeOAuth with client registration
What the challenge saidBearer resource_metadata="https://mcp.ai.teamwork.com/.well-known/oauth-protected-resource"
Protected resource metadatamcp.ai.teamwork.com
Authorization server metadatateamwork.com
Registration endpointhttps://www.teamwork.com/developer/api/v1/apps/register.json

The sign-in route, step by step

  1. Request https://mcp.ai.teamwork.com/sse without a token. It answers 401 and a WWW-Authenticate header.
  2. Read the protected resource metadata at https://mcp.ai.teamwork.com/.well-known/oauth-protected-resource to find the authorization server.
  3. Register a client at the registration endpoint https://www.teamwork.com/developer/api/v1/apps/register.json (dynamic client registration), so no human has to create an app first.
  4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes.

See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.

CLI

No CLI is on record for Teamwork.com. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See shipping a CLI agents can use.

Other agent surfaces

Agent surfaces other than MCP and CLI
SurfaceResult
OpenAPI fileNo OpenAPI file at the root paths checked.
WebMCP in the initial HTMLNot detected on the home page by the shared crawl.
MCP discovery fileFound: teamwork.com/.well-known/mcp.json answered with a valid document in the shared crawl.
A2A agent cardNot found (the crawl got a non-200 answer).
A2A agent card (older path)Found: teamwork.com/.well-known/agent.json answered with a valid document in the shared crawl.
agents.jsonNot found (the crawl got a non-200 answer).
OAuth authorization server metadataFound: teamwork.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl.
NLWeb endpointNot checked in this edition.

Registry listings

Registry listings
RegistryListed
Official MCP RegistryYes: com.teamwork/mcp
GitHub MCP RegistryNo
awesome-remote-mcp-serversNo
SmitheryNot checked: Smithery's listing pages and search API were unavailable on 4 November 2026.
GlamaNot checked: Glama's API needs a key and attribution terms.