Last checked 2026-09-26
Add the server
Grok Build adds a remote MCP server with grok mcp add. Run this in your terminal:
grok mcp add --transport http compliance https://demo.mvdm.io/compliance/mcp
This adds the server for you in every project, in ~/.grok/config.toml. To share the server with your team through your repository, add --scope project after add. Grok Build then writes it to .grok/config.toml in the current folder.
Run grok mcp list to check the server. If something is wrong, grok mcp doctor compliance checks the settings and the connection.
Sign in
Grok Build's docs say that a server that needs OAuth starts a browser sign-in on first use. So this guide leads with the browser sign-in:
- Start Grok Build. The first time it uses the Compliance server, your browser opens Auth, the mvdm.io sign-in service. To sign in straight away, open
/mcps, pick the Compliance server, and pressi. - Sign in, if you are not signed in already.
- Auth shows a consent page. It names the Agent and warns that the Agent gets all your power, in every Account you belong to, billing and the License included. It asks which Account the Agent starts in.
- Press Allow, then go back to Grok Build and ask it something about your Compliance work.
Grok Build stores the sign-in in ~/.grok/mcp_credentials.json.
You can see and end every connection on API & Agent Access. An ended connection fails on its next call.
A Personal token instead
A Personal token works in Grok Build. Use one when a browser sign-in is not possible:
- Open API & Agent Access and create a Personal token. Choose its name, the Account it starts in, and when it expires.
- Copy the token. It is shown only once.
- Put the token in an environment variable, such as
COMPLIANCE_TOKEN, in your shell profile. - Tell Grok Build to send it as the
Authorization: Bearerheader. Add this to~/.grok/config.toml:
[mcp_servers.compliance] url = "https://demo.mvdm.io/compliance/mcp" bearer_token_env_var = "COMPLIANCE_TOKEN"
Grok Build reads the token from your environment, so the token stays out of the file.
A Personal token acts as you, like a browser sign-in does. Keep it secret, and end it on API & Agent Access when you no longer need it.
Notes for Grok Build
- Grok Build looks up MCP tools when it needs them, so a large set of tools costs little until it uses them.
- Grok Build also reads MCP servers from Claude Code's and Cursor's settings files. If you added Compliance there already, run
grok inspectfirst. It shows every server Grok Build loaded and where from. If Compliance is in that list, you need no new entry. - To stop using Compliance for a while, open
/mcpsand turn the server off with Space.
What to expect
- Browser handoff. Some acts need you in the browser, such as anything that costs money or accepting the Legal terms. Your Agent then shows you a link. Open it, check what is filled in, and confirm. If you do not open the link, nothing happens.
- Upload link. A tool call cannot carry a file, so your Agent asks Compliance for an Upload link, a one-time address for one file. The Agent sends the file there itself, often with
curl, or it shows you the link so that you can pick the file in your browser. The link expires after a few minutes. - One Account at a time. Your Agent starts in the Account you chose on the consent page, or the one you chose for your Personal token. Every answer says which Account it acted in. Ask your Agent to switch, and it moves to another Account you belong to.
- Rate limit. Each User has a limit on calls per minute, shared by all of your Agents and scripts. Over the limit, a call fails and says how many seconds to wait.
Another way in
Compliance also has a command-line tool, the Compliance CLI. Grok Build can run it as a shell command. See the CLI guide.