Operator Guide
Running the stack: starting it, its ports and keys, connecting clients, the console, health and logs.
Quickstart
Before you start
Sizing
The base: the stack itself
The Console
What it is
Claude Integration
What the engine expects
Agent Skills
What the skills are
ChatGPT and OpenAI Integration
The endpoint, client key and agent profile are as in Claude integration.
OpenClaw Integration
The endpoint, client key and agent profile are as in Claude integration.
Other MCP Clients
1. Endpoint. http8765/mcp over streamable HTTP, or /mcp/sse for a client that speaks only the older SSE transport. A client that calls from a vendor's cloud needs the stack published over HTTPS.
Authentication with eMemory SaaS
How it works
Authentication with Your Own Identity Provider
This page describes what the engine's code does. It has been run only against eMemory SaaS's own identity provider.
Connecting Clients and Operating the Stack
Start the stack
Single Stack
The deployment option: a single stack on one machine. Start it with the quickstart.
Offline Stack
The deployment option: a single stack on one machine, with no internet needed.
Stacks in a Mesh
The deployment option distributed mesh architecture.
Local Stacks Peered with eMemory SaaS
The deployment option peering.
Multi-Site Mesh
The deployment option stacks in a mesh.