norc-mcp
norc-mcp is an MCP server connecting AI platforms like Claude and ChatGPT
to your norc account — manage cron jobs, machines, and run history from a
chat interface, no dashboard required.
It’s a thin, stateless client: it holds no secrets and no database access
of its own, and only forwards your API key to vault.norc.app (or
$NORC_VAULT_URL). MIT licensed.
- Generate a norc API key: vault → Settings → API Keys → Generate key.
- Add the server to your MCP client’s connector config, pointing at
https://mcp.norc.app/mcpwith your key as the Bearer token (the exact field depends on the client).
Claude Code reads a server name plus a single server-config object via
claude mcp add-json:
claude mcp add-json norc '{"type":"http","url":"https://mcp.norc.app/mcp","headers":{"Authorization":"Bearer norc_sk_your_api_key_here"}}'Claude Desktop doesn’t support remote (http) servers directly in
claude_desktop_config.json — that file is for local, stdio-launched
servers only. Reach the same endpoint through the
mcp-remote bridge, which runs
locally and proxies stdio to the remote URL. Paste this into the
mcpServers block and swap in your key:
{ "mcpServers": { "norc": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.norc.app/mcp", "--header", "Authorization:${NORC_AUTH_HEADER}" ], "env": { "NORC_AUTH_HEADER": "Bearer norc_sk_your_api_key_here" } } }}The header is passed as Authorization:${NORC_AUTH_HEADER} (one argv
element, no space before the value) rather than inlined directly — Claude
Desktop on Windows can split an args entry on spaces, which would corrupt
an inlined "Authorization: Bearer ..." value.
list_jobs,create_job,update_job,delete_joblist_machines,rename_machine,delete_machinelist_runs
Self-hosting
Section titled “Self-hosting”Run your own instance if you’d like — this does not mean self-hosting norc itself, it still talks to the hosted norc API:
pnpm installpnpm buildPORT=3000 node dist/server.jsDocker
Section titled “Docker”docker run -p 3000:3000 norcapp/norc-mcp