Orchestrator

Multica

Multi-agent setup: connect the AI tool Multica launches, add its MCP config when needed, then give each Multica agent one Mem AI Identity.

Multica Guide Open Multica

Start with the official install path, then open the detailed guide when you need remote configuration, troubleshooting, or the manual fallback path.

Agent shortcut

Ask your agent to install it

Copy a one-line request. Your agent will open this guide, use the recommended path, and verify the setup.

How Multica Connects

Connect the AI tool Multica launches, then set one Mem AI Identity for the Multica agent.

If the agent runs Claude Code, save the Nowledge Mem MCP config in the Multica agent's MCP settings. Multica starts Claude Code as a child process, so Claude Code needs that MCP config passed through --mcp-config.

Command

NMEM_AGENT_ID=cindy

Sessions inside the launched AI tool can sync through that tool's Nowledge Mem connector. Multica's own workspace history needs a Multica export, API, or hook before Mem can import it directly.

Do not put broad secrets in agent custom env. NMEM_AGENT_ID is only an identity selector.

More Orchestrator Connectors

Slock

Multi-agent setup: connect the AI tool Slock launches, then give each Slock worker one Mem AI Identity.

By Nowledge Labs

Slock Guide Open Slock

Lody

Runtime launcher setup: connect the AI tool Lody launches, then add a Mem AI Identity only when an Agent Config represents a stable role.

By Nowledge Labs

Lody Guide Open Lody

Cumora

AI teammate setup: connect the AI tool Cumora launches, then give each teammate its own Mem AI Identity instruction.

By Nowledge Labs

Cumora Guide Open Cumora