Work with Grok

Status: Available

Use the Grok CLI with the same Crux MCP endpoint as Cursor and Claude Code.

Setup

1. Open Settings → External sources → AI assistants → Grok (or Settings → Setup MCP → Grok).
2. Copy the one-command install and run it in your terminal: grok mcp add --transport http crux https://www.crux-hq.com/mcp
3. Sign in when prompted (OAuth), then capture research, ask about the experience, or plan work by project name.

You can also paste the config.toml block into ~/.grok/config.toml. Grok also loads compatible configs from ~/.cursor/mcp.json if you already installed Crux for Cursor.

What Grok can do

Grok gets the full Crux tool set, so it both reads and writes your projects:

• Read — list projects, read the research and experience graphs, ask why an entity exists (ask_why), and read the current plan (list_plan).
• Write — capture research from the conversation (capture_research), create experience entities, register code references, and schedule activities and to-dos (upsert_activity, create_todo).

Writing requires the connection's Write permission, which is on by default. See the full read and write tool list.

Plan from the conversation

Ask Grok to plan or sequence work and it reads what is already scheduled, proposes activities, dates, owners, and the to-dos under each, and writes them once you agree. They appear immediately on the Crux Plan calendar and timeline.

How it fits

Crux keeps Research (evidence) and Experience (pages, features, content) linked. Grok plugs into that loop — it does not replace the tool you already use for day-to-day work in that product.

Notes

Write scope is on by default for new grants so agents can save research, schedule work, and register code tags. Manage grants under Settings → Integrations.

Next

• MCP, overlay, and the browser extension
• Plan: calendar & timeline
• Work with Cursor