Nora 0.1.4 is live in the MCP Registry: self-hosted OpenClaw and Hermes fleet operations

[solomon2773]

Hi — I maintain Nora, an Apache-2.0 self-hosted control plane for operating OpenClaw and Hermes agent fleets.

The operator dashboard for the fleet exposed through the MCP server.

We published the Nora MCP server to the official registry as io.github.solomon2773/nora, with the current release at 0.1.4 through @noraai/mcp-server. The npm package was published with provenance, and a clean initialize/list-tools handshake reports 15 default safe tools.

The stdio integration exposes:

• Agent inventory, status, runtime details, and configuration history
• Fleet health, monitoring events, usage metrics, and per-agent cost
• Lifecycle operations protected by workspace-scoped Nora API keys
• An additional destructive-operation gate: delete_agent is not registered unless NORA_MCP_ALLOW_DESTRUCTIVE=true

For a read-only setup, the API key only needs agents:read and monitoring:read. The server runs locally and sends requests directly to the operator's configured Nora deployment.

Registry entry:
https://registry.modelcontextprotocol.io/?q=io.github.solomon2773%2Fnora

Source for the published package:
https://github.com/solomon2773/nora/tree/d38024cfce325d9fde6616b11c81628d2d323957/mcp-server

Documentation:
https://noradocs.solomontsao.com/guides/mcp-server

I would particularly value technical feedback on the read-versus-lifecycle tool boundary and whether the least-privilege setup is clear enough in the registry metadata.