Lobu

MCP文档知识

提供方 未标注

文档知识 stdio · 本地进程 未标注 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

面向ChatGPT、Claude、Codex及其他MCP客户端的共享公司上下文与受管工具。

一句话选型结论

按资料字段整理

Lobu 属于文档知识类 MCP 服务器,stdio · 本地进程,鉴权方式未标注,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类文档知识 传输方式stdio · 本地进程 鉴权未标注 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

文档知识
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

记忆

安装与配置

stdio · 本地进程 未标注
客户端在本机拉起子进程,数据不出本机
# Claude Code npx @lobu/cli@latest connect claude-code # Codex npx @lobu/cli@latest connect codex # OpenCode npx @lobu/cli@latest connect opencode

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
文档检索问答

在你的文档库里按问题找答案。

知识库读写

把新资料写进知识库,随用随取。

内容整理

把零散资料归纳成结构化笔记。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在文档知识场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Lobu当前 未标注 stdio · 本地进程 本地部署 有 未标注
dify 未标注 stdio · 本地进程 本地部署 有 2026-04-11
open-webui 未标注 stdio · 本地进程 本地部署 有 2026-04-11
JeecgBoot 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Cherry Studio 未标注 未标注 未标注 无 2026-05-17
mempalace 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

文档知识
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类文档知识本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

16.7 KB
来自项目仓库与上游目录的原文,未做删改

Lobu — Give every agent a live model of your world

Lobu is an open-source, event-sourced context layer for AI agents. Every tool call, data
change, device signal, API event, and conversation becomes an event, linked to the entities and
identities it belongs to — a person, a project, a customer, a home, a company. That gives agents
a live, queryable model of your world instead of a transcript they forget when the session ends.

ChatGPT, Claude, Codex, and your own agents read and write that same permission-aware history and
current context, whether you're wiring up your own accounts or an entire company's stack. When a
responsibility should outlive one chat, any agent can discover and hand it to a persistent Lobu
specialist over MCP.

Connect your tools once. Every agent resumes from the same live context.```text
WITHOUT LOBU WITH LOBU

Agent A -> Slack / GitHub / CRM Slack GitHub CRM DBs Devices
Agent B -> Slack / GitHub / CRM \ | | | /
Agent C -> Slack / GitHub / CRM +-----+-----+----+----+
|
Each agent re-fetches. v
Each session forgets. +-------------------+
| LOBU |
| events + entities |
| history + policy |
+---------+---------+
|
shared context
+-----------------+-----------------+
| | |
ChatGPT Claude / Codex Your agents


## See it in ChatGPT

The 86-second muted demo shows ChatGPT using Lobu over MCP to pull connected context and call
governed tools without leaving the conversation. The same shared context remains available to
Claude, Codex, and custom agents.

https://github.com/user-attachments/assets/26e6329a-1bc6-4480-8e57-e9388e38dde9

## Start with the agent you already use

Point any MCP client at Lobu. No Lobu agent runtime or `lobu.config.ts` is required.```bash
# Claude Code
npx @lobu/cli@latest connect claude-code

# Codex
npx @lobu/cli@latest connect codex

# OpenCode
npx @lobu/cli@latest connect opencode

Complete OAuth when prompted, connect the sources you want to share, and ask your agent to use
Lobu when it needs shared context.

The same MCP endpoint works with Claude Code, Codex, OpenCode, Antigravity, ChatGPT, Claude Desktop, Cursor, and custom MCP clients. Run lobu connect to detect a client, install the supported MCP and skill bundle, or get the exact native handoff when the host requires UI setup. Authentication happens in that agent on first use.

Setup guides: Claude · ChatGPT · Codex · Grok

Download Lobu: Mac app · Chrome extension

> Upgrading a Mac install made before the ai.lobu.mac app identity? Install the
> DMG by hand — the in-app updater does not carry an install across the bundle
> identifier change. It replaces /Applications/Lobu.app in place; also delete
> /Applications/Owletto.app if a pre-rename build is still there, since that one
> sits at its own path. From 20.0.1 your settings and the app's device identity
> carry across the rename, so device-pinned Automations keep running against the
> same worker. Login Items and privacy grants cannot come with them — macOS keys
> both to the bundle identifier — so the new app asks about Open at Login once and
> re-prompts for each permission on first use.

