Hosted MCP
Every store is a remote MCP server — connect an agent with one command.
Every managed store is also a remote MCP server. An agent connects with one command — no application code:
claude mcp add --transport http orecloud \
"https://<host>/mcp/<org>/<environment>/<store>" \
--header "Authorization: Bearer <key>"orecloud mcp install prints ready-to-paste configs for Claude Code,
Cursor, and VS Code; the console's Connect panel shows them prefilled.
Scopes decide the toolset
The key's scopes decide which tools the agent sees:
| Key scope | Tools |
|---|---|
read:search | lodedb_search, lodedb_stats |
+ read:text (on an expose-text store) | + lodedb_get, inline text in search hits |
+ write (on a cloud-writer store) | + lodedb_add, lodedb_remove |
With a write-scoped key, an agent can bootstrap and maintain its own memory
through MCP alone. Append ?read_only=true to the endpoint URL to force a
read-only toolset regardless of the key.
Same tools locally
Tool names and schemas are contract-tested equal to the local lodedb mcp
stdio server, so an agent moving between a local LodeDB directory and its
hosted copy sees the same tools.