Locus product guide · Updated
How to add Locus to Grok, Grok Build, and Grok Bot
To add Locus to Grok, open grok.com Connectors, choose New Connector, then Custom, paste https://api.paywithlocus.com/api/credits/mcp, and approve Locus in your browser. Grok Build takes a plugin or a grok mcp add command. Grok Bot takes one chat message. All three connect to the same Locus Pro credit balance.
Setup, step by step
Step 1
Open Grok connectors
Sign in to grok.com and go to the Connectors page.
https://grok.com/connectors
Step 2
Create a custom connector
Choose New Connector, then Custom.
Step 3
Paste the Locus MCP server URL
Name it Locus and paste this URL. Leave any header or key fields empty. Grok finds the sign-in flow from the URL.
https://api.paywithlocus.com/api/credits/mcp
Step 4
Approve Locus in your browser
Grok opens Locus sign-in. The consent screen names the client as Grok. Sign in or create an account, pick the workspace whose credits Grok should use, and approve.
Step 5
Turn it on in a chat
In a new chat, open Attach, then Connectors, and select Locus. Then ask a free question to confirm the connection.
What's my Locus balance?
How do I add Locus to the Grok Build CLI?
Install the Locus plugin with one command, then sign in from the /mcps screen. The plugin adds the MCP connection and three skills: locus, locus-setup, and locus-workflows.
Command: grok plugin install locus-technologies/locus-pro-plugin --trust
Then open grok, type /mcps, pick locus, and press i. Approve Locus in your browser. Grok Build does not ask you to sign in on first use, so press i before you ask for a tool.
To add only the MCP server without the skills, run: grok mcp add --transport http locus-pro https://api.paywithlocus.com/api/credits/mcp
Then open grok, type /mcps, pick locus-pro, press i, and approve Locus. Use one of the two methods, not both. Two entries point at the same account.
How do I add Locus to Grok Bot?
Send Grok Bot one message and confirm. It adds the server for you.
Message: Add a custom MCP server called Locus at https://api.paywithlocus.com/api/credits/mcp
Choose Add it when Grok Bot asks, then approve Locus in your browser. This path was checked by the Locus team in Grok Bot. Grok Bot stores the server itself. It does not write it to a local settings file.
Which Grok setup should I use?
Use the surface where you already work with Grok. Each one keeps its own connection, so set up each surface you use.
| Surface | Method | What you get |
|---|---|---|
| grok.com | Custom connector with the MCP URL | Locus tools in chat, picked under Attach, then Connectors |
| Grok Build CLI | grok plugin install (easiest) or grok mcp add | Plugin: MCP plus three Locus skills. MCP add: tools only |
| Grok Bot | One chat message, then Add it | Locus tools inside Grok Bot |
How do I check that Grok can use Locus?
Ask "What's my Locus balance?". Grok calls the free balance tool and reads back your credits. In Grok Build with grok mcp add, the tool shows as locus-pro__get_balance.
If the balance reads 0 when you expect credits, you probably approved a different workspace at consent. Reconnect Locus and pick the funded workspace on the consent screen.
The balance check is free. Paid tool calls use credits at the price shown before the call. Your spending limits and tool permissions still apply.
Frequently asked questions
Do I need an xAI API key or a Locus API key?
No. Grok signs in to Locus with browser OAuth and stores the connection. You do not copy a key into Grok.
Why does Grok Build not ask me to sign in?
Grok Build waits for you to start sign-in. Type /mcps, pick the Locus server, and press i. The docs line that says Grok opens sign-in on first use is out of date.
Can I load fewer Locus tools into Grok?
Yes. Use https://api.paywithlocus.com/api/credits/mcp?surface=compact as the server URL. Compact mode loads short discovery and execution tools and can still reach the same catalog.
Can I use Locus with the xAI API instead of the Grok apps?
xAI documents remote MCP tools in its native SDK and its OpenAI-compatible Responses API. We have not tested Locus there. An API integration cannot finish a browser sign-in, so it needs a service credential from an enterprise workspace.
Implementation references
Use these first-party references for current request contracts and account requirements. Tool availability, prices, and negotiated terms can change.
Sources
Third-party details were checked on September 29, 2026. Vendors change pricing and features often, so confirm on their site before you decide.