Manoma

io.github.paperdavidPublished by GitHub account paperdavidv0.2.1Updated Oct 24, 2026

MCP server for soul.md — your portable AI identity layer across every LLM.

VerifiedSTDIODesktop onlyProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Manoma is a local MCP server that reads a user-owned soul.md identity file, letting an assistant recall your values, voice and focus and record decisions and l

What you can do
Read the soul.md identity file: fetch context, list its sections and check skill depth for the current session. Write back to the file: add a decision, add a lesson, or update the current focus, each provenance-stamped, sanitized and disclosed. Keep your identity portable across LLM tools as a plain-text file that versions in git.
When to use it
Use it when you keep a soul.md file and want assistants to know your values, voice and current focus across sessions and tools, and to record decisions and lessons back into that file as you work.
Requirements
Runs as a local process via npx (Node.js). The SOUL_MD_PATH environment variable points to your soul.md file and defaults to ~/soul.md. No account, cloud service or authentication is required.
Before you install
The write-back tools add decisions, lessons and focus updates to your soul.md file; the README says changes require your approval and are visible as git diffs, but review them. The file holds personal identity details, so keep it out of shared or public repositories.

Installation

In SourceWeft

  1. Open Manoma in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

soul.md

Your identity, not theirs. One plain-text file that tells every AI who you are — and that you own.

soul.md is an open format for your AI identity: values, voice, skills, current focus. It lives on your machine, versions in git, and gets compiled into the tools you use. Manoma is the CLI and MCP server that make it work.

bash
npx manoma init        # create your soul.mdnpx manoma interview   # let an AI you already use write it with younpx manoma compile     # wire it into Claude Code — every session knows you

Two more commands close the loop with your AI's own memory:

bash
npx manoma refresh     # the AI that's been learning about you proposes updates                       # to your file — your approval required, never silentnpx manoma remember    # save your soul.md INTO the AI's memory, so even plain                       # chats with zero setup know you

Their memory collects; your file is the owned, current copy.

  • User-owned — a file on your machine. No cloud, no account, no vendor.
  • Works everywhere — compiled into tool configs, pasted into instruction fields, readable by anything.
  • Stays alive — add the MCP server and the AI records decisions and lessons into the file as you work, dated and signed; every change is a git diff.

The format

The specification is one page and public domain (CC0): eight plain-markdown sections, a deterministic grammar, and one invariant — a soul.md must stay useful pasted raw into any prompt. Every file written for the older v1.4 format keeps working (migration guide).

The conformance corpus defines correct parsing; a reader that reproduces its expected outputs is conformant. Parallel implementations are welcome — a Python or Rust parser that passes the corpus is a first-class citizen.

The MCP server

json
{  "mcpServers": {    "manoma": { "command": "npx", "args": ["-y", "manoma-mcp"] }  }}

One block in Claude Desktop, Cursor, or any MCP client. Six tools: get_context, get_skill_depth, list_sections, and the write-back trio add_decision / add_lesson / update_now — provenance-stamped, sanitized, disclosed. Details in mcp/README.md.

Repo

manoma/├── mcp/          — the MCP server + manoma CLI (npm: manoma-mcp, manoma)├── cli/          — the `manoma` npm name (forwards to manoma-mcp)├── conformance/  — the normative parsing corpus├── docs/         — migration guide, archived v1.4 spec├── templates/    — v1.4-era example files (valid, being modernized)├── SPEC.md       — the format specification (CC0)└── LICENSE       — MIT (code)

Philosophy

Every AI vendor keeps its own memory of you, in its own cloud. soul.md is the opposite bet: your identity as a plain file you control, portable between tools, diff-able in git, built to outlive any individual model.

The schema is the thing. The runtime is just how it's read.

Feedback, forks, and parallel implementations welcome — issues. MIT / CC0.

Source: README.md at commit fa5cc3f

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts