@nyuchi/mukoko-events-mcp
v2.0.0-beta.1
Published
MCP server for Mukoko Events (events.mukoko.com) — discover and manage community events across Africa. Stdio bridge to the hosted Streamable HTTP endpoint at events.mukoko.com/mcp.
Maintainers
Readme
@nyuchi/mukoko-events-mcp
Locally-installable MCP server for Mukoko Events (events.mukoko.com) — discover and manage community events across Africa (the platform is also branded Nhimbe).
This package is a thin stdio ⇄ Streamable-HTTP bridge to the hosted server
at https://events.mukoko.com/mcp. It owns no logic: every tool call is relayed
to the hosted endpoint, which is the single trust boundary. Same tools, same
behaviour as the remote connector — this just lets stdio-only clients (Claude
Desktop, Cursor, and similar) run it locally over npx.
Clients that speak Streamable HTTP directly (Claude, ChatGPT connectors) can skip this package and connect straight to
https://events.mukoko.com/mcp.
Usage
npx @nyuchi/mukoko-events-mcp@beta(While 2.x is in beta the package publishes under the beta dist-tag; drop
@beta once 2.0.0 ships.)
Claude Desktop / stdio client config
{
"mcpServers": {
"mukoko-events": {
"command": "npx",
"args": ["-y", "@nyuchi/mukoko-events-mcp@beta"]
}
}
}Reads vs. writes
Reads (discover, search, get an event) work anonymously.
Writes (create / update an event) require a WorkOS bearer token. Set
MUKOKO_EVENTS_TOKENand the bridge forwards it as anAuthorizationheader on every request:{ "mcpServers": { "mukoko-events": { "command": "npx", "args": ["-y", "@nyuchi/mukoko-events-mcp@beta"], "env": { "MUKOKO_EVENTS_TOKEN": "<workos-access-token>" } } } }
Environment / arguments
| Variable / arg | Purpose | Default |
| ---------------------- | ----------------------------------------------------------------- | -------------------------------- |
| MUKOKO_EVENTS_MCP_URL| Override the hosted endpoint (or pass it as the first CLI arg). | https://events.mukoko.com/mcp |
| MUKOKO_EVENTS_TOKEN | WorkOS bearer token; enables the write tools when set. | (unset — reads only) |
Testing with the MCP Inspector
The MCP Inspector drives the bridge as a stdio server — no install needed:
# Interactive UI (tools, resources, prompts, notifications)
npm run inspect
# or headless, list tools and exit
npm run inspect:list
# a read-only tool call
npx @modelcontextprotocol/inspector --cli node bin/mukoko-events-mcp.js \
--method tools/call --tool-name events_near_me --tool-arg city=HarareEvent tools return three parts: a plain-text summary, a self-contained
text/html UI resource (ui://nhimbe/events — the card/carousel that lets
hosts visualize events inline), and structuredContent for programmatic use.
License
MIT © Nyuchi Web Services
