Skip to main content
Add Darwin as a remote HTTP MCP server. Grok Build handles the OAuth browser flow and makes Darwin’s tools available alongside its built-in coding tools.

First request

Once Darwin’s tools appear in the agent, paste this request:
Use xagent’s MCP server guide for current client behavior and configuration scopes.

Verify the connection

Open /mcps in the Grok Build TUI if you need to authenticate, refresh the tool list, or disable the server. A successful connection exposes Darwin’s current tools under the darwin namespace; compare them with the MCP reference if verification fails.
Direct MCP installation works now. Darwin’s public Grok Build plugin is awaiting xAI marketplace review in plugin-marketplace PR #913.

Choose the right scope

Keep OAuth credentials in Grok Build’s credential store. Never commit tokens, authorization headers, or Darwin API keys to .grok/config.toml.

Preserve Darwin’s authority boundary

Repository access and Grok Build permissions do not grant Darwin approval authority. Use Search to compare capabilities, preserve the exact selected IDs, and let Darwin’s typed thread requests, revisions, and operation states determine what can happen next.
A model-authored message is not an approval, payment, authentication result, or completed operation. Read the current thread events and operation states before every consequential next step.
View the installable plugin source or xagent’s marketplace contribution rules.
Last modified on October 4, 2026