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

# MCP server

> Connect MobileBoost to Cursor, Claude Code, and other MCP clients

The MobileBoost MCP server lets your AI coding agent call MobileBoost directly: list and edit tests, trigger test runs, and check run status without leaving your editor. Any client that supports the [Model Context Protocol](https://modelcontextprotocol.io) can connect to it.

## Prerequisites

* A MobileBoost account
* An MCP-compatible client (Cursor, Claude Code, Claude Desktop, or any other MCP client)

## Server details

| Field             | Value                                   |
| ----------------- | --------------------------------------- |
| URL               | `https://api.mobileboost.io/mcp`        |
| Transport         | Streamable HTTP                         |
| Authentication    | OAuth 2.1 (browser sign-in, no API key) |
| Protocol revision | `2025-06-18`                            |

## Integrate the server

Pick your client below and follow the steps. The first time you connect, your browser opens a MobileBoost sign-in page; after that, the client refreshes tokens automatically.

<Tabs>
  <Tab title="Cursor">
    <Steps>
      <Step title="Open the MCP configuration">
        In Cursor, open **Settings → MCP → Add new MCP server**, or edit `~/.cursor/mcp.json` directly.
      </Step>

      <Step title="Add the MobileBoost server">
        Paste the following entry:

        ```json theme={null}
        {
          "mcpServers": {
            "mobileboost": {
              "url": "https://api.mobileboost.io/mcp"
            }
          }
        }
        ```
      </Step>

      <Step title="Sign in">
        Save the file. Cursor opens a browser tab — sign in with your MobileBoost account and approve the requested scopes. The server then shows up with a green status indicator under **Settings → MCP**.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Claude Code">
    <Steps>
      <Step title="Add the server with the CLI">
        ```bash theme={null}
        claude mcp add --transport http mobileboost https://api.mobileboost.io/mcp
        ```
      </Step>

      <Step title="Sign in">
        Claude Code opens your browser on first use. Sign in to MobileBoost and approve access.
      </Step>

      <Step title="Verify the connection">
        ```bash theme={null}
        claude mcp list
        ```

        The `mobileboost` entry should report as connected.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Claude Desktop">
    Add MobileBoost as a [custom connector](https://support.claude.com/en/articles/11175166) - no config file editing needed.

    <Steps>
      <Step title="Open Connectors settings">
        In Claude Desktop, click your profile icon and choose **Settings**, then go to **Connectors** in the sidebar. You can also open it directly at [claude.ai/customize/connectors](https://claude.ai/customize/connectors).
      </Step>

      <Step title="Add a custom connector">
        Scroll to the bottom of the connector list and click **Add custom connector**.
      </Step>

      <Step title="Enter the MobileBoost URL">
        In the **Remote MCP server URL** field, paste:

        ```
        https://api.mobileboost.io/mcp
        ```

        Leave **Advanced settings** untouched. MobileBoost uses Dynamic Client Registration, so no OAuth client ID or secret is required.
      </Step>

      <Step title="Save and connect">
        Click **Add** to save the connector, then click **Connect** next to MobileBoost in the list. A browser window opens for you to sign in to MobileBoost and approve the requested scopes.
      </Step>

      <Step title="Enable in chat">
        Open a new chat, click the **+** button in the message composer, choose **Connectors**, and toggle **MobileBoost** on.
      </Step>
    </Steps>

    <Note>
      Custom connectors connect from Anthropic's cloud, not your local machine. The MobileBoost MCP server is publicly reachable, so this works out of the box.
    </Note>

    <Info>
      On Team and Enterprise plans, an Owner must first add the connector under **Organization settings → Connectors** before members can connect to it.
    </Info>
  </Tab>

  <Tab title="VS Code">
    <Steps>
      <Step title="Create the MCP config">
        In your project root, create `.vscode/mcp.json`:

        ```json theme={null}
        {
          "servers": {
            "mobileboost": {
              "type": "http",
              "url": "https://api.mobileboost.io/mcp"
            }
          }
        }
        ```
      </Step>

      <Step title="Start the server">
        Open the Command Palette and run **MCP: List Servers**, select **mobileboost**, and click **Start**. VS Code opens your browser to complete sign-in.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Other clients">
    Any MCP-compatible client can connect to MobileBoost. Use:

    * **URL**: `https://api.mobileboost.io/mcp`
    * **Transport**: Streamable HTTP

    For clients that only support stdio, use the `mcp-remote` bridge:

    ```bash theme={null}
    npx -y mcp-remote https://api.mobileboost.io/mcp
    ```

    The client (or `mcp-remote`) discovers the authorization server, registers itself, and runs the browser sign-in flow automatically.
  </Tab>
</Tabs>

## Verify the integration

Once connected, ask your agent something that requires MobileBoost data, for example:

```
List my MobileBoost tests.
```

The agent should call `list_tests` and return your tests. If the call fails with an authentication error, sign out and reconnect from your client's MCP settings.

## Available tools

The server exposes the following tools, all scoped to your MobileBoost organisation:

| Tool                  | Scope       | Description                                                                  |
| --------------------- | ----------- | ---------------------------------------------------------------------------- |
| `list_tests`          | `mcp:read`  | List tests with id, title, tags, and last update time.                       |
| `get_test`            | `mcp:read`  | Fetch a single test by id, including its commands.                           |
| `create_test`         | `mcp:write` | Create a new test with a title and a list of commands.                       |
| `update_test`         | `mcp:write` | Replace the commands of an existing test.                                    |
| `delete_test`         | `mcp:write` | Delete one or more tests.                                                    |
| `execute_tests`       | `mcp:write` | Trigger a test suite run by `testIds` or `tags`. Returns a `testSuiteRunId`. |
| `get_test_run_status` | `mcp:read`  | Fetch the status and summary of a previously-started run.                    |

Read-only clients that only request `mcp:read` see the four read tools and have the write tools hidden.

## Scopes

The server defines two OAuth scopes:

* `mcp:read` — list and read tests and runs
* `mcp:write` — create, update, delete, and execute tests

Most clients request both by default. To restrict an agent to read-only access, set the scope explicitly in your client config (see your client's documentation for the exact field).