Grok Bot

Read https://mem.nowledge.co/SKILL.md and the Grok Bot guide at https://mem.nowledge.co/docs/integrations/grok-bot. Use the configured Nowledge Mem MCP connector to search my memories and save a scoped test decision. Do not use localhost. Do not claim automatic full-thread capture unless Grok Bot provides a documented export or hook.

What this is

Grok Bot is Grok's cloud-hosted agent. 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 Bot can use connectors and MCP servers from its cloud computer. Creating a custom MCP connector and enabling a plugin for a Bot are separate steps.

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.

The connection is two-way in a precise sense: Grok Bot can call Mem, while Mem cannot read Grok Bot's private conversation history. For a local desktop Mem, Access Anywhere is the bridge; for a hosted Mem, use the Cloud MCP address.

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. Create the custom connector at grok.com/connectors; do not try to create it inside the Bot's Plugins page. If the Bot or its team also exposes the shared Nowledge Mem package, you may enable that separately 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.

1. In Mem, open Settings → Access Mem Anywhere, or use your Nowledge Cloud connection.
2. Copy the public MCP address and keep its key private.
3. Open grok.com/connectors, choose New Connector → Custom, enter the MCP address, and complete OAuth. For a Business or Enterprise team, an admin may need to provision the connector and allow its server first.
4. In Grok Bot, open Settings → Plugins and enable the connector for the Bot. Enable the shared Nowledge Mem package separately only if it is available under your team's policy.
5. Ask the Bot to search your memories, then save one test decision to the intended Space.

Never 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 automatic

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: confirm the custom connector exists at grok.com/connectors, then reload the Bot and enable it under Settings → Plugins.
• A team member cannot connect: ask a team admin to check the shared MCP allowlist and member-managed-server policy.
• 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.

For the separate local coding-agent path, see Grok Build.