Grok Setup

Grok reaches Nexus-Catalyst two ways. Use whichever matches where you work — they are not exclusive.

Surface	Method	Recall
grok.com	Custom connector (OAuth)	Model calls the tools
Grok CLI / Grok Build	Plugin — MCP rule plus a stop hook	Model calls recall; storage is automatic

---

Grok on the web

Prerequisites

Custom connectors sit on Grok’s paid tiers, and the MCP server must be reachable on the public internet. Ours is.

Setup

1. Go to grok.com/connectors
2. Choose New Connector, then Custom

3. URL: https://mcp.nexus-catalyst.com
4. Sign in with your Nexus-Catalyst account when prompted

Grok discovers the tools and they are available in your next chat.

Then add the Agent instruction set to your custom instructions, or Grok will not call recall unprompted.

---

Note

Menus move. If what you see does not match the steps above, Connectors is the authority — it is maintained by xAI and updates when their UI does.

Grok CLI and Grok Build

Both use the same CLI surface, so the same plugin covers them.

Install

npm install -g @nexus-catalyst/grok-plugin
export NC_PLUGIN_API_KEY="your-plugin-key"
nc-grok install
nc-grok status

Your Plugin API key comes from Account → API Keys. Put the export in your shell profile (~/.zshrc, ~/.bashrc) so it survives new sessions.

What it installs

• A rule telling the model to call recall_context at the start of a session
• A stop hook that stores the exchange when a session ends — this half is automatic

So recall depends on the model following the rule, while storage does not.

Commands

nc-grok install      # Add the NC rule and stop hook
nc-grok uninstall    # Remove them, leaving other config intact
nc-grok status       # Check installation state and API key

Note

If your Grok Build install uses a different binary, point it at the same ~/.grok (or project) config the plugin writes. The layout is documented in cli-hooks.

Troubleshooting

nc-grok status shows no API key

NC_PLUGIN_API_KEY is not set in the shell you are actually using. Check with echo $NC_PLUGIN_API_KEY.

Recall is inconsistent in the CLI

Expected to a degree — recall here is a rule, not a hook, so it depends on the model. Adding the full Agent instruction set makes it markedly more reliable.

---

Need help? Common Issues · support@nexus-catalyst.com