memos-cloud-server
MemOS Cloud Server Skill
This skill allows the Agent to interact with MemOS Cloud APIs for memory search, addition, deletion, knowledge base management, and feedback.
⚠️ Setup & Safety Rules (MUST READ)
Before executing any API operations, ensure these environment variables are configured. Each variable has an ownership layer — who is responsible for setting it — which determines whether it should ever be overridden at call time.
| Variable | Required | Ownership layer | Per-call override? | Notes |
|---|---|---|---|---|
MEMOS_API_KEY |
Yes | User / deployment secret | No | Auth token. Never expose to the LLM. |
MEMOS_USER_ID |
Yes | User / host platform | No | Must be deterministic (hashed email, employee ID). Do NOT use random or per-session IDs. |
MEMOS_CLOUD_URL |
No | Deployment | No | API base URL. Default: https://memos.memtensor.cn/api/openmem/v1. |
MEMOS_AGENT_ID |
No | Host platform (per-process injection) | Yes — via --agent-id on add_message / add_feedback |
Isolates memories per agent. A single global env var only supports one agent per machine; for multi-agent on one device, either let the host platform inject this per-process or pass --agent-id per call. |
MEMOS_APP_ID |
No | Host platform | Yes — via --app-id on add_message / add_feedback |
Isolates memories per application. Same multi-tenant caveat as MEMOS_AGENT_ID. |
MEMOS_ALLOW_PUBLIC |
No | Admin / security policy | No | true/false, default false. Security boundary — never let the LLM toggle this per call. |
MEMOS_ASYNC_MODE |
No | Deployment | No | true/false, default true. Whether add_message returns before processing completes. |
Multi-agent isolation pattern: Prefer per-process env injection by the host platform (each agent gets its own process tree with a distinct MEMOS_AGENT_ID). When the platform cannot inject env vars, fall back to passing --agent-id / --app-id on each call — the CLI flag takes precedence over the env var. These values must come from the orchestrator/platform; the LLM must not invent them.