Skip to main content

Connect Grok (grok.com) to Floxar

You add Floxar to Grok on grok.com as a custom connector. Grok identifies itself with its own Client ID Metadata Document, so it needs no client ID or secret from you. Reading and running trails through Grok are confirmed. Grok Build, the command-line client, is a separate client with a guide of its own: Connect Grok Build.

On Grok Business and Enterprise, a team admin provisions the connector in the cloud console first.

Before you start, make sure MCP is on for your account and have your account URL ready. Connecting an AI client explains both, and what the sign-in and consent page show.

Add Floxar​

  1. Open grok.com/connectors, select New Connector, then choose Custom.
  2. Enter your account URL as the MCP server URL.
  3. Sign in to Floxar in the window grok.com opens, confirm the account and allow the connection.

The MCP server URL is your account URL:

https://mcp.floxar.com/a/<account_id>

What the sign-in looks like​

The consent page shows Grok under Floxar's label for it. Grok asks for the three capabilities and to stay connected; the consent page lists what the account allows of that.

Known limits​

  • A revoked connection asks you to authenticate. After an account admin revokes the connection, Grok reports "Auth required". Use Re-Auth on the connector's page to connect again.
  • Disconnecting on grok.com is local only. The connection stays active in Floxar until you or an account admin end it there (see "Disconnecting and revoking" in Connecting an AI client).
  • Grok Build may share this connection. Once the account is a grok.com connector, Grok Build can use the same connection, and revoking it disconnects both.

Last reviewed: 2026-09-30