To test changes merged to main, run bunx @lobu/cli@canary --help. The
canary tag moves only when a maintainer runs Publish Packages from main
in GitHub Actions with channel canary; that run requires the commit's CI and
image checks and smokes the packed CLI before publishing. The published version
is then exercised across the Linux runtime matrix, so check the run's result before
depending on it. Use @latest for stable releases. Canary versions include the
full commit SHA so you can pin a preview when reproducing a bug. Package managers
can cache the moving tag: copy the exact version from the successful workflow run,
use it in place of canary, and confirm the installed version with lobu --version.

Recall what the company knows

Ask from Claude Code, Codex, or ChatGPT:

> What did we decide about enterprise onboarding, and what changed since the last release?

Lobu searches shared, durable organizational memory under the caller's permissions, regardless of which agent asks. The answer can combine connected discussions, project activity, customer records, saved decisions, and typed company entities without rebuilding that context from scratch in every chat.

Hand work to a persistent Lobu specialist

Ask your primary agent:

> Ask our customer-researcher specialist to review the latest feedback and propose the next three interviews.

The agent discovers the specialists available to you, selects the right one, delegates the task, and brings the result back. The specialist has its own identity, instructions, tools, durable conversations, and access policy.

To the user this stays one conversation in their primary agent. The specialist itself persists: it remains available to other authorized people and agents instead of disappearing with the current chat.

Why Lobu

Instead of every agent rebuilding the same state through per-session tool calls, Lobu runs a shared data layer:

  • Connect once. Polls, webhooks, APIs, and agent-written connectors feed one append-only event log.
  • Know once. Events can be indexed as searchable knowledge and linked to typed entities such as companies, projects, incidents, and customers.
  • Use from any agent. Authorized MCP clients read and contribute to the same organizational state according to their grants.
  • Delegate when useful. Persistent Lobu specialists can own a role, conversation history, tools, and recurring responsibilities.
  • Keep control. Identity, source permissions, approvals, credential brokering, provenance, and audit stay server-side.```mermaid
    flowchart TD
    Sources["Connectors / webhooks / devices / APIs"] --> Log[("append-only log")]
    Log -->|"resolve identities<br/>attach provenance"| Graph["context graph<br/>entities + links<br/>current + history"]
    Graph -->|"query"| Agents["agents + specialists"]
    Graph -->|"watch / subscribe"| Agents
    Agents -->|"sandbox + scoped tools / MCP<br/>policy + approvals"| Actions["actions on systems"]
    Actions -->|"action events"| Log

**MCP is for doing. Lobu&#x27;s event graph is for knowing.**

## One context layer, personal or company

The primitives don&#x27;t change between a single person&#x27;s accounts and an entire company&#x27;s stack —
only what&#x27;s connected does. Identities, entities, events, history, and policy work the same way
at either scope.```text
PERSONAL                               COMPANY

WhatsApp  Gmail  Calendar  Mac        Slack  GitHub  CRM  DB
    \       |       |      /              \      |     |   /
     +------+-------+-----+                +------+-----+---+
                    \                      /
                     +------- LOBU -------+
                     | identities         |
                     | entities + events  |
                     | history + policy   |
                     +---------+----------+
                               |
                      shared agent context
                  +------------+------------+
                  |                         |
       &quot;When is Alice home?&quot;      &quot;Why is Acme at risk?&quot;

Three ways to use Lobu

1. Add shared context to existing agents

Agents can search and save memory, query structured entities, inspect connected sources, and delegate to Lobu specialists without moving to a new chat interface or adopting Lobu's runtime.

Docs: Memory · Claude · ChatGPT · Codex

2. Run persistent Lobu specialists

Create a specialist for a durable responsibility: customer research, support triage, release coordination, incident follow-up, or an internal domain. People can talk to it from the Lobu web app or Slack, while other agents can call the same specialist over MCP.

