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

# Claude

> Use Claude with FITsociety MCP as a custom connector.

Use this guide when you want Claude to call FITsociety MCP tools through a
remote custom connector.

## Prerequisites

Before connecting, make sure:

* your company has the `mcp` feature enabled
* a Manager or Admin coach has created an MCP grant (OAuth consent or a static
  MCP API key) for the access you need

See [Setup for Coaches](/mcp/setup-for-coaches) for how to enable the feature
and create a grant.

## Server URL

```text theme={null}
https://mcp.fitsociety.io/mcp/v1
```

## Add the connector

In Claude:

1. Open **Customize > Connectors**.

2. Click **Add custom connector**.

3. Enter a name such as `FITsociety MCP`.

4. Enter the remote MCP URL:

   ```text theme={null}
   https://mcp.fitsociety.io/mcp/v1
   ```

5. Save the connector and complete the FITsociety authorization flow.

Team or Enterprise workspaces may require an admin to enable custom connectors
before users can add them.

## Authentication

Use OAuth when Claude opens the FITsociety consent flow. The authorizing coach
chooses the company, modules, write tools, and special consent flags.

If Claude asks for advanced OAuth settings, use the values exposed by the
FITsociety discovery endpoints:

```text theme={null}
https://mcp.fitsociety.io/.well-known/oauth-protected-resource/mcp/v1
https://mcp.fitsociety.io/.well-known/oauth-authorization-server
```

## Verify

Ask Claude:

```text theme={null}
List the FITsociety tools you can use and group them by module.
```

Then test a safe read-only request:

```text theme={null}
Search for a client by email in FITsociety.
```