Cradle × Nowledge Mem

Cradle includes @cradleapp/nowledge-mem as a first-party integration plugin. It keeps memories, threads, Spaces, graph data, and credentials in Mem while giving Cradle agents a guided path to use them.

Before You Start

• Nowledge Mem is running locally, or you have a reachable remote Mem server
• Cradle is installed
• You can open Cradle's Plugin Marketplace and plugin settings

For a local setup, confirm Mem first:

nmem status

Enable The Plugin

1. Open Cradle's Plugin Marketplace.
2. Find Nowledge Mem under integration plugins.
3. Enable the bundled plugin.
4. Open Nowledge Mem Settings from Cradle's sidebar.
5. Keep the default local endpoint, or enter the endpoint for your Mem server.

The plugin defaults to:

http://127.0.0.1:14242

Configuration

The settings panel owns non-secret configuration:

For environment-based or remote setup, Cradle also supports:

NMEM_API_URL=http://127.0.0.1:14242
NMEM_MCP_URL=http://127.0.0.1:14242/mcp
NMEM_API_KEY=your-key

Cradle does not write NMEM_API_KEY into plugin storage and does not return it from public config routes. The settings panel only reports whether a key is present.

Verify

Open the plugin status view, then ask a Cradle agent:

Use the Nowledge Mem integration to read my Working Memory and summarize the current focus.

A healthy setup can reach Mem and return Working Memory or Context Bundle content. If mcpUrl is configured, Cradle also registers the nowledge-mem streamable HTTP MCP server for runtimes that can use it.

What Works Today

• Read Working Memory
• Fetch Context Bundle with source_app=cradle
• Search and explicitly create durable memories
• Search, read, create, and append saved threads
• Register Mem MCP when configured
• Load Cradle's bundled nowledge-mem skill

What Is Not Automatic Yet

Cradle's current plugin is guided and route-driven. It does not yet provide:

• automatic pre-turn recall
• automatic session capture
• pre-compaction capture
• provider-neutral tool exposure in every Cradle runtime

These require Cradle plugin lifecycle support. Installing an additional Mem hook or community package would not create those host events and could duplicate ownership, so keep one bundled plugin as the integration boundary.

Troubleshooting

Cradle cannot reach Mem

Run nmem status on the same machine, then check apiUrl. For remote Mem, confirm that the endpoint is reachable from Cradle and that NMEM_API_KEY is available to the Cradle process.

The agent can use plugin routes but not MCP tools

Set mcpUrl to the Mem MCP endpoint and reload the plugin. The default local value is http://127.0.0.1:14242/mcp.

A Cradle conversation did not appear in Threads

That is expected unless the agent explicitly created or appended the thread. Automatic transcript capture is not part of Cradle's current plugin lifecycle.

Related

• Connectors overview
• Threads
• Cradle's official plugin guide