What this is
Grok Bot is the cloud-hosted agent surface. It is different from Grok Build, the coding agent that can load a local plugin, and from consumer Grok on the web, which uses the Browser Extension. Grok documents plugins, skills, and hooks; a Bot or team may expose those capabilities through its Settings → Plugins surface.
Connect Mem
Grok Bot cannot reach a service running on your computer. Use Nowledge Cloud or an authenticated Access Anywhere endpoint that is publicly reachable over HTTPS.
You do not need Plus or Max to connect a Bot. Access Anywhere Quick link works without a subscription, Cloudflare account, or domain. Plus and Max include the stable managed Nowledge Link; a user-managed Cloudflare domain is another option for a stable address.
MCP is the reliable connection path. If the Bot or its team exposes the shared Nowledge Mem package, you may enable it there for the skills and lifecycle hooks that the host supports. The package does not bypass Grok's team policy or give Mem access to private Bot data.
- In Mem, open Settings → Access Mem Anywhere, or use your Nowledge Cloud connection.
- Copy the public MCP address and keep its key private.
- In Grok Bot, open Settings → Plugins and add a custom connector, then enter the MCP address and authentication requested by the connector flow.
- Ask the Bot to search your memories, then save one test decision to the intended Space.
Do not paste http://127.0.0.1:14242 or http://localhost:14242 into Grok Bot. Those addresses are for the local desktop app and local agents only.
What works
- MCP memory search, context retrieval, distillation, and scoped writes
- The same Cloud/App Space and identity rules used by other remote clients
- Explicit Bot role and identity configuration when several Bots share one account
What is not promised
The MCP connector does not automatically import every Grok Bot conversation.
We have not verified a Bot-specific transcript export or hook payload that a
Nowledge Mem connector can read for complete-thread capture, so there is no nmem t sync --from grok-bot command. Grok's general hook support does not, by
itself, establish access to the Bot's private transcript.
If you have a supported conversation export, use Import existing conversations. MCP tools search and update data already in Mem; they do not grant the server access to a Bot's private conversation files.
Identity and spaces
When a Bot represents a durable role, configure that role explicitly in Mem. Do not use the Bot's display name or source_app as an identity selector. The server remains authoritative for the Space and access scope.
Troubleshooting
- The connector cannot connect: confirm the MCP address is public HTTPS and not a loopback or private LAN address.
- Memory tools are missing: reload the Bot after changing its connector settings and confirm the connector is enabled in Grok Bot Settings → Plugins.
- The Bot searches the wrong Space: check the remote Mem connection and explicit Space/identity configuration; do not create a new Space just to make the connection pass.
