Is the Teamwork MCP server down?

mcp-registry/com.teamwork/mcp · v1.60.0

Also listed as awesome/teamwork/mcp

healthy
Last checked 2026-10-26 18:03 UTC · handshake 424ms

As of 2026-10-26 18:03 UTC, the Teamwork MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 14 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
99.8%
checks observed
4,905
outages (90d)
14
tools
214

The Teamwork.com official MCP server helps teams efficiently manage client projects with AI.

Point your MCP client at this streamable-http endpoint: https://mcp.ai.teamwork.com

Agent-readiness: B (80/100)

B (80/100): 1 error(s), 3 warning(s) across 214 tool(s); ~71,561 tokens of tool definitions.
Scores higher than 18% of 15,768 MCP servers Glimind has audited.
Its tool list costs an agent ~71,561 tokens per session — more than 99% of servers.
78 → 80 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions73
Safety hints100
Token cost0
Client compatibility100
Protocol100
Reliability100
Stability100

What to fix (4)

Loading this server's tool list costs an agent ~71,561 tokens before any work — more than 99% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

6 tool definition(s) exceed ~1,200 tokens each (largest: twprojects-list_tasks, ~2,540).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~6,659 tokens every session. How to fix →

Tools: twprojects-list_tasks, twprojects-count_tasks, twprojects-list_allocations, twprojects-list_projects, twprojects-update_task and 1 more · saves ~6,659 tokens/session

214 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

73 tool(s) have descriptions under 20 characters.

Say when to use the tool and what it returns, not just its name restated ("Get weather" → "Current weather for a city: temperature, conditions, wind. Use for 'now', not forecasts."). How to fix →

Tools: twdesk-create_customer, twdesk-create_tag, twdesk-create_ticket, twdesk-create_ticket_type, twdesk-get_customer and 68 more

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.teamwork/mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.teamwork/mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.teamwork%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fcom.teamwork%2Fmcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.teamwork%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.teamwork%2Fmcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.teamwork%2Fmcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.teamwork%2Fmcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:c896ad4371eb6f73…, first seen 2026-10-17, included at leaf 14478 of 74,602. Version history · verify what your client received.

Tools (214)

Compare: most reliable communication servers · most reliable other servers · most reliable files servers · most reliable knowledge servers · most reliable productivity servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Teamwork MCP server down right now?

As of 2026-10-26 18:03 UTC, the Teamwork MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 14 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Teamwork MCP server provide?

Teamwork MCP server advertises 214 tools, including twchat-get_conversation, twchat-get_current_user, twchat-get_or_create_dm, twchat-list_conversations, twchat-list_messages.

How do I install Teamwork MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.ai.teamwork.com

Is the Teamwork MCP server safe to connect to an AI agent?

Glimind scanned all 214 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Teamwork MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve