Skip to main content
Glama

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

Related MCP server: Deployment.io MCP Server

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):

    {
      "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:

    "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:

pnpm install
pnpm build
PORT=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

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

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

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

License

MIT

Available Tools

9 tools
create_jobCInspect

Create a new cron job on a machine.

Inputs: name (required), command (required), schedule (required), machine_id (required), +1 more.

delete_jobDInspect

Delete a job.

Inputs: id (required).

delete_machineCInspect

Unpair (delete) a machine.

Inputs: id (required).

list_jobsBInspect

List the user's cron jobs, optionally filtered by machine.

Inputs: machine_id.

list_machinesBInspect

List the user's paired machines.

Inputs: no named parameters.

list_runsAInspect

List job run history, optionally filtered by job, machine, or status. Paginated via cursor.

Inputs: limit, cursor, job_id, status, +1 more.

rename_machineCInspect

Rename a machine.

Inputs: id (required), name (required).

sync_jobsAInspect

Make the account's jobs match a declared set (declarative, like norc gitops). Jobs not listed are DELETED. Defaults to a dry run that only returns the diff; set apply=true to execute it. Always show the user the dry-run diff, especially the deletes, and get their confirmation before applying. Requires the gitops sync feature on the account.

Inputs: jobs (required), apply.

update_jobCInspect

Update an existing job (name, schedule, command, or enabled state).

Inputs: id (required), name, command, enabled, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions: jobs, machines, and run history are separated cleanly. The only meaningful overlap is sync_jobs, which can also create/update/delete jobs declaratively, but its bulk/destructive semantics and dry-run behavior are clearly described.

    Naming Consistency5/5

    All names follow a consistent snake_case verb_noun pattern: list_jobs, create_job, update_job, delete_job, list_machines, rename_machine, delete_machine, list_runs, sync_jobs. There are no mixed casing or inconsistent verb styles.

    Tool Count5/5

    Nine tools is well-scoped for a cron-job and machine management server. Each tool covers a meaningful operation, and the set avoids both excessive granularity and missing core actions.

    Completeness4/5

    The job lifecycle is well covered with list/create/update/delete plus declarative sync, and machines have list/rename/delete. Minor gaps exist, such as no explicit machine pairing/create operation and no job-run detail or cancellation tool, but core workflows are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers