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

# Regional MCP servers

> Each OnboardMe region has its own MCP server and sign-in. Use the one that matches the practice.

Every OnboardMe practice is hosted in exactly one region. Each region runs its own MCP server, and that server only talks to its own region's API. There is no cross-region routing.

## Servers by region

| Region | MCP server URL | Partner API and sign-in server | OnboardMe app |
| - | - | - | - |
| Australia & New Zealand | `https://anzmcp.onboardme.app/mcp` | `https://anzapi.onboardme.app` | `https://anz.onboardme.app` |
| United Kingdom | `https://ukmcp.onboardme.app/mcp` | `https://ukapi.onboardme.app` | `https://uk.onboardme.app` |
| South Africa | `https://zamcp.onboardme.app/mcp` | `https://zaapi.onboardme.app` | `https://za.onboardme.app` |

Enter the MCP server URL exactly as shown, including `/mcp` and with no trailing slash. The URL is also the OAuth resource identifier, so a different spelling makes sign-in fail.

## Pick the right region

Use the region where the practice signs in to OnboardMe. If your staff sign in at `uk.onboardme.app`, use `https://ukmcp.onboardme.app/mcp`.

If you connect to the wrong region:

* **Sign in with OnboardMe** sends you to that region's login page. Your account will not be found there, or you will not see your practice.
* **API key** connections fail with `401`, because the key belongs to a practice in another region.

## How sign-in stays in region

Each MCP server publishes OAuth metadata at `/.well-known/oauth-protected-resource/mcp`. That metadata names the regional API as the only authorization server:

```json theme={null}
{
  "resource": "https://ukmcp.onboardme.app/mcp",
  "authorization_servers": ["https://ukapi.onboardme.app"],
  "scopes_supported": ["onboardme.read", "onboardme.write"]
}
```

The regional API issues the access token, and only for its own MCP server. A token from one region is rejected by every other region's server.

## Several regions

If you work with practices in more than one region, add one connection per region and give each a clear name, for example **OnboardMe ANZ** and **OnboardMe UK**. Each connection signs in separately.

<Note>
  Practices do not span regions, and the MCP server does not copy data between regions. Requests go from your assistant to the regional MCP server, then to the same region's API.
</Note>

For the Partner API itself, see [Regions](/concepts/regions).


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