> ## 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: Gemini CLI

> Add the hosted SuprSend MCP server to Gemini CLI in ~/.gemini/settings.json and sign in with your SuprSend account.

## Set up the connection

<Steps>
  <Step title="Add the SuprSend MCP server">
    Open `~/.gemini/settings.json`. If the file doesn't exist yet, create it first with `touch ~/.gemini/settings.json`.

    ```bash theme={"system"}
    open ~/.gemini/settings.json
    ```

    Add:

    ```json theme={"system"}
    {
      "mcpServers": {
        "suprsend": {
          "httpUrl": "https://mcp.suprsend.com/mcp"
        }
      }
    }
    ```

    The field name is `httpUrl`, not `url`. Gemini Code Assist reads the same file, so the server works there too.
  </Step>

  <Step title="Sign in with your SuprSend account">
    Start Gemini CLI and run:

    ```
    /mcp auth suprsend
    ```

    Gemini CLI 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 Gemini CLI session, ask:

    ```
    List my SuprSend workspaces.
    ```

    Gemini answers with your SuprSend workspaces.
  </Step>
</Steps>

## Pin a workspace and restrict tools

By default, Gemini CLI can use every workspace and tool your role allows. To keep it on one workspace, or to give it only the tools a job needs, change `httpUrl` in your settings:

* **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_*
  ```

You can also hide tools locally with Gemini's `includeTools` and `excludeTools` fields. Keep `trust` off: it skips Gemini's confirmation before each tool call.

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="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.