Control Cursor and Claude compat scanners in Grok Build

Grok Build can scan Cursor and Claude harness directories for skills, rules, agents, MCP configs, and hooks. Each scanner defaults on. Official switches: Settings reference.

What gets scanned

Family	Env master switches (default on)
Cursor	GROK_CURSOR_SKILLS_ENABLED, GROK_CURSOR_RULES_ENABLED, GROK_CURSOR_AGENTS_ENABLED, GROK_CURSOR_MCPS_ENABLED, GROK_CURSOR_HOOKS_ENABLED
Claude	GROK_CLAUDE_SKILLS_ENABLED, GROK_CLAUDE_RULES_ENABLED, GROK_CLAUDE_AGENTS_ENABLED, GROK_CLAUDE_MCPS_ENABLED, GROK_CLAUDE_HOOKS_ENABLED

TOML mirrors under [compat.cursor] / [compat.claude] with keys skills, rules, agents, mcps, hooks (true / false, default true).

Keep a Grok-only load

Disable the scanners you do not want for a clean discovery dump. Example — turn Cursor MCP and Claude hooks off for one process:

export GROK_CURSOR_MCPS_ENABLED=0
export GROK_CLAUDE_HOOKS_ENABLED=0
grok inspect

Or pin in user config:

[compat.cursor]
mcps = false

[compat.claude]
hooks = false

Re-enable by setting 1 / true or unsetting the env override.

Verify

grok inspect
grok inspect --json

Confirm which rules, skills, plugins, hooks, and MCP servers loaded and from which path — Inspect what Grok Build loads. Native Grok paths (.grok/, AGENTS.md, marketplace plugins) still load when vendor scanners are off.

Pitfalls

• Compat scanners are additive discovery. Turning them off does not remove Grok-native .grok/agents/, skills, or MCP entries.
• Project .grok/config.toml is limited to MCP, plugins, and permission rules — put [compat.*] in user ~/.grok/config.toml.
• Duplicate MCP names: a project server with the same name as a user server replaces the user one entirely.