← FAQ hub

FAQ · P1

MCP domain-split proxy for REA

When the full tools/list is too large for your host, filter by domain groups instead of corrupting schemas.

Problem

REA can advertise a large catalog (community measurements around ~139 tools / hundreds of thousands of tokens). Strict clients and bounded prefills reject the session — see MCP schema size.

Pattern: stdio filter proxy

A community MIT project, ghirardo-giorgio/REA-MCP-Split, sits between the MCP host and REA as a stdio filter proxy. It:

• Keeps a maintainable group catalog (e.g. session, core, native).
• Exposes only the groups you enable — measured slices can drop token cost dramatically (e.g. session,core,native vs full catalog).
• Ships catalog update helpers so the filter stays aligned with upstream tool names.

This is packaging / proxy — not a fork of REA’s analysis engines and not a crack tool.

Operator steps (conceptual)

1. Install and pin rea-agents as usual; confirm doctor on your host.
2. Clone or install the domain-split proxy; point it at your REA entry.
3. Enable only the domain groups your session needs; leave heavy native groups off until required.
4. Register the proxy as the MCP server in the client (not the full REA server), then reconnect.
5. If a needed tool is missing, add its group — do not paste truncated/malformed JSON schemas to “beat” provider caps.

Related cuts

• dsh-mcp-rea — curated thin face + rea_cli escape hatch for hosts that cannot filter tools at all.
• Upgrade upstream rea-agents when schema compaction lands; prefer CLI for one-off heavy jobs.

Compliance

Proxying tool catalogs does not change the legal target rule: analyze only software you are authorized to inspect. See legal boundary.