
Connect
Point your client at the server
- Claude Code
- Other clients
Authenticate
The first tool call triggers an OAuth flow in your browser. Log in with the account you use for Squad, approve the request, and the client stores the resulting token. Later sessions reuse it.Four scopes are requested:
read:workspace, write:workspace, openid and email.Land on a workspace
Tools run against one workspace. If your account can reach exactly one, the server selects it on the first call and remembers it. If you can reach more than one, the first call comes back asking for a choice and listing your organisations and workspaces. Your assistant then calls
select_workspace with the IDs.Read scope and write scope
Read tools needread:workspace. Write tools need write:workspace.
Which tools are which is on Tools.
Switching workspace
Switch at any time by asking for another workspace by name. The assistant callslist_workspaces, then select_workspace.
If your access to the selected workspace is revoked, the next call clears the selection and asks you to choose again.
Version compatibility
The hosted server is version 4 and targets the current Squad platform, the one behind app.meetsquad.ai. Version 3 targets the previous Squad product and speaks a different API. Connecting tohttps://mcp.meetsquad.ai/mcp always reaches the current version, so there is nothing to pin.
Prompts
Four ready-made workflows come with the server. Most clients surface them as slash commands or a prompt picker.Resources
Two resources hold workspace context so strategy questions cost no tool calls. Pin them in clients that support resources.Display IDs
Squad entities carry short IDs so your assistant can cite its evidence.SI- signal, IN- insight, AC- action, GL- goal, OP- decision brief, DC- document, CL- cluster. Ask for IN-42 and you get insight 42.
Where to go next
Tool catalogue
All thirty tools, their parameters, and the scope each one needs.
CLI
The same capabilities in a shell.
