---
title: "MCP Servers"
canonical_url: https://developer.repebble.com/index-01/mcp/
last_updated: 2026-10-06
sdk_version: 4.44
---
# MCP Servers

Source: https://developer.repebble.com/index-01/mcp/

The Index 01 assistant calls tools through the [Model Context Protocol](https://modelcontextprotocol.io). The built-in actions (notes, reminders, timers, calendar, messaging) are MCP servers inside the Pebble mobile app. You can add your own server over HTTP, and the assistant lists its tools and calls them when a recording asks for something they do.

The MCP client is in `mcp/src/commonMain/kotlin/coredevices/mcp/client/` and the settings screens are in `experimental/src/commonMain/kotlin/coredevices/ring/ui/screens/settings/mcp/` of [github.com/coredevices/mobileapp](https://github.com/coredevices/mobileapp).

## Requirements

- The server speaks MCP over HTTP with either the SSE transport or the Streamable HTTP transport. Pick the matching one when you add the server.
- The URL is reachable from the phone. Use HTTPS unless the server is on the same local network as the phone.
- Authentication, if any, is a single static `Authorization` header value. OAuth flows are not supported.
- `tools/list` returns every tool in one page. The app does not follow `nextCursor`.
- Prompts are optional. Only prompts without arguments are offered, and only the text of the first message of a prompt is used.
- Servers are called by a cloud model. See [Cloud LLM Only](#cloud-llm-only).

## Adding a Server

In the Pebble mobile app:

- Open the Index 01 settings and tap _MCP & Tool Settings_.
- Open the _MCP Servers_ tab and tap _Add MCP Server_.
- Enter a _Name_. Letters, digits, `-` and `_` only, up to 32 characters. The name identifies the server in the app and in tool names.
- Enter the _URL_. The app connects as you type, shows the server's title under the field when the connection works, and shows the error when it does not. A server that cannot be reached can still be saved.
- Choose _SSE_ or _Streamable_ to match the server's transport. _SSE_ is the default.
- Under _Groups_, pick the sandbox groups the server belongs to. See [Sandbox Groups](#sandbox-groups).
- To authenticate, expand _Authorization (optional)_ and enter the full header value, for example `Bearer token123`.
- If the server offers prompts, expand _Prompts_ and select the ones to include.
- Tap _Save_.

Edit a server by tapping it in the list. _Delete_ removes it from every group.

### The Authorization Header

The value you enter is sent as the `Authorization` header on every request the app makes to the server, including the connection check in the dialog, as entered. Include the scheme, so `Bearer <token>` rather than the bare token. The app does not refresh or rotate it. Leave the field empty for a server without authentication.

### Prompts and Instructions

The `instructions` string a server returns from `initialize` is added to the assistant's context whenever the server is in the active group. Prompts you select in the dialog are fetched with `prompts/get` and appended after the instructions. Use them for standing guidance on when and how to call the server's tools.

### Caching

The app caches `tools/list` and `prompts/list` results. If the server declares `listChanged` for tools or prompts, the cache lasts one hour and is cleared when the server sends the corresponding `notifications/*/list_changed` notification. Otherwise it lasts five minutes.

## Sandbox Groups

A sandbox group is a set of MCP servers and the model that runs them. The _Groups_ tab in _MCP & Tool Settings_ lists them. Every phone has a group named _Default MCP Sandbox_ that runs the Index agent with the built-in actions; servers you add to it are available to a gesture routed to _Index agent_. You can also create your own groups and route a recording gesture to one by choosing _MCP sandbox_ on the _Ring Button_ screen.

Each group has a _Model Type_:

| Model type | Behaviour |
| --- | --- |
| Index Agent | The default Index assistant. Understands notes and the built-in actions. Cannot be customised. |
| Default | Fast at intent recognition. Fine for most tool sets. |
| High Capability | Slower. Better with large numbers of tools and more complex tasks. |

Deleting a group does not delete its servers; they can be added to other groups.

## Cloud LLM Only

Remote MCP servers are always called by a cloud model. The _Agent Model_ setting in the Index 01 settings applies to the Index agent, which is what runs the _Default MCP Sandbox_ group and any group whose model type is _Index Agent_:

- With _Cloud LLM_ or _Cloud LLM (with Local fallback)_, HTTP servers in the default group are available to the Index agent.
- With _Local LLM_, HTTP servers in the default group are shown as disabled with the reason "Remote MCP servers need the Cloud LLM". The on-device model also does not support every built-in action.
- The _Local LLM_ options cannot be selected while the default group's model type is _Default_ or _High Capability_. Changing the default group to one of those model types switches _Agent Model_ back to _Cloud LLM_.

Groups with the _Default_ or _High Capability_ model type run in the cloud whatever _Agent Model_ is set to, and a gesture can be routed to them under any setting. They need a signed-in Pebble account.
