Skip to content
lobu
API Blog

Connect from Grok

Give Grok web and Grok CLI the same source-linked company context, permissions, and governed actions used by your other agents.

Use mapped devices from Grok

Grok can request governed work that Lobu routes to an authorized device worker for local files, connector syncs, actions, or device Automations. Run lobu daemon on that machine once; a named context keeps one stable host identity, while supported Claude Code, Codex, and OpenCode sessions receive separate per-session identities for interactive delivery. See the device worker setup.

Lobu is open-source but we also have a managed cloud. If you'd like to try, sign in at app.lobu.ai, then point Grok at https://app.lobu.ai/mcp as the MCP endpoint. The same URL works for every workspace. Pick one below to scope it to that example.

Paste this into Grok and it will install Lobu for you.

Prompt for Grok
Connect this Grok session to Lobu, the shared company context layer for agents, over MCP: https://lobu.ai/mcp.

Onboard yourself:
- If you have a CLI: run `grok mcp add --transport http lobu https://lobu.ai/mcp`, then open the MCP menu and complete OAuth on first use.
- If you can't touch a terminal: ask the user to open grok.com/connectors, choose New Connector → Custom, add https://lobu.ai/mcp, and authenticate Lobu — then continue once connected.

Authenticate when prompted, then:
Read the Lobu skill at https://app.lobu.ai/api/skill/lobu, then run search_sdk for the smallest SDK surface you need. Do not dump the whole workspace.
Search existing memory before answering or saving a duplicate. Use search_memory/save_memory for durable context, query_sdk for reads, run_sdk for writes. Preview consequential writes first and keep every returned source URL, identifier, and approval status exact — never invent one, never fabricate a returned URL or identifier.

Connect Grok

  1. For Grok CLI, run grok mcp add --transport http lobu https://lobu.ai/mcp.
  2. Authenticate Lobu when Grok first calls an MCP tool.
  3. For Grok web, open grok.com/connectors and choose New Connector → Custom.
  4. Add https://lobu.ai/mcp, complete OAuth, and select the Lobu workspace.

Grok CLI and Grok web can use the same Lobu MCP endpoint. For a self-hosted Lobu instance, replace https://lobu.ai/mcp with your own publicly reachable endpoint.

Related Docs

Understand the MCP connectionSee how external agent clients reach Lobu tools and memory.Choose what to rememberSeparate session files from shared organizational state.Explore other surfacesUse the same agent in team chat, web, or a custom app.