# Nora [Health: Active]

**Category:** 🤖 Coding Agents  
**Repository:** https://github.com/solomon2773/nora  
**GitHub Stars:** 58  
**npm Downloads (last month):** 138  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/nora

## Description
Operate your self-hosted Nora agent fleet from MCP clients.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "nora": {
    "command": "npx",
    "args": ["-y","@noraai/mcp-server"]
  }
}
```

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/nora/readme_