# Connect FRM to an AI assistant

Start with this read-only endpoint:

```text
https://cqxvkuvdzjbrnlxgvben.supabase.co/functions/v1/frm-mcp/mcp?mode=read
```

Sign in to FRM through the browser when your AI app requests it. Your assistant can retrieve the records your FRM account can access. Retrieved records are shared with that AI platform. Disconnect apps from FRM → Settings → Connected AI apps.

The read-only URL exposes lookup tools only. Keep that URL in your configuration. The OAuth grant itself is not a distinct read-only grant; a client switching to the update URL can request write tools. Remove `?mode=read` only when you want to enable changes and have reviewed the available tools.

## ChatGPT, Claude, Perplexity

Add a custom remote MCP connector, enter the URL above, select OAuth, then complete FRM sign-in and consent. ChatGPT may require developer mode; organizations may restrict custom connectors. A custom connection and a public directory listing are separate things. Menu names and account availability can change; see the platform links in `catalog.json` or the FRM setup screen.

## Cursor

Merge `frm-cursor-read.json` into `.cursor/mcp.json` under `mcpServers`, then enable FRM and sign in. Keep other server entries.

## GitHub Copilot / VS Code

Merge `frm-vscode-read.json` into `.vscode/mcp.json` under `servers`, start FRM in the MCP server list, and sign in. Use its tools in agent chat.

## Claude Code

Merge `frm-claude-code-read.json` into your project's `.mcp.json`, or run:

```sh
claude mcp add --transport http frm 'https://cqxvkuvdzjbrnlxgvben.supabase.co/functions/v1/frm-mcp/mcp?mode=read'
```

Start Claude Code, run `/mcp`, and authenticate FRM.

## Codex

Merge `frm-codex-read.toml` into `~/.codex/config.toml`, or run:

```sh
codex mcp add frm --url 'https://cqxvkuvdzjbrnlxgvben.supabase.co/functions/v1/frm-mcp/mcp?mode=read'
codex mcp login frm
```

## Gemini CLI

Merge `frm-gemini-read.json` into `~/.gemini/settings.json`, keeping `trust: false`. Start Gemini CLI and run `/mcp auth frm`. This configuration is for Gemini CLI, not the Gemini consumer app.

## Grok API

Use the server-side `grok-readonly.mjs` example from the rollout package. It requires an xAI API key, a model your xAI account can use, and an FRM OAuth token authorized by the user. The example does not implement OAuth sign-in or token refresh for your application. Never use a Supabase service-role key. Keep credentials server-side and out of chat, browser bundles, URLs, and config downloads. API calls incur your provider's charges.

## Muse and Grok Bot

Muse requires FRM publisher onboarding and review at https://platform.muse.ai/. Grok Bot documents a Connect apps directory; an arbitrary custom MCP installation route has not yet been verified. Neither has a confirmed FRM directory listing. FRM can also be used through Grok Bot's browser by signing in directly.

## Verify before using real records

1. Authenticate using a synthetic demo FRM account.
2. Ask “Find Alex Rivera” after adding that sample donor to the demo account.
3. Confirm the result matches FRM and cannot access another organization.
4. Check that the read-only connection exposes no tools that change records.
5. Disconnect it in FRM and verify the platform can no longer use the grant. If an already issued access token remains valid, document its lifetime and fix revocation behavior before promising immediate cutoff.

Protocol support and configuration files do not by themselves establish an end-to-end working connection. Each platform needs its own sign-in and test.
