wrapper 2026-10-10 wrappermcpschemadsh

dsh-mcp-rea: curated MCP face + rea_cli escape hatch

Some MCP hosts register **every** tool into every prefill. dsh-mcp-rea answers with a **curated face** plus `rea_cli`, so schema stays small without amputating capability.

Source meta

0 GitHub stars (snapshot)

Language: JavaScript

License: MIT

Updated: 2026-10-10

GitHub source ↗

rea.run rating

4/5 — Thin MCP bridge + CLI escape hatch

Quality. 21 curated tools ≈ 6.7 KB schema vs full ~1.83 MB; `rea_cli` keeps full CLI reach.

Evidence. Selftest covers handshake, schema size, escape-hatch passthrough.

Limits. Local DSH bundle pattern; Windows Ghidra PE-only caveats still apply.

For. Hosts that cannot filter tools/list (e.g. some DSH setups).

What it is. MIT thin-shell MCP server exposing 21 REA-oriented tools and a whitelisted rea_cli escape hatch. Aimed at DSH-style hosts without tool-filter fields.

Relation to REA. Depends on installed rea-agents CLI (REA_ENTRY recommended). Different cut than domain-split proxies: curation + escape hatch rather than group filters.

Workflow. Pin rea-agents → set REA_ENTRY / Ghidra env if needed → point host at server.mjs → run selftest.mjs.

Evaluation. Clear ops story for schema pain. Read Windows PE/DLL limits before expecting full native coverage.

Compliance

Bridge/packaging only — no crack content. Pair with legal-boundary + Windows×Ghidra docs.

Takeaways

Curate first; escape hatch second.
Schema size is a product constraint.
Native limits remain host/engine limits.

Related on rea.run