Connect the MCP server
Add the Hannu Model Context Protocol server to your agent and call the platform as native tools.
Hannu exposes a Model Context Protocol server at https://mcp.hannu.africa. An MCP-capable agent discovers the tools, calls them, and stays inside its spend policy — no glue code, no client to maintain.
Add it to your agent
// ~/.your-agent/mcp.json
{
"mcpServers": {
"hannu": {
"url": "https://mcp.hannu.africa",
"auth": "Bearer ${HANNU_KEY}"
}
}
}The server speaks JSON-RPC 2.0 over HTTP and implements initialize, tools/list, and tools/call. The bearer key maps to the same agent context — and the same governance — as the REST API.
Same platform, two front doors
MCP and REST are the same governed layer. Use MCP when your agent already speaks it; use REST for anything else. Every MCP tool has a REST equivalent and vice-versa.
For agent frameworks that negotiate OAuth 2.1, the server supports it and resolves the same agent identity. A static bearer key works everywhere.
Next
- The tool catalogue — 16 tools live today.
- MCP vs REST — parity and when to use which.
- What's absent by design.