Skip to content
lobu
API Blog

Connect from Claude Code

Let Claude Code retrieve the team’s decisions and exact source evidence before it changes a repository, then save the verified result for the next agent.

Use mapped devices from Claude Code

Claude Code 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 Claude Code 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 Claude Code and it will install Lobu for you.

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

Onboard yourself:
- If you have a CLI: run `claude mcp add --transport http lobu https://lobu.ai/mcp`, then open `/mcp` and complete OAuth.
- If you can't touch a terminal: ask the user to run that Claude Code command, open `/mcp`, authenticate Lobu, and restart the session — 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 Claude Code

  1. Run claude mcp add --transport http lobu https://lobu.ai/mcp.
  2. Open /mcp in Claude Code and authenticate Lobu in the browser.
  3. Restart the Claude Code session if the newly connected tools are not listed.
  4. Ask Claude Code to search Lobu memory before it edits the repository.

The HTTP transport supports Lobu’s OAuth flow. For a self-hosted Lobu instance, replace https://lobu.ai/mcp with your own publicly reachable MCP 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.