X
XAGI-Lab/melra
Open-source local MCP runtime that checks AI-agent tool calls, gates risky actions on approval, verifies…
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Client config (built from the install command this repo gives)
{
"mcpServers": {
"xagi-lab-melra": {
"command": "npx",
"args": ["@melra/cli@alpha"]
}
}
}Parsed from the README we fetched on 2026-10-26; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"xagi-lab-melra": {
"command": "npx",
"args": ["@melra/cli@alpha"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio xagi-lab-melra -- npx @melra/cli@alpha
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 13 ★ · XAGI-Lab/melra · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-25 · last seen 2026-11-14 · seen 24× · listed by 2 sources
- Score
- score 203 · 13 ★ · 2 sources · repo
- Install
npx @melra/cli@alpha
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx @melra/cli@alpha. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
XAGI-Lab/melra；first catalogued 2026-10-25；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# MELRA
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
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:
bash
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 MELRAWORKSPACE 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):
text
Which MCP client should use MELRA?
1) Claude Code detected: 'claude' on PATH
2) Cursor detected: config file found
3) 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 |
### 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:
bash
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 MELRAWORKSPACE 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):
text
Which MCP client should use MELRA?
1) Claude Code detected: 'claude' on PATH
2) Cursor detected: config file found
3) 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 |
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/xagi-lab-melra/)
- Source
- github · https://github.com/XAGI-Lab/melra
- Browse by field
- Open source
- Traction
- 13 ★
- Listed by
- 2 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.