> ## Documentation Index
> Fetch the complete documentation index at: https://docs.meetsquad.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Squad MCP server

> Connect Claude, ChatGPT or any MCP client to Squad over OAuth and work signals, insights, actions and briefs from your assistant.

<img className="block dark:hidden" src="https://mintcdn.com/squad/O_98Wy8uNjlYcgBb/images/hero-mcp-light.png?fit=max&auto=format&n=O_98Wy8uNjlYcgBb&q=85&s=6fe3fd9448ae406dbf84695437c5c59a" alt="Squad MCP" width="2400" height="720" data-path="images/hero-mcp-light.png" />

<img className="hidden dark:block" src="https://mintcdn.com/squad/O_98Wy8uNjlYcgBb/images/hero-mcp-dark.png?fit=max&auto=format&n=O_98Wy8uNjlYcgBb&q=85&s=b121892e20bc1ce12f8345b567a5889c" alt="Squad MCP" width="2400" height="720" data-path="images/hero-mcp-dark.png" />

Squad runs a hosted MCP server. Point an MCP client at it, authenticate once in your browser, and your assistant can read the evidence behind any decision, capture new feedback, and generate decision briefs without leaving the conversation.

## Connect

<Steps>
  <Step title="Point your client at the server" icon="link">
    ```
    https://mcp.meetsquad.ai/mcp
    ```

    Streamable HTTP transport. There is nothing to install and nothing to self-host.

    <Tabs>
      <Tab title="Claude Code">
        ```bash theme={null}
        claude mcp add --transport http squad https://mcp.meetsquad.ai/mcp
        ```
      </Tab>

      <Tab title="Other clients">
        Other clients take the URL directly. OAuth configuration is discovered from the server's `.well-known/oauth-protected-resource` metadata, which names the authorization server, so most clients need no further configuration.
      </Tab>
    </Tabs>
  </Step>

  <Step title="Authenticate" icon="key-round">
    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`.
  </Step>

  <Step title="Land on a workspace" icon="folder-tree">
    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.
  </Step>
</Steps>

## Read scope and write scope

Read tools need `read:workspace`. Write tools need `write:workspace`.

<Warning>
  The scope check happens when a tool is called, not when tools are listed. A read-scoped session still sees every write tool in `tools/list`, and the call fails at execution with a message saying the token does not include `write:workspace` and to reconnect with write access. If your assistant reports that a write tool is unavailable, the fix is reconnecting with write scope, not retrying.
</Warning>

Which tools are which is on [Tools](/mcp/tools).

## Switching workspace

Switch at any time by asking for another workspace by name. The assistant calls `list_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](https://app.meetsquad.ai). Version 3 targets the previous Squad product and speaks a different API. Connecting to `https://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.

| Prompt                  | What it runs                                                                             |
| ----------------------- | ---------------------------------------------------------------------------------------- |
| `triage-feedback`       | Checks for duplicates, ingests a piece of feedback, reports where it landed              |
| `weekly-product-review` | What changed, what the evidence says, what needs deciding                                |
| `draft-decision-brief`  | Generates a brief from an action or insight and walks it to a readable draft             |
| `ground-this-ticket`    | For coding agents: pulls the customer evidence behind a piece of work before building it |

## Resources

Two resources hold workspace context so strategy questions cost no tool calls. Pin them in clients that support resources.

| URI                         | Contents                                            |
| --------------------------- | --------------------------------------------------- |
| `squad://workspace/context` | The current workspace's mission and product context |
| `squad://goals`             | Strategic goals with importance rankings            |

## 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

<CardGroup cols={3}>
  <Card title="Tool catalogue" icon="wrench" href="/mcp/tools">
    All thirty tools, their parameters, and the scope each one needs.
  </Card>

  <Card title="CLI" icon="terminal" href="/cli/overview">
    The same capabilities in a shell.
  </Card>
</CardGroup>