Scaffold and run one locally:```bash
npx @lobu/cli@latest init my-specialist
cd my-specialist
npx @lobu/cli@latest run
npx @lobu/cli@latest chat -c local "hello"


`lobu run` starts the local stack with an embedded Postgres database by default and opens the web UI on `:8787`. It applies the project&#x27;s `lobu.config.ts` automatically only in embedded mode. To use external Postgres, set `DATABASE_URL`, ensure pgvector is available, then authenticate and apply the project to that runtime separately.

The current canary CLI downloads the required runtime components on first use and caches them for later runs. `--help`, `--version`, and commands that only connect to a remote runtime do not install the local stack. Docker images include their runtime dependencies at build time and start directly; local embedding model weights can still download on first use. See Docker deployment for the separate database and service configuration.

`lobu init`, including `init -y`, generates `ENCRYPTION_KEY` in the project&#x27;s `.env`. A manual setup must supply this key before starting: generate a 32-byte base64 value with `openssl rand -base64 32`. Keep the same key with the persistent database; replacing it makes previously encrypted secrets unreadable.

Docs: Getting started · Agent workspace · Skills · Slack

### 3. Build with the CLI and TypeScript SDK

The same governed data and operations are available without an agent:```bash
npx @lobu/cli@latest memory run                     # list the memory tools
npx @lobu/cli@latest memory run search_memory &#x27;{&quot;query&quot;:&quot;onboarding&quot;}&#x27;
npx @lobu/cli@latest call run_sdk --arg title=&#x27;List recent entities&#x27; \
  --arg script=&#x27;export default async (_ctx, client) =&gt; client.entities.list({ limit: 5 })&#x27;

Or from Node and TypeScript:```ts
import { client, searchMemory } from "@lobu/client";

client.setConfig({
baseUrl: "https://lobu.ai",
headers: { Authorization: Bearer ${process.env.LOBU_TOKEN} },
});

const hits = await searchMemory({
path: { orgSlug: "my-org" },
body: { query: "onboarding" },
});


Mint a token with `lobu token create`. The MCP tools and typed SDK operations share the server-side tool registry and access rules; `lobu memory run` dispatches through the MCP endpoint, and `lobu call` through the REST tool route by default (MCP when `LOBU_API_TOKEN` and `LOBU_MEMORY_URL` are set). `lobu call run_sdk`, `query_sdk`, and `query_sql` require a `title` arg, which names the call in the activity feed.

## Core concepts

### Shared context

Connectors collect activity on a schedule or through webhooks. Discussions, project changes, customer records, API events, and saved agent knowledge land in the same append-only history.

Typed entities connect that history to the things you care about: `Company`, `Project`, `Customer`, `Incident`, or schemas you define. Corrections supersede old facts rather than erasing their provenance.

Connectors are extensible. You can build them in TypeScript, and coding agents can use Lobu&#x27;s connector contract and validation flow to create integrations for sources Lobu does not ship with.

Docs: Memory · Connectors · API

### Persistent specialists

A Lobu specialist has a stable role, instructions, memory, tools, and conversation history. It can be reached from web chat or Slack and called by external agents through `client.conversations.send`.

Specialists use role files for identity and instructions: `IDENTITY.md`, `SOUL.md`, and `USER.md`. Guardrails can inspect input, output, and tool calls. Connector actions follow organization Auto, Ask, or Block rules in Settings → Policies; guardrails still apply under Auto, and action results return to the shared event log.

External agents do not ask users to write delegation code. They pass scripts like these to Lobu&#x27;s `query_sdk` and `run_sdk` MCP tools:

Scripts must default-export an async function. Lobu passes the execution context as the first argument and the ClientSDK as the second; keep `await` and `return` inside that function. A bare top-level `await` or `return` fails compilation. The same function format works with `lobu call run_sdk --arg title=&#x27;…&#x27; --arg script=&#x27;…&#x27;`.```ts
// Discover specialists through query_sdk.
export default async (_ctx, client) =&gt; {
  const { agents } = await client.agents.list();
  return agents;
};
``````ts
// Delegate through run_sdk and wait for the specialist&#x27;s reply.
export default async (_ctx, client) =&gt; {
  return client.conversations.send({
    agent_id: &quot;customer-researcher&quot;,
    thread: &quot;enterprise-onboarding&quot;,
    text: &quot;Review the latest customer feedback and propose the next three interviews.&quot;,
  });
};

