{"slug": "building-coordination-infrastructure-what-32-mcp-servers-without-a-bus-look-like", "title": "Building Coordination Infrastructure: What 32 MCP Servers Without a Bus Look Like", "summary": "A developer has released africa-coord-bus, an open-source coordination layer for 32 Model Context Protocol (MCP) servers covering Kenya's coordination domains such as water, health, and agriculture. The tool defines a standard CoordinationEvent schema and an EventBus that routes cross-domain events to the appropriate MCP servers, enabling automated responses like triggering water quality checks when a cholera outbreak is flagged. The project is available on GitHub and PyPI, and is designed to be installable with a single pip command.", "body_md": "Thirty-two MCP servers for Kenya's coordination domains.\n\nWater. Health. Agriculture. Insurance. Land. Education. Transport. Tax. Labor. Market prices.\n\nEach one works. None talks to any other.\n\nThis is what 32 isolated tools looks like in practice: a CHW in Kisumu flags a cholera cluster. The water quality system doesn't know. The county procurement system doesn't know. The emergency medicine supply chain doesn't know. The tools that need to respond are all present. The coordination between them doesn't exist.\n\nThe Model Context Protocol ecosystem is growing fast. For most of the world, it's growing in domains that already have coordination infrastructure: calendar apps, email clients, project management tools. These tools coordinate with each other through years of API integrations, webhooks, Zapier connections, and shared data stores.\n\nAfrican coordination domains don't have that legacy. They're being built now, from scratch, on MCP.\n\nThat means the coordination layer has to be built at the same time.\n\n[ africa-coord-bus](https://github.com/gabrielmahia/africa-coord-bus) defines a\n\n`CoordinationEvent`\n\n— a standard cross-domain signal schema — and an `EventBus`\n\nthat routes events to the tools that need to respond.The routing table is explicit:\n\n| Trigger | Cascade |\n|---|---|\n`water.drought_alert` (Warning+) |\nbima-mcp, kilimo-mcp, soko-mcp |\n`water.drought_alert` (Alert+) |\n+ afya-mcp, county-mcp |\n`health.disease_outbreak` (cholera) |\nwapimaji-mcp water quality check |\n`agriculture.price_spike` (>30%) |\nafya-mcp food security watch |\n`water.flood_alert` |\nafya-mcp waterborne watch, county-mcp |\n\nCustom rules take three lines:\n\n``` python\nfrom africa_coord_bus import RoutingRule, EventDomain, EventSeverity\n\nbus.routing.add(RoutingRule(\n    name=\"locust→emergency_procurement\",\n    trigger_domain=EventDomain.AGRICULTURE,\n    trigger_event_type=\"locust_swarm\",\n    trigger_min_severity=EventSeverity.ALERT,\n    target_actions=[\"fomu-mcp.emergency_procurement\", \"county-mcp.agriculture_alert\"],\n))\n```\n\nThe pattern that's emerging for East Africa:\n\n```\nPublic domain datasets (HuggingFace)\n        │ grounding knowledge\n        ▼\n32 MCP servers (PyPI) ←── africa-coord-bus\n        │\n        ▼\nA2A + ADK agents\n        │\n        ▼\nStreamlit coordination interfaces\n```\n\nEach layer is replaceable. The models are replaceable. The MCP servers are replaceable. What persists is the coordination architecture.\n\n```\npip install africa-coord-bus\n```\n\nSource: [github.com/gabrielmahia/africa-coord-bus](https://github.com/gabrielmahia/africa-coord-bus)\n\nThe coordination gap was the last missing layer. It's now installable.\n\nSource: [africa-coord-bus on PyPI](https://pypi.org/project/africa-coord-bus/)", "url": "https://wpnews.pro/news/building-coordination-infrastructure-what-32-mcp-servers-without-a-bus-look-like", "canonical_source": "https://dev.to/gabrielmahia/building-coordination-infrastructure-what-32-mcp-servers-without-a-bus-look-like-243c", "published_at": "2026-08-03 10:00:00+00:00", "updated_at": "2026-08-03 10:11:42.085131+00:00", "lang": "en", "topics": ["developer-tools", "ai-infrastructure", "ai-agents"], "entities": ["africa-coord-bus", "MCP", "Kenya", "HuggingFace", "PyPI", "GitHub", "A2A", "ADK"], "alternates": {"html": "https://wpnews.pro/news/building-coordination-infrastructure-what-32-mcp-servers-without-a-bus-look-like", "markdown": "https://wpnews.pro/news/building-coordination-infrastructure-what-32-mcp-servers-without-a-bus-look-like.md", "text": "https://wpnews.pro/news/building-coordination-infrastructure-what-32-mcp-servers-without-a-bus-look-like.txt", "jsonld": "https://wpnews.pro/news/building-coordination-infrastructure-what-32-mcp-servers-without-a-bus-look-like.jsonld"}}