Nora runs on your own machine — the client starts it, so there is no endpoint to ping. 65 installs a week from npm. Last commit 15 Oct 2026.
Operate self-hosted OpenClaw and Hermes agent fleets on Docker or Kubernetes from MCP clients.
We read the source, 3 d ago · rules 995398eba69f
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
`rm -rf ${shellSingleQuote(HERMES_INTEGRATIONS_DIR)}`,
require("child_process").execFileSync(tsxBin, [file], { stdio: "inherit" });
path.join(appBackendsDir, name),
docker_probe='const http=require("http");const request=http.request({socketPath:"/var/run/docker.sock",path:"/_ping",method:"GET"},response=>{let body="";response.setEncoding("utf8");response.on("data",chunk=>body+=chunk);response.on("end",()=>process.exit(response.stat…
for (const entry of fs.readdirSync(currentDir, { withFileTypes: true })) {
const res = await deps.fetch(`https://api.telegram.org/bot${botToken}/getMe`);
# Need to install as root; the base image's final layer is `USER sandbox`. USER root # Global install so every user sees both binaries. npm on this base image uses # `/usr` as its global prefix (not `/usr/local`). Remove the inherited ~863 MB # OpenClaw tree before reinstalling…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Today is the operative word: we check Nora every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add nora -e 'NORA_API_URL=<NORA_API_URL>' -e 'NORA_API_KEY=<NORA_API_KEY>' -- npx -y @noraai/mcp-server
{
"mcpServers": {
"nora": {
"command": "npx",
"args": [
"-y",
"@noraai/mcp-server"
],
"env": {
"NORA_API_KEY": "<NORA_API_KEY>",
"NORA_API_URL": "<NORA_API_URL>"
}
}
}
}
[mcp_servers.nora]
command = "npx"
args = ["-y", "@noraai/mcp-server"]
env = { NORA_API_URL = "<NORA_API_URL>", NORA_API_KEY = "<NORA_API_KEY>" }
{
"mcpServers": {
"nora": {
"command": "npx",
"args": [
"-y",
"@noraai/mcp-server"
],
"env": {
"NORA_API_KEY": "<NORA_API_KEY>",
"NORA_API_URL": "<NORA_API_URL>"
}
}
}
}
{
"servers": {
"nora": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@noraai/mcp-server"
],
"env": {
"NORA_API_KEY": "<NORA_API_KEY>",
"NORA_API_URL": "<NORA_API_URL>"
}
}
}
}
Put your own values in place of
<NORA_API_URL> (Base URL of your Nora backend API (e.g. https://nora.example.com). Falls back to NORA_HOST, then the Nora CLI config at ~/.nora/config.json), <NORA_API_KEY> (Nora workspace API key (nora_…) used to authenticate against the Nora public REST API. Falls back to NORA_TOKEN, then the Nora CLI config).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
NORA_MCP_ALLOW_DESTRUCTIVE (Set to "true" to enable destructive tools (e.g. delete_agent). Disabled by default).
Operate a k3s / Kubernetes cluster from your AI agent — safe-by-default MCP server.
Build, deploy, and operate hosted web apps on VibeKit (vibekit.bot) from any MCP client.
OpenShift/Kubernetes cluster management via the oc CLI for MCP clients
Deploy self-hosted OpenClaw to AWS, GCP, Azure or a local VM — a CLI and an MCP server in one.
Governed Docker and Kubernetes operations for AI agents: scoped keys, guardrails, human approvals.
Kubernetes RCA agent that sandboxes its own AI with OPA Gatekeeper. MCP-ready for any client.
Mock OpenAPI specs locally, or log in to deploy hosted mocks on mockzilla.org from your MCP client.
Hosted MCP for creating, checking, deploying, and hosting static sites for AI agents.
Answers built from our own checks of this server.