Docs: Agent workspace · Guardrails · Security

Automations

Automations are versioned background responsibilities activated manually, on a schedule, by a connector event, or by another Automation's durable output. They read governed sources, persist structured results, and can notify Slack, open a ticket, or start agent work while nobody is in chat.

Collection and activation stay independent: connect a source once, keep its durable history useful to every authorized agent, then choose whether a responsibility should run on a schedule or immediately when a matching event arrives. Polling connectors, authenticated webhooks, and Automation outputs use their appropriate ingestion paths but converge on the same durable Automation run lifecycle. Initial syncs establish a baseline without flooding subscribers; repeated deliveries are deduplicated.

See the activation and chaining model.

Optional execution

Shared context and delegation over MCP do not require Lobu to execute code for the calling agent. When a Lobu specialist needs a shell, the built-in runtime provides lightweight just-bash execution. Remote sandbox providers such as Vercel Sandbox can be connected for workloads that need stronger isolation or more compute.

Which sandbox runs the code is a deployment choice. Lobu provides the shared context, permissions, and governance around it.

Channels

Lobu specialists can serve Slack, Telegram, WhatsApp, Discord, Teams, Google Chat, the web app, and a REST API. Channel conversations remain separate while reading the same authorized organizational context.

Setup: Slack · Telegram · Discord · WhatsApp · Teams · Google Chat

How Lobu differs

  • Agent frameworks help developers implement an agent loop. Lobu gives agents and people a shared organizational state and a place to keep persistent specialists.
  • Direct MCP integrations expose tools from one provider. Lobu continuously builds durable, cross-source context that every authorized agent can reuse.
  • Agent runtimes host a particular agent. Lobu lets people keep using Claude Code, Codex, ChatGPT, or their own runtime and add Lobu only where shared context or delegation is useful.
  • Workflow engines encode a graph of predetermined steps. Lobu Automations handle durable triggers and background responsibilities, while agents decide how to complete open-ended work.

Agent configuration

Runtime configuration is managed through the web app or the same org-scoped REST API used by the CLI. Local lobu.config.ts projects support validation and repeatable apply workflows.bash npx @lobu/cli@latest login npx @lobu/cli@latest org set my-org npx @lobu/cli@latest agent list

Docs: CLI reference · lobu apply

Deployment

Use the embedded runtime locally or self-host Lobu with external Postgres. Production guides: Docker · Cloud · Kubernetes

Security and privacy

Permissions and audit stay on Lobu's gateway. Lobu MCP servers and the credential-brokering layer handle provider and connector credentials, OAuth and token refresh, and third-party API proxying. Workers receive scoped placeholders or short-lived provider-derived access, never OAuth tokens or durable stored credentials. Connector actions follow organization approval policies, and connected data remains organization-scoped.

The built-in just-bash and embedded execution modes are policy and convenience boundaries, not VMs for hostile code. Use a remote sandbox provider when the workload needs a stronger isolation boundary.

Docs: Security · Secret proxy · Guardrails · Threat model

Design partners

We are working with technical teams that already use Claude Code, Codex, ChatGPT, or custom agents and want those agents to share company context or delegate to persistent specialists.

The best starting point is one team, one or two connected sources, and one repeated responsibility. Talk to the founder or reach out on X/Twitter.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Lobu 怎么安装?

在客户端按下面的安装命令接入:# Claude Code npx @lobu/cli@latest connect claude-code # Codex npx @lobu/cli@latest connect codex # OpenCode npx @lobu/cli@latest connect opencode。装完在客户端配置里引用同一个包或端点。

Lobu 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Lobu 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Lobu 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

Lobu 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Windsurf、Gemini CLI;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Lobu 能提供哪些能力?

资料显示能力标签包括 记忆。具体工具清单以官方文档为准。

Lobu 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

Lobu 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。