norc-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NORC_API_KEY | Yes | Your norc API key, generated from vault → Settings → API Keys. Required for authenticated access; without it the server starts in HTTP mode. | |
| NORC_VAULT_URL | No | Optional custom norc vault URL. Defaults to the hosted norc vault. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_jobsB | List the user's cron jobs, optionally filtered by machine. |
| create_jobC | Create a new cron job on a machine. |
| update_jobC | Update an existing job (name, schedule, command, or enabled state). |
| delete_jobD | Delete a job. |
| list_machinesB | List the user's paired machines. |
| rename_machineC | Rename a machine. |
| delete_machineC | Unpair (delete) a machine. |
| list_runsA | List job run history, optionally filtered by job, machine, or status. Paginated via cursor. |
| sync_jobsA | Make the account's jobs match a declared set (declarative, like |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
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.
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.
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.
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.