> For the complete documentation index, see [llms.txt](https://api-docs.realfinity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api-docs.realfinity.io/mcp/connecting/clients-and-configuration.md).

# Clients & Configuration

This page covers wiring each client up to the server. For details on the OAuth sign-in flow itself, see [Authentication](/mcp/connecting/authentication.md).

Every client below uses the same production endpoint, with UAT available as an alternative for testing against non-production data:

* **Production:** `https://ai.realfinity.io/mcp`
* **UAT:** `https://ai-uat.realfinity.io/mcp`

## claude.ai

1. Go to the connectors settings in claude.ai and add a **custom connector**.
2. Set the transport to **Streamable HTTP**.
3. Enter the URL: `https://ai.realfinity.io/mcp` (or the UAT URL to test against non-production data).
4. Save the connector. OAuth is discovered automatically from the server — you don't need to configure a client ID or secret yourself.
5. When prompted, sign in with a Realfinity account.

## Claude Desktop

Add a **remote MCP server** entry pointing at the same production URL, `https://ai.realfinity.io/mcp` (or the UAT URL). Claude Desktop will walk you through the OAuth sign-in the first time it connects.

## MCP Inspector

[MCP Inspector](https://github.com/modelcontextprotocol/inspector) is the official browser-based debugger for MCP servers. It's useful for testing the tools end-to-end, including the OAuth flow, before wiring the server into another client.

1. Launch Inspector:

   ```bash
   npx @modelcontextprotocol/inspector
   ```

   It opens in your browser, typically at `http://localhost:6274`.
2. Configure authentication:
   * Client ID: `[In Keeper]`
   * Client Secret: `[In Keeper]`
3. Configure the connection:
   * **Transport:** `Streamable HTTP`
   * **URL:** `https://ai.realfinity.io/mcp` (or the UAT URL)
4. Click **Connect**, then sign in with your Realfinity account.
5. Click **List Tools**. You should see all 24 tools the server exposes.

## Local development

To run the MCP server on your own machine instead of connecting to a hosted environment:

```bash
dotnet run --project MCP/Realfinity.Mcp/src/Realfinity.Mcp.csproj
```

The server binds to `https://localhost:7003` / `http://localhost:8003`. Point any client at `http://localhost:8003/mcp`.

Two things trip people up here:

* **`appsettings.json` is the staging baseline**, not a Development default — there is no `appsettings.staging.json`. If you need UAT or production settings locally, the overrides are `appsettings.uat.json` and `appsettings.prod.json`.
* **There is no `Development` launch profile.** The available profiles are `Staging` (the default), `Uat`, and `Production`.