norc

io.github.norcappPublished by GitHub account norcappv0.3.2Updated Nov 3, 2026

Manage cron jobs, machines and run history in your norc account from any AI chat.

VerifiedStreamable HTTPWeb executable

Overview

norc's hosted MCP server (mcp.norc.app); API key required; Streamable HTTP.

No AI overview yet: these facts come from the registry entry and the server itself.

Endpoint
mcp.norc.app
Last checked

Installation

In SourceWeft

  1. Open norc in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.norcapp%2Fnorc-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "norc": {
      "type": "http",
      "url": "https://mcp.norc.app/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

norc-mcp

[npm] [npm downloads] [Docker] [Docker pulls] [MCP Registry] [License: MIT] [mcptry] [Glama]

MCP server for connecting AI platforms (Claude, ChatGPT, etc.) to your norc account — manage cron jobs, machines, and run history from a chat.

Setup

  1. Generate a norc API key: vault → Settings → API Keys → Generate key.
  2. Install it for your client (below). Hosted option: point a client that supports remote servers at https://mcp.norc.app/mcp with your key as the Bearer token (exact field depends on the client).

Install

Claude Desktop

  1. Install Node.js 20 or newer (Claude Desktop runs the server with npx).
  2. Open Claude Desktop → Settings → Developer → Edit Config. This opens claude_desktop_config.json:
    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
    • Windows: %APPDATA%\Claude\claude_desktop_config.json (Microsoft Store install: %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\claude_desktop_config.json)
  3. Add norc under mcpServers (keep any servers already there) and use your own key (vault → Settings → API Keys):
    json
    {  "mcpServers": {    "norc": {      "command": "npx",      "args": ["-y", "norc-mcp"],      "env": { "NORC_API_KEY": "norc_sk_..." }    }  }}
    On Windows, npx is a .cmd script and may fail to launch directly; use cmd instead:
    json
    "command": "cmd","args": ["/c", "npx", "-y", "norc-mcp"]
  4. Quit Claude Desktop completely and reopen it. Closing the window is not enough. norc's tools then appear in the tools menu.

Claude Code

Install the norc plugin, which adds slash commands and starts this server for you, or add it directly:

claude mcp add norc --env NORC_API_KEY=norc_sk_... -- npx -y norc-mcp

Other local MCP clients (Cursor, etc.)

Use the same command / args / env block as the Claude Desktop config above. Without NORC_API_KEY (or --stdio) the server starts in HTTP mode instead, and a missing or malformed key in stdio mode exits with an error.

Hosted (remote clients)

For clients that only support remote servers, use https://mcp.norc.app/mcp (Streamable HTTP, POST) with the header Authorization: Bearer norc_sk_.... It is the same code as this repo, deployed on Vercel; your key is forwarded to vault.norc.app and not stored.

Tools

  • list_jobs, create_job, update_job, delete_job
  • list_machines, rename_machine, delete_machine
  • list_runs
  • sync_jobs — declarative sync of your full job set (like norc gitops). Dry run by default; jobs not listed are deleted when apply is true. Needs the gitops sync feature enabled on your account.

Self-hosting (HTTP)

This server is a thin, stateless client — it holds no secrets and no database access of its own. It only forwards your API key to vault.norc.app (or $NORC_VAULT_URL). Run your own instance if you'd like:

bash
pnpm installpnpm buildPORT=3000 node dist/server.js

Note: self-hosting this server does not mean self-hosting norc itself — it still talks to the hosted norc API.

Run via Docker

bash
docker run -p 3000:3000 norcapp/norc-mcp

Set NORC_VAULT_URL if you're pointing at a non-default vault instance:

bash
docker run -p 3000:3000 -e NORC_VAULT_URL=https://vault.norc.app norcapp/norc-mcp

License

MIT

Source: README.md at commit c6f83c9

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.3.2LatestNov 3, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts