@lanonasis/memory Sdk Standalone

onasis-team

Standalone Memory SDK - drop into any project for multi-agent orchestration with persistent memory

Add to Cursor Add to VS Code Run on PlugMCP

1{2  "mcpServers": {3    "lanonasis-memory-sdk-standalone": {4      "command": "npx",5      "args": [6        "-y",7        "@lanonasis/[email protected]"8      ]9    }10  }11}

.cursor/mcp.jsonMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y @lanonasis/[email protected]

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1claude mcp add lanonasis-memory-sdk-standalone -- npx -y @lanonasis/memory-sdk-standalone@1.1.1

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "lanonasis-memory-sdk-standalone": {4      "command": "npx",5      "args": [6        "-y",7        "@lanonasis/[email protected]"8      ]9    }10  }11}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 1.1.1
Last checked: 2026-10-28

Stars: —
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install @lanonasis/memory Sdk Standalone?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does @lanonasis/memory Sdk Standalone need an API key?

No required environment variable is listed on this record.

What transport does @lanonasis/memory Sdk Standalone use?

@lanonasis/memory Sdk Standalone runs locally over stdio.

When was @lanonasis/memory Sdk Standalone last checked?

Last checked 2026-10-28. Standalone Memory SDK - drop into any project for multi-agent orchestration with persistent memory

From the publisher

Documentation

Lan Onasis — Artifact Warehouse & SDK Distribution

Intended public repository. This repo contains published npm packages, SDK, CLI, and IDE extensions. The Express server (src/server.ts) is valid for standalone/self-hosted deployments only — production API traffic at api.lanonasis.com bypasses it entirely and routes directly to Supabase Edge Functions.

Published Artifacts

Package	Version	Description
`@lanonasis/cli`	3.9.x	CLI with MCP server + interactive commands
`@lanonasis/mcp-core`	1.0.0	Production MCP server (17+ tools)
`@lanonasis/memory-sdk`	1.0.0	Memory-as-a-Service TypeScript SDK
`@lanonasis/ai-sdk`	0.2.2	Drop-in AI SDK

Repository Structure

lanonasis-maas/
├── packages/               # Published npm packages
│   ├── memory-sdk/         # @lanonasis/memory-sdk
│   ├── claude-memory/      # Claude session memory enrichment
│   └── recall-forge/       # OpenClaw plugin
├── cli/                    # @lanonasis/cli command-line tool
├── IDE-EXTENSIONS/         # VS Code, Cursor, Windsurf extensions
├── src/                    # Express server — standalone path ONLY
└── docs/                   # Context documentation

Production API Path (what NOT to expect here)

Production intelligence API at api.lanonasis.com routes directly to Supabase Edge Functions in apps/onasis-core/supabase/functions/. The Express server in src/ is NOT in the production path for memory/intelligence routes.

For SDK/CLI calling production endpoints, use https://api.lanonasis.com — not the local Express server.

Development

Package manager: bun (not npm).

bun install              # Install dependencies
bun run build            # Build all packages
bun run dev              # Start Express server (standalone testing only)
bun test                 # Run tests

Express Server — Standalone Path Only

src/server.ts is a valid standalone Express server for:

Self-hosted/enterprise deployments
Local development without cloud dependencies
Testing SDK functionality against local endpoints

It is NOT the production API server. Production routes go directly to Supabase Edge Functions.

Authentication

Production (api.lanonasis.com): X-API-Key with lano_* prefix via Supabase EFs. Standalone (localhost:3000): JWT/Bearer token via Express auth middleware.

Database

Supabase (PostgreSQL + pgvector) — same project as the platform (mxtsdg*********.supabase.co). Connect via SUPABASE_URL env var.

Never run supabase db push against production. Use reviewed SQL or MCP tool.

Adding New Features

Feature	Location
New SDK methods	`packages/memory-sdk/src/`
New CLI commands	`cli/src/commands/`
New npm package	`packages/<name>/`
New backend logic	`apps/onasis-core/supabase/functions/` (EF) — NOT here

Status

Intended public repo — perform secrets audit before publishing
Package manager: bun
Express server: standalone/self-hosted only
Production API: Supabase EFs in onasis-core

