list_workspacesLABSCO SUMMARY
Display ids exist so the assistant can show its work.
Prefixed identifiers — SI- for a signal, IN- for an insight, AC- for an action — let a model cite the exact evidence behind a claim instead of summarising it into something unverifiable. That is the difference between a product assistant you can check and one you have to trust. The ground-this-ticket prompt points at the same idea from the other end: before a coding agent builds something, pull the customer evidence for why. Writes are scope-gated, so a read-only token is a real option.
What it is
A hosted MCP server for Squad, which ingests user feedback, clusters it into signals, distils insights, and links those to the actions and goals a product team works on. Its README puts the tool count at about 35, and every entity has a short display id so an assistant can cite what it is claiming.
What you get
- Orientation —
list_workspaces,select_workspace,get_workspace_overview,update_workspace,list_members - Retrieval across everything:
searchfor semantic search andget_entityto fetch any object by its display id or UUID - The evidence layer —
list_signals,find_similar_signals,list_clusters,get_cluster,list_insights - Work tracking through
list_actions,get_action_context,update_actionandupdate_action_status - Strategy —
list_goals,create_goal,update_goal,update_insight,dismiss_signal,get_activity ingest_signal— captures new feedback with deduplication, so a support ticket lands as a signal and you are told whether it is a known theme- Briefs and knowledge:
generate_brief,list_briefs,update_brief_status, pluslist_documents,create_document,update_document - Four prompts that compose the tools —
triage-feedback,weekly-product-review,draft-decision-brief, andground-this-ticketfor coding agents - Two pinnable resources:
squad://workspace/contextfor mission and product context,squad://goalsfor ranked strategic goals - Safety annotations on every tool, marking which are read-only and which are destructive
Requirements
A Squad account. Connect with claude mcp add --transport http squad https://mcp.meetsquad.ai/mcp and complete OAuth in the browser on first use; other clients discover the OAuth configuration automatically from the server's protected-resource metadata. Nothing runs locally. Scopes matter: read tools need read:workspace and write tools need a token minted with write:workspace. Self-hosting is not expected — this is a hosted service — but the source is here, built on Node.js 22+ with pnpm. MIT licensed.
Setup effort
One command — claude mcp add --transport http squad https://mcp.meetsquad.ai/mcp
USE CASES
Triaging a support ticket
Capture it as a signal with deduplication and find out immediately whether it is a known theme or something new.
Checking the evidence behind a decision
Open the insight and read the customer signals and clusters it was built from, rather than taking the summary on faith.
Running the weekly product review
Read what changed, what the evidence says and what needs deciding, in one pass over activity, insights and actions.
Writing a decision brief
Generate a brief from the action or insight it belongs to, then move its status as it progresses.
Grounding a ticket before building it
Pull the customer evidence behind the action so the implementation answers the actual complaint.
Keeping strategy visible to the agent
Pin the workspace context and ranked goals as resources so strategy questions need no tool calls at all.
30 tools
Listed in project docs. Your client may show a different list.
select_workspaceget_workspace_overviewupdate_workspacelist_memberssearchget_entitylist_signalsfind_similar_signalslist_clustersget_clusterlist_insightslist_actionsget_action_contextupdate_actionupdate_action_statuslist_goalscreate_goalupdate_goalupdate_insightdismiss_signalget_activitylist_documentscreate_documentupdate_documentlist_briefsgenerate_briefupdate_brief_statusingest_signallist_integrationsBEFORE YOU INSTALL
What to know first
Tools you get
30 tools named in the project's documentation.
INSTALLATION
Connect your client
Server setup
Setup
Claude Code
Claude Code:
claude mcp add --transport http squad https://mcp.meetsquad.ai/mcpOn first use, authenticate via OAuth in your browser when prompted
Other MCP clients: connect to https://mcp.meetsquad.ai/mcp — OAuth config is discovered from the server's .well-known/oauth-protected-resource metadata
Hosted endpoint
https://mcp.meetsquad.ai/mcpAdd this hosted endpoint to your MCP client.
MCP Clients
Any MCP client
URL: https://mcp.meetsquad.ai/mcp
Auth: OAuth configuration is automatically discovered via the server's .well-known/oauth-protected-resource metadata