Log inSubmit server
Nora logo

Nora

Operate self-hosted OpenClaw and Hermes agent fleets through Nora’s MCP interface.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Nora

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "nora": {
      "command": "npx",
      "args": [
        "-y",
        "@noraai/mcp-server"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @noraai/mcp-server

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 2d ago.

Overview

The Nora MCP server connects MCP clients to a self-hosted Nora control plane for operating OpenClaw and Hermes agent fleets. Nora manages deployments on Docker or Kubernetes and provides lifecycle controls, monitoring, logs, terminals, budgets, schedules, and workspace administration through its broader platform. Reach for it when an AI client needs to automate or inspect agents running on infrastructure your team controls.

Use cases

  • Operate OpenClaw fleets from an MCP client
  • Manage Hermes deployments on Kubernetes
  • Inspect agent logs, metrics, and costs
  • Apply budgets and scheduled runs to agents
  • Control self-hosted runtime lifecycles

Key features

  • OpenClaw and Hermes fleet management
  • Docker and Kubernetes deployment support
  • Agent lifecycle operations
  • Streaming logs and interactive terminals
  • Budgets, schedules, and monitoring
  • MCP, REST API, and CLI automation

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

7/7 checks healthy over the last 46d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11d ago via OSV.dev · @noraai/mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars58Stargazers on the source repository.
npm downloads138Package downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Nora works

What Nora MCP server does

Nora MCP server gives supported MCP clients an automation path into a self-hosted Nora deployment. Nora is designed to run fleets of OpenClaw and Hermes agents on infrastructure controlled by the operator. The platform exposes operator workflows under /app and platform administration under /admin, while the MCP package provides an agent-facing way to work with that control plane.

The surrounding Nora platform covers the agent lifecycle on Docker and Kubernetes. Operators can provision agents, start or stop them, restart or redeploy them, and review version history. Existing runtimes can also be recreated from uploaded bundles.

How it works

Nora runs as a self-hosted control plane rather than as a hosted fleet service. The quick-start path installs the full stack with Docker Engine and Compose v2 on macOS, Linux, or Windows through WSL2. A Kubernetes deployment is also available through a published OCI Helm chart. Once Nora is running, an MCP client can be configured to use the Nora MCP package and operate the fleet through the client interface.

The managed runtime targets are Docker and Kubernetes, both described as generally available in the README. Nora also lists an experimental Proxmox LXC target, but that option is not VM-grade isolation and should be treated differently from the primary deployment paths.

Nora’s control plane combines runtime operations with fleet visibility. The platform includes streaming logs, an interactive terminal, a file browser and editor, and embedded OpenClaw and Hermes interfaces. Monitoring includes per-agent metrics and cost information, along with a needs-attention view for conditions such as errors, stuck agents, budget overruns, or stalled telemetry.

Setup and configuration

The documented local installation requires Docker Engine and Compose v2. The installer checks for Docker, Git, and OpenSSL, can generate or preserve secrets, may create a bootstrap administrator, and selects another local port if the default is already occupied. The default local URL is http://localhost:8080, although setup can choose a different port.

macOS, Linux, and WSL2 users can run the repository’s shell installer. Windows users need PowerShell 7 or later and can use the PowerShell installer. Required secrets and ingress settings are covered by the linked Helm instructions.

Treat those details as installation-specific and obtain them from the package documentation before configuring an MCP client.

Tools and capabilities

Through the Nora MCP server, the relevant use case is controlling a Nora-managed agent fleet from an MCP client. The underlying platform supports capabilities including:

  • Deploying OpenClaw and Hermes agents to Docker or Kubernetes.
  • Starting, stopping, restarting, and redeploying agents.
  • Viewing logs, metrics, costs, and fleet attention states.
  • Running scheduled jobs with cron schedules, queue retries, and sweep guards.
  • Applying per-agent LLM budget limits with automatic pausing.
  • Managing encrypted provider secrets and supported integrations.
  • Working with workspaces, roles, account events, and platform administration.

Nora also provides a public REST API, an official CLI package, and the MCP package. The README names Claude Code, Gemini CLI, Claude Desktop, and Cursor as supported clients for the MCP automation path.

Limitations and notes

It therefore cannot establish whether every Nora UI operation is available through MCP. The MCP server also depends on a reachable, configured Nora installation; it is not described as a standalone replacement for the Nora control plane.

Security behavior is part of the platform configuration. Provider keys are encrypted at rest with AES-256-GCM and synchronized to running runtimes. Production startup requires a valid encryption key unless an operator intentionally enables the insecure plaintext override. Remote Docker hosts use SSH host-key pinning, and Kubernetes deployments include baseline network-policy ingress isolation with administrator-managed CIDR rules.

The platform advertises a catalog of 69 credential and connectivity entries and more than 17 LLM providers, but executable behavior comes from runtime skills or MCP adapters. Supported per-agent MCP servers must be enabled explicitly. Experimental NemoClaw and Proxmox LXC features have additional constraints and should not be treated as equivalent to the primary Docker and Kubernetes paths.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Nora

Nora is an MCP server that connects MCP clients to the self-hosted Nora agent operations platform. Its main tools provide automation access for managing OpenClaw and Hermes fleets, including deployment and lifecycle workflows, while Nora itself also handles monitoring, logs, budgets, schedules, and infrastructure administration.

Install and run the Nora control plane first, then configure the MCP package for your client using its package documentation.

Yes, Cursor is named as a supported client for Nora’s MCP automation. You still need a running self-hosted Nora control plane and the client configuration required by the `@noraai/mcp-server` package.

Yes, Nora can provision and operate OpenClaw and Hermes agents on Kubernetes. The project provides an OCI Helm chart for the full control plane and documents required secrets and ingress options in its Kubernetes setup instructions.

Related MCP servers

All in Coding Agents All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewNora AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/nora?style=directory)](https://allmcps.com/mcp/nora)
HTML Embed
<a href="https://allmcps.com/mcp/nora"><img src="https://allmcps.com/api/badge/nora?style=directory" alt="Nora on AllMCPs" /></a>