Skip to main content

Connect Grok Build to Floxar

Grok Build, the command-line client, identifies itself with the identifier Floxar publishes for it, grok-build. There is no client secret. The connection is confirmed with Grok Build 1.0.44. Grok on grok.com is a separate client with a guide of its own: Connect Grok (grok.com).

Grok Build sends no scopes unless they are set. Without them, Floxar takes the request as asking for the three capability scopes, and the connection does not ask to stay connected, so the oauth_scopes line below is recommended.

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. Add the server to ~/.grok/config.toml (or .grok/config.toml in a project).

    [mcp_servers.acme-floxar]
    url = "https://mcp.floxar.com/a/<account_id>"
    oauth_client_id = "grok-build"
    oauth_scopes = ["floxar.read", "floxar.execute", "floxar.author", "offline_access"]

  2. Start Grok Build, run /mcps and press i to authenticate. Sign in to Floxar in the browser window, confirm the account and allow the connection.

What the sign-in looks like​

The consent page shows Grok Build under Floxar's label for it, with its vendor. Grok Build runs on your computer, so the connection returns to a local address, and the consent page says so.

Known limits​

  • Grok Build may share your grok.com connection. If the same account is also a connector on your grok.com account, Grok Build offers that connection under /mcps as well, and the two then share one connection: revoking it disconnects both.
  • Disconnecting on grok.com is local only, including for a connection Grok Build shares. The connection stays active in Floxar until you or an account admin end it there (see "Disconnecting and revoking" in Connecting an AI client).
  • After a revocation, Grok Build's log reports a failed handshake and a failed start. Authenticate again from /mcps.
  • Type the identifier exactly. An oauth_client_id other than grok-build is refused as an invalid client.

Last reviewed: 2026-09-30