reli

East Africa has 30+ open MCP servers covering payments, tax, health, drought, land, counties, labour rights, and more — but an AI agent builder had to discover, install, and hand-wire each one into their client. The stack existed; the on-ramp didn't.

reli (Swahili: rails) is that on-ramp. One command chain takes any MCP-capable client from zero to the full Kenya coordination stack:

pip install reli-cli
reli up --pack core        # install + wire into Claude Desktop + verify

Under two minutes. Then ask your agent: "what Kenya-stack tools do you have?"

Commands

reli list                  # every component, grouped by domain pack
reli list --pack financial # payments, tax, credit, insurance, markets
reli install health        # or any pack, server name, or "all"
reli config                # wire installed servers into Claude Desktop (backs up first)
reli config --stdout       # print JSON for any other MCP client
reli doctor                # verify every installed component imports cleanly
reli demo drought          # watch one signal cascade across five institutions

Domain packs

The demo

reli install core && reli demo drought

A drought alert in Baringo fires real routing rules from africa-coord-bus: parametric insurance evaluation, drought-resistant crop advisory, malnutrition surveillance activation, county alerts, market price signals. One signal, multiple institutions, zero phone calls — that is the coordination gap this stack closes.

Trust integrity

Stack servers ship DEMO datasets — illustrative, not live institutional feeds. Do not use outputs for operational, financial, medical, or legal decisions. No partnership with any government, regulator, or financial institution is implied.

The wider stack

Full developer reference: The Nairobi Stack

IP & Collaboration

MIT licensed. Feedback via GitHub Issues only — pull requests are not accepted. Full policy: docs/architecture/IP_POLICY.md. Security reports: see SECURITY.md.