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

# Quickstart: Grok

> Add the hosted SuprSend MCP server to Grok as a custom connector, or to Grok Build from the command line, and sign in with your SuprSend account.

## Set up the connection

<Tabs>
  <Tab title="Grok">
    <Steps>
      <Step title="Add the SuprSend MCP server">
        Go to [grok.com/connectors](https://grok.com/connectors), click **New Connector**, and select **Custom**. Paste `https://mcp.suprsend.com/mcp` as the MCP server URL.

        On Grok Business and Enterprise, a team admin must provision the connector first.
      </Step>

      <Step title="Sign in with your SuprSend account">
        Complete the sign-in when Grok asks. Sign in with your SuprSend account. The agent gets the same permissions your role has in the SuprSend dashboard.
      </Step>

      <Step title="Verify the connection">
        In a new chat, ask:

        ```
        List my SuprSend workspaces.
        ```

        Grok answers with your SuprSend workspaces.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Grok Build">
    <Steps>
      <Step title="Add the SuprSend MCP server">
        ```bash theme={"system"}
        grok mcp add --transport http suprsend https://mcp.suprsend.com/mcp
        ```

        To add the server for one repo only, add `--scope project`.
      </Step>

      <Step title="Sign in with your SuprSend account">
        Start Grok Build, run `/mcps`, select **suprsend**, and press `i`. Grok Build opens your browser. Sign in with your SuprSend account. The agent gets the same permissions your role has in the SuprSend dashboard.
      </Step>

      <Step title="Verify the connection">
        In a Grok Build session, ask:

        ```
        List my SuprSend workspaces.
        ```

        Grok Build answers with your SuprSend workspaces.
      </Step>
    </Steps>
  </Tab>
</Tabs>

## Pin a workspace and restrict tools

By default, Grok and Grok Build can use every workspace and tool your role allows. To keep them on one workspace, or to give them only the tools a job needs, use one of these URLs when you add the server:

* **Pin a workspace** by adding its slug to the path. The agent then can't switch to another workspace:

  ```
  https://mcp.suprsend.com/mcp/staging
  ```

* **Restrict tools** with `?tools=`, a comma-separated list of tool names or groups:

  ```
  https://mcp.suprsend.com/mcp/staging?tools=users_*,data_*
  ```

See [Scope the connection](/reference/mcp-overview#scope-the-connection) for every URL pattern, and the [tool list](/reference/mcp-tool-list) for every tool.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Grok Build can't reach the server">
    Run `grok mcp doctor suprsend`. It checks the server's configuration and connection, and tells you what to fix.
  </Accordion>

  <Accordion title="Server shows disconnected or refuses the connection">
    Check the workspace slug in the URL. It must match a workspace in your SuprSend account exactly, for example `staging`, not the workspace's display name. A slug that doesn't exist fails with `403 workspace_forbidden`. To see your slugs, remove the slug, reconnect, and ask: "List my SuprSend workspaces."
  </Accordion>
</AccordionGroup>

<CardGroup cols={2}>
  <Card title="Tool list" icon="list" href="/reference/mcp-tool-list">
    Every tool, grouped by category, with read vs write labels.
  </Card>

  <Card title="Prompt cheatsheet" icon="message" href="/reference/mcp-prompts">
    Ready-to-use prompts to get started fast.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.