Skip to main content

africa-coord-bus

The coordination layer between East Africa's AI tools.

MCP servers exist for Kenya's coordination domains — payments, water, agriculture, health, land, education. They work in isolation. When a drought signal is raised (today wapimaji-mcp produces simulated ones), bima-mcp doesn't know to evaluate parametric insurance payouts. afya-mcp doesn't know to activate malnutrition surveillance. kilimo-mcp doesn't know to issue drought-resistant crop advisories.

This package provides the event bus that connects them.

The coordination gap

A smallholder farmer in Turkana has parametric crop insurance. NDVI anomaly data shows drought coming 6 weeks out. The insurance contract says coverage triggers when SPI drops below -1.5.

Without coordination: the farmer finds out the crop is failing at harvest. The insurance company finds out at claims submission. The health system finds out at clinic presentation.

With coordination:

wapimaji-mcp → CoordinationEvent(drought_alert, ALERT)
    │
    ├── bima-mcp.evaluate_parametric_payout      (triggered immediately)
    ├── kilimo-mcp.issue_drought_advisory         (farmers receive SMS)
    ├── afya-mcp.activate_malnutrition_watch      (CHWs briefed)
    └── county-mcp.alert_county_health            (county notified)

Six weeks earlier. Before the damage is visible.

AI Agent Compatibility

Model-agnostic: any MCP-capable model can drive these tools. No model is recommended or certified here; keep a person approving consequential actions.

Architecture: Shared Context Store (CA-MCP)

Research validation: Enhancing MCP with Context-Aware Server Collaboration (arXiv:2601.11595, January 2026) — introduces CA-MCP, adding a Shared Context Store (SCS) to stateless MCP. Results:

  • Statistically significant reduction in LLM calls for complex multi-server tasks
  • Decreased response failures when task conditions are not immediately satisfied
  • Validated on TravelPlanner and REALM-Bench benchmarks

africa-coord-bus implements a compatible event-driven shared context pattern: the coordination bus acts as the SCS for cross-domain cascades. A drought event from wapimaji-mcp propagates context (severity, county, affected area) to bima-mcp, kilimo-mcp, and county-mcp without each server re-establishing that context independently.

The disconnected models problem (Krishnan, arXiv:2504.21030): stateless MCP servers lack global context — making coordination buses like this one structurally necessary, not optional, for multi-domain agents in East Africa.

Install

pip install africa-coord-bus

Usage

from africa_coord_bus import (
    EventBus, CoordinationEvent, DomainCascade,
    EventDomain, EventSeverity, KenyaLocation
)

# Create bus with offline queue
bus = EventBus(queue_path="/var/coord-bus/queue.jsonl")

# Wire all domain cascade handlers
cascade = DomainCascade(bus)
cascade.wire_all()

# Publish a drought signal from wapimaji-mcp
event = CoordinationEvent(
    domain=EventDomain.WATER,
    event_type="drought_alert",
    source="wapimaji-mcp",
    severity=EventSeverity.ALERT,
    location=KenyaLocation(county="Turkana", county_code=23),
    data={
        "ndvi_anomaly": -0.28,
        "spi_3month": -1.8,
        "rainfall_deficit_pct": 42,
    },
)

targets = bus.publish(event)
# → [WATER→FINANCE] bima-mcp.evaluate_parametric_payout | Turkana | drought_alert | alert
# → [WATER→AGRI]    kilimo-mcp.issue_drought_advisory    | Turkana | drought_alert | alert
# → [WATER→HEALTH]  afya-mcp.activate_malnutrition_watch | Turkana | drought_alert | alert

Built-in routing rules

Trigger Cascade
water.drought_alert (WARNING+) bima-mcp.evaluate_parametric_payout, kilimo-mcp.issue_drought_advisory, soko-mcp.price_alert
water.drought_alert (ALERT+) + afya-mcp.activate_malnutrition_watch, county-mcp.alert_county_health
health.disease_outbreak (cholera/typhoid) wapimaji-mcp.flag_water_risk
health.disease_outbreak (WARNING+) county-mcp.health_alert, fomu-mcp.emergency_procurement
agriculture.price_spike (>30% above seasonal) afya-mcp.food_security_watch, bima-mcp.food_security_eval
water.flood_alert (WARNING+) afya-mcp.waterborne_watch, county-mcp.flood_response

Add custom rules:

from africa_coord_bus import RoutingRule, EventDomain, EventSeverity

bus.routing.add(RoutingRule(
    name="outbreak→emergency_procurement",
    description="Disease outbreak triggers essential medicine procurement",
    trigger_domain=EventDomain.HEALTH,
    trigger_event_type="disease_outbreak",
    trigger_min_severity=EventSeverity.ALERT,
    target_actions=["fomu-mcp.emergency_medicine_order"],
))

Offline-first

Events are written to a local queue before dispatch. If dispatch fails, events persist for replay:

bus = EventBus(queue_path="/var/coord-bus/events.jsonl")
# ... system restart ...
bus.replay_queue()  # processes all unhandled events

