Quickstart

memnode now has two first-class paths: a hosted SaaS flow for shared tenants and a local MCP flow for users who want everything on their own machine. The product copy should reflect both.

Hosted path

Create an account and open the dashboard.
Provision a hosted tenant for your workspace.
Create a scoped API token with `memory.read` and `memory.write`.
Validate the token with `GET /api/v1/whoami`, then send `record` and `recall` traffic to the hosted API base.

curl -sS https://memnode.dev/api/v1/whoami \
  -H "Authorization: Bearer $MEMNODE_TOKEN"

Local MCP path

The local mode still matters. Run the Rust data plane yourself, point your MCP client at `memnode mcp`, and keep memory entirely on your own machine or repo path.

cargo run --bin memnode -- server --bind 127.0.0.1:8080
export MEMNODE_URL=http://127.0.0.1:8080
export MEMNODE_API_KEY=mn_live_...

Reference examples

Conversational assistant

Recall before reply, then record both sides of the turn so memory survives restarts.

examples/conversational_assistant

Coding assistant

Model projects and conventions as typed entities instead of loose text memories.

examples/coding-assistant

Research agent

Track whether a claim is observed, reported, inferred, or hypothesized, plus the source chain.

examples/research_agent

What makes Memnode different

Typed provenance instead of one undifferentiated memory bucket.
Hosted tenants and local MCP are both part of the product story.
Dashboard-issued tokens map cleanly onto `memory.read`, `memory.write`, and `memory.admin` scopes.
The hot path stays in the Rust data plane; Supabase remains the source of truth, not the read path.