MELRA

Name: MELRA
Author: XAGI-Lab

by XAGI-Labversion 0.3.0-alpha.14i★ –iRuns on your computer

Registry nameio.github.XAGI-Lab/melra

Install

Overview

Description from the maker (original English)

Local MCP runtime for policy-governed, verified agent actions with durable receipts.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "melra": {
      "command": "npx",
      "args": [
        "-y",
        "@melra/cli",
        "serve"
      ]
    }
  }
}

Run this in your terminal

claude mcp add melra -- npx -y @melra/cli serve

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "melra": {
      "command": "npx",
      "args": [
        "-y",
        "@melra/cli",
        "serve"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "melra": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@melra/cli",
        "serve"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account XAGI-Lab, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32684 servers in this category
Published to the registry more recently than 64% of the other 32684 servers in this category
Basic checks equal to or better than 100% of the other 32684 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is MELRA safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.3.0-alpha.14) reached the registry 22 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Master CSS

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Master CSS

by master-co

Inspect Master CSS classes, generated CSS, and project stylesheets from your AI client.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

MELRA

Modular Execution Layer for Reliable Autonomy

Your AI agent decides what to do. MELRA governs how tool calls are authorized, verified, and recovered.

An open-source local execution runtime for agent tool calls you route through MELRA. It checks each call against policy, requests approval when needed, verifies declared evidence, and keeps a redacted receipt of what runs to an outcome. For each task, MELRA dispatches mutations at most once; uncertain outcomes are parked for reconciliation instead of replay. Exactly-once external effects still depend on the provider. Calls made through other tools remain outside MELRA's control.

Works with

26-second demo · Quick start · How it works · See what it is doing · Docs · Contribute · Discussions · Product Hunt launch

26-second demo

https://github.com/user-attachments/assets/e5cf895d-7ea6-4797-a1ef-e69cc5860d3f

[!WARNING]

MELRA is alpha software. The local runtime is tested end to end, but APIs may

change before 1.0. Use an isolated workspace, keep domain and command allowlists

narrow, and read every approval before you give it.

Quick start

You need Node.js 22.13 or newer, or 23.4 or newer. From the project the agent should work in, one command sets everything up:

cd ~/project

npx @melra/cli@alpha setup

That directory becomes the agent's workspace, the boundary for its file and command operations. setup shows it, and asks before making your home directory, a directory holding it, or / the workspace; set MELRA_WORKSPACE to choose another.

In a terminal, setup is a short wizard. It writes a safe local policy, finds the agent apps on your machine, asks which one should use MELRA, and writes MELRA into that app's own config file, keeping everything else in it (and saving a .bak first):

Which MCP client should use MELRA?

Claude Code detected: 'claude' on PATH
Cursor detected: config file found
Gemini CLI detected: config folder found ...

Choose 1-26 [1]: 1 Write it into ~/project/.mcp.json? [Y/n]

✓ Workspace ~/project ✓ Policy ~/.melra/policy.json ✓ Claude Code ~/project/.mcp.json

Next: Start claude in this workspace and approve the 'melra' server when it asks; 'claude mcp list' then shows it connected. Or start it with 'melra launch claude-code', so MELRA's are the only tools it has that change anything.

Then restart your agent app (Claude Code asks you to approve a project's server once) and ask it to do something, for example *"use melra to show me the system info"*. That's it.

Prefer flags, a container, or building from source?

How	Command
One client, no questions	`npx @melra/cli@alpha setup --client cursor --write`
Print the config instead of writing it	`npx @melra/cli@alpha setup --client codex`
Install globally	`npm install -g @melra/cli@alpha && melra setup`
Container (no Node needed)	`docker run --rm ghcr.io/xagi-lab/melra:alpha doctor`
Prebuilt release	download from releases, verify against `SHA256SUMS`, then `node melra/dist/bin.js doctor`
From source	`git clone https://github.com/XAGI-Lab/melra.git && cd melra && corepack enable && pnpm install --frozen-lockfile && pnpm build && pnpm melra setup`
One file, no Node needed (experimental)	from a checkout: `pnpm build:sea`, then `./dist-sea/melra setup`; see single executable
Check what you installed	`npm audit signatures` verifies registry signatures; npm provenance links each package to its GitHub Actions build (see npm packages)

Every command prints readable output in a terminal and plain JSON when piped or with --json, so scripts keep working. MELRA creates /payload.key with private permissions on first start; back it up with the SQLite files, because losing it makes persisted payloads unreadable. See installation for every install path, environment variable, and the hardened Docker invocation.

[!CAUTION]

This project publishes only under the @melra/ npm scope (@melra/cli is the CLI)

and on its releases, where the Python

SDK's wheel is. An unscoped npm package melra or a PyPI package melra is

not this project's. Install from that scope, from this repository, or from the

releases.

If MELRA helps, star the repository so other agent builders can find it. Trying it in Cursor or another client? Share the client and its version, your OS, and your MELRA version (npx @melra/cli@alpha version) in issue #184; partial test results are useful too.

What is MELRA?

AI agents no longer just talk. They edit files, run commands, click through websites and call APIs on your behalf. Four questions come with that, and most agents answer them differently, or not at all:

🛡️ Is it allowed?

Every action MELRA receives is checked against your policy, and checked again at the moment it runs. Risky changes wait for your exact approval.

✅ Did it really work?

"No error" is not success. An action counts only when the evidence you declared holds: the file exists, the exit code is 0, the page says what it should. For a file change or a memory delete MELRA also checks the end state itself: a written file holds exactly the bytes sent.

🔁 What if it crashes?

Every mutation MELRA dispatches is recorded before it runs and runs at most once. After a crash, MELRA settles it from its evidence or the provider; what it cannot settle waits in recovery_required and is never replayed.

🧾 What happened?

Every action MELRA runs to an outcome leaves a redacted, append-only receipt and a certificate that carries its own digest, so you can audit what ran, who asked, and why it was allowed.

MELRA answers those questions in one place for tool calls routed through it, across supported agents. It sits underneath your agent for those calls, the way an operating system sits underneath your apps:

<img src="docs/assets/read

Only the beginning is shown; read the rest in the repo

MELRA

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Master CSS

README from the maker

MELRA

Your AI agent decides what to do. MELRA governs how tool calls are authorized, verified, and recovered.

26-second demo

Quick start

What is MELRA?

🛡️ Is it allowed?

✅ Did it really work?

🔁 What if it crashes?

🧾 What happened?