All available at pypi.org/user/gmahia:

  • wapimaji-mcp — drought intelligence (publishes water.drought_alert)
  • bima-mcp — parametric insurance (consumes drought events)
  • kilimo-mcp — agricultural coordination (consumes drought + price events)
  • afya-mcp — health coordination (consumes drought + flood + disease events)
  • mpesa-mcp — M-Pesa payments (handles insurance payouts)

Integration with wapimaji-mcp

wapimaji-mcp v0.1.3+ includes built-in coordination publishing. When drought phase ≥ 2 (Stressed), it automatically fires coordination events:

# wapimaji-mcp now exposes this MCP tool:
result = call_mcp_tool("publish_drought_coordination", {
    "county": "Turkana",
    "phase": 3,
    "rainfall_deficit_pct": 42.0
})
# → fires 5 downstream actions automatically via africa-coord-bus

See examples/wapimaji_drought_cascade.py for the complete integration.

IP & Collaboration

MIT licensed. Feedback via GitHub Issues only — pull requests are not accepted. Demo data is labeled DEMO and is not suitable for operational decisions. Full policy: docs/architecture/IP_POLICY.md. Security reports: see SECURITY.md.

Part of the East Africa coordination stack

Model-agnostic by design: closed APIs, open-weight models, and small distilled models are all first-class citizens.

Interoperability: CAP 1.2 export

Events can be emitted as OASIS Common Alerting Protocol (CAP) 1.2 so a county, ministry, or warning network can consume them with existing tools — no need to adopt this bus:

from africa_coord_bus import CoordinationEvent, to_cap_xml
xml = to_cap_xml(event)   # valid CAP 1.2; also to_cap_dict(event)

Trust integrity is preserved: a DEMO/synthetic event is emitted as status=Exercise, never Actual, so a test signal cannot be mistaken for a live public alert.

Offline sync: conflict-free queue merge (CRDT)

Events are immutable and uuid-keyed, so two offline queues reconcile by union — a grow-only set (G-Set), the simplest CRDT. merge_queues is idempotent, commutative, and associative, so devices sync in any order and replay is safe:

from africa_coord_bus import merge_queues, write_queue
merged = merge_queues("device_a/queue.jsonl", "device_b/queue.jsonl")  # deduped by event_id
write_queue(merged, "synced/queue.jsonl")

Humanitarian interop: HXL + IPC hint

from africa_coord_bus import to_hxl_row, ipc_severity_hint
to_hxl_row(event)          # HXL-tagged row for HDX / HXL Proxy tooling
ipc_severity_hint(event)   # coarse IPC-phase HINT (food-security domains) — NOT an IPC classification

The IPC helper is a legibility hint only; its caveat is embedded in the return value and it never assigns Phase 5 (Famine), which is a formal analytical act.

Provenance: trust integrity as a declared field

Every event declares its reality and epistemic confidence, so downstream systems never have to guess:

from africa_coord_bus import CoordinationEvent, EventReality, EventConfidence
CoordinationEvent(..., reality=EventReality.DEMO, confidence=EventConfidence.PROBABLE)
  • reality (REAL | DEMO) — a DEMO event can never export as a live CAP alert (status=Exercise), declared not string-sniffed. Default REAL.
  • confidence (CONFIRMED | PROBABLE | SPECULATIVE | UNKNOWN) — the epistemic ladder; flows into CAP certainty (Observed/Likely/Possible/Unknown). Default UNKNOWN — undeclared confidence is never assumed.

Metadata

Release files for africa-coord-bus 0.4.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for africa-coord-bus 0.4.1
File Size Uploaded Provenance Actions
africa_coord_bus-0.4.1.tar.gz 33.8 kB With provenance Details for africa_coord_bus-0.4.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for africa-coord-bus 0.4.1
File Interpreter ABI Platform Actions
africa_coord_bus-0.4.1-py3-none-any.whl Python 3 none any Details for africa_coord_bus-0.4.1-py3-none-any.whl

Total release size: 59.9 kB

Release files / africa_coord_bus-0.4.1.tar.gz

Download URL africa_coord_bus-0.4.1.tar.gz
Size 33.8 kB
Tags Source
SHA-256 checksum
How to use checksums
ccc9322e331cc4b5c34acdeb1aaf05c09372e69c7f80338daae26de7d7c02986
BLAKE2b-256 checksum
How to use checksums
5c9aa011acfc08be32e2ecf5f0ff0845aac89af0989da886e60e43bb600d60ba
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.

Transparency log

Release files / africa_coord_bus-0.4.1-py3-none-any.whl

Download URL africa_coord_bus-0.4.1-py3-none-any.whl
Size 26.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
1975079503ebd6c8736cb87d5c7661b274ee7df47ad64e3afd04df69fd13db18
BLAKE2b-256 checksum
How to use checksums
03a737fc3b9e191478ef47f1dca20a75ae82cd93fc03deaff7506bb8d5319e36
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.

Transparency log

Security for africa-coord-bus 0.4.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for africa_coord_bus-0.4.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page