Skip to content
API Blog

MCP Reference

Agents use these tools to read and write the same permission-aware workspace. Setup: ChatGPT, Claude, OpenClaw.

  • Lobu Cloud: https://lobu.ai/mcp. Pin a workspace with https://lobu.ai/mcp/{org}, for example https://lobu.ai/mcp/acme.
  • Self-hosted: https://<your-host>/mcp and https://<your-host>/mcp/{org}. A local server is http://localhost:8787/mcp. Do not point a self-hosted workspace at https://lobu.ai/mcp.

Auth reuses the shared session; lobu memory run <tool> '{...}' invokes the same tools from the CLI.

These ship on MCP tools/list and are what an agent discovers automatically.

ToolPurposeKind
search_memorySemantic search of saved workspace memory: entities, facts, decisions, preferences, observations, notes. “What do we know?“read
save_memoryAppend facts/preferences/decisions/observations to memory. Pass supersedes_event_id to replace a fact; entity_ids to attach to entities.write
search_sdkDiscover ClientSDK methods and runtime helpers by name/namespace. Returns signatures + access requirements; mode="read" filters to read-only.read
query_sdkRead data through typed SDK methods (entities, relationships, feeds, operations, metrics). Scripts are TS; await ctx.sleep(ms) for polling.read
query_sqlPaginated, sortable, member-safe read-only SQL. Tables auto-scope to the bound org; virtual feeds are live-only.read
run_sdkAny mutating workspace action (CRUD entities, connections, Automations, feeds, operations, templates). dry_run:true previews without executing.write

Power rule: discover with search_sdk → read with query_sdk/query_sql/search_memory → write with run_sdk/save_memory.

query_sdk and run_sdk run in an isolated V8 isolate. Caps: 1 MB of output, 200 SDK calls, 180 seconds, and 30 seconds per ctx.sleep(). run_sdk with dry_run:true previews writes and does not dispatch them. Reactions use the same runner. See Author a connector.

Keep calls short. Never invent a returned URL or identifier. Search before saving a duplicate. Writes follow the caller’s org role and mcp:read / mcp:write scope.

First-party / admin tools (manage_agents, manage_connections, manage_feeds, manage_operations, manage_automations, query_metric, list_metrics, list_organizations, and friends) are NOT advertised on MCP tools/list. Agents and controllers reach the same surface through query_sdk/run_sdk ClientSDK namespaces, and admin UI / REST consumers dispatch them at POST /api/:org/:toolName (see REST API).

Last updated: