FRM + Grok API
Connect FRM to Grok API.
xAI’s Responses API supports remote MCP. A backend must supply a user-authorized FRM OAuth token; this is separate from a grok.com directory listing.
Your connection guide
Set up your API integration
Use the server-side example in the FRM connector rollout package.
Obtain a FRM token through your application’s OAuth flow. Store it server-side and handle refresh and revocation.
Use the read-only URL and allow only the required lookup tools. xAI does not currently support require_approval, so this example does not expose write tools.
Keep credentials on your server.
Your backend needs an xAI API key and a user-authorized FRM OAuth token, including refresh and revocation handling. Keep credentials out of browser code, chat, URLs, and configuration downloads. Never use a Supabase service-role key for this connection. Provider API charges apply.
This is a documented connection route. FRM sign-in and tool calls still need to be verified in this app. Availability depends on your plan and administrator settings; directory publication requires separate review.
Once you’re connected
Start a useful conversation.
Try a lookup using a synthetic demo account first, and check the result against FRM.
“Find a donor and show their giving history.”
“Summarize our fundraising results this calendar year.”
“Show my open fundraising tasks due this week.”
Always your relationships
You control the connection.
Access follows your FRM account permissions. Records retrieved by an assistant are shared with the AI platform you connect. Review proposed changes and disconnect any app in FRM settings.
FRM connection guide · Updated