marm-init

Configure persistent shared memory for MCP clients across multiple agents.

329|62|Updated Jun 10, 2025
One-click install
npx skills add https://github.com/Lyellr88/MARM-Systems --skill marm-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: marm-init
Source: https://github.com/Lyellr88/MARM-Systems/tree/main/skills/marm-init
Command: npx skills add https://github.com/Lyellr88/MARM-Systems --skill marm-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of setting up MARM, a persistent local-first memory layer for MCP clients, so agents can share context, retain project decisions, and avoid repeated setup work.

Core Features & Use Cases

  • Guided installation: Helps choose and verify the MARM runtime, whether using Docker or local Python.
  • Transport and client setup: Configures HTTP or STDIO connections and writes the right MCP connection details for supported agents.
  • Multi-agent memory sharing: Links MARM across tools like Claude, Codex, Gemini, Qwen, Cursor, and VS Code so they can read and write the same memory pool.
  • Dashboard access: Starts or exposes the web dashboard for browsing memories, sessions, and logs.
  • Use case: Use this Skill when you want an assistant to walk you through a full MARM installation and leave your agent connected to persistent shared memory.

Quick Start

Tell the assistant to guide you through MARM setup for your agent and let it choose the transport, runtime, and connection details.

Frequently Asked Questions about marm-init

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up shared memory for multiple AI agents?

Shared memory for multiple AI agents is configured by validating the MARM engine and writing MCP connection details for each client. This links tools like Claude, Codex, and Cursor to a persistent local-first memory pool so they can read and write shared context.

Can I use Docker to run an MCP memory server locally?

You can use Docker to run an MCP memory server locally by selecting it as your runtime during setup. The guided installation helps verify the Docker runtime, generate API keys, and confirm server health after launch.

How do I configure MCP clients to use STDIO or HTTP transport?

Configuring MCP clients for STDIO or HTTP transport involves choosing the appropriate connection type and writing the corresponding MCP configuration entries. The setup process validates the transport selection and verifies server health across your agents.

Does shared agent memory work across different coding tools like VS Code and Cursor?

Shared agent memory works across different coding tools like VS Code and Cursor by linking MARM across MCP-capable clients. This multi-agent linking allows tools like Gemini, Qwen, and Claude to access the same persistent memory pool.

What is the best way to access a memory dashboard for browsing agent sessions?

Accessing a memory dashboard for browsing agent sessions is handled by starting or exposing the web dashboard during setup. This provides an interface to browse retained memories, active sessions, and logs from your connected agents.

Why do my agents keep losing project context between sessions?

Agents lose project context between sessions because they lack a persistent memory layer. Implementing a local-first shared memory infrastructure like MARM allows agents to retain decisions and share context without manual setup work.