@lanonasis/memory Sdk Standalone

onasis-team

Standalone Memory SDK - drop into any project for multi-agent orchestration with persistent memory

Autonomous Agents Knowledge Memory

Add to Cursor Add to VS Code Run on PlugMCP

GitHub npm Website

Add to Cursor Add to VS Code Run on PlugMCP

1{2  "mcpServers": {3    "lanonasis-memory-sdk-standalone": {4      "command": "npx",5      "args": [6        "-y",7        "@lanonasis/[email protected]"8      ]9    }10  }11}

.cursor/mcp.jsonMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y @lanonasis/[email protected]

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1claude mcp add lanonasis-memory-sdk-standalone -- npx -y @lanonasis/memory-sdk-standalone@1.1.1

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "lanonasis-memory-sdk-standalone": {4      "command": "npx",5      "args": [6        "-y",7        "@lanonasis/[email protected]"8      ]9    }10  }11}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 1.1.1
Last checked: 2026-10-28

Stars: —
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install @lanonasis/memory Sdk Standalone?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does @lanonasis/memory Sdk Standalone need an API key?

No required environment variable is listed on this record.

What transport does @lanonasis/memory Sdk Standalone use?

@lanonasis/memory Sdk Standalone runs locally over stdio.

When was @lanonasis/memory Sdk Standalone last checked?

Last checked 2026-10-28. Standalone Memory SDK - drop into any project for multi-agent orchestration with persistent memory

From the publisher

Documentation

Lan Onasis — Artifact Warehouse & SDK Distribution

Intended public repository. This repo contains published npm packages, SDK, CLI, and IDE extensions. The Express server (src/server.ts) is valid for standalone/self-hosted deployments only — production API traffic at api.lanonasis.com bypasses it entirely and routes directly to Supabase Edge Functions.

Published Artifacts

Package	Version	Description
`@lanonasis/cli`	3.9.x	CLI with MCP server + interactive commands
`@lanonasis/mcp-core`	1.0.0	Production MCP server (17+ tools)
`@lanonasis/memory-sdk`	1.0.0	Memory-as-a-Service TypeScript SDK
`@lanonasis/ai-sdk`	0.2.2	Drop-in AI SDK

Repository Structure

lanonasis-maas/
├── packages/               # Published npm packages
│   ├── memory-sdk/         # @lanonasis/memory-sdk
│   ├── claude-memory/      # Claude session memory enrichment
│   └── recall-forge/       # OpenClaw plugin
├── cli/                    # @lanonasis/cli command-line tool
├── IDE-EXTENSIONS/         # VS Code, Cursor, Windsurf extensions
├── src/                    # Express server — standalone path ONLY
└── docs/                   # Context documentation

Production API Path (what NOT to expect here)

For SDK/CLI calling production endpoints, use https://api.lanonasis.com — not the local Express server.

Development

Package manager: bun (not npm).

bun install              # Install dependencies
bun run build            # Build all packages
bun run dev              # Start Express server (standalone testing only)
bun test                 # Run tests

Express Server — Standalone Path Only

src/server.ts is a valid standalone Express server for:

Self-hosted/enterprise deployments
Local development without cloud dependencies
Testing SDK functionality against local endpoints

It is NOT the production API server. Production routes go directly to Supabase Edge Functions.

Authentication

Production (api.lanonasis.com): X-API-Key with lano_* prefix via Supabase EFs. Standalone (localhost:3000): JWT/Bearer token via Express auth middleware.

Database

Supabase (PostgreSQL + pgvector) — same project as the platform (mxtsdg*********.supabase.co). Connect via SUPABASE_URL env var.

Never run supabase db push against production. Use reviewed SQL or MCP tool.

Adding New Features

Feature	Location
New SDK methods	`packages/memory-sdk/src/`
New CLI commands	`cli/src/commands/`
New npm package	`packages/<name>/`
New backend logic	`apps/onasis-core/supabase/functions/` (EF) — NOT here

Status

Intended public repo — perform secrets audit before publishing
Package manager: bun
Express server: standalone/self-hosted only
Production API: Supabase EFs in onasis-core