norc-mcp
OfficialRelated Servers
Alternatives to norc-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to manage Rundeck operations including jobs, executions, projects, nodes, system management, key storage, webhooks, and ACL policies via natural language.5033 npm1Apache 2.0
- AlicenseBqualityBmaintenanceEnables AI agents to schedule and manage cron jobs and webhooks, inspect and replay executions, and configure failure alerts through a local MCP server.18138 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to access connected services and accounts through one MCP/REST interface, run scheduled or event-triggered plain-English jobs, and securely manage notifications, approvals, credentials, and model routing.MIT
- AlicenseNot gradedqualityDmaintenanceEnables ChatGPT to inspect Jobber data and manage controlled automations with scheduling, approval workflows, and audit trails.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables managing and deploying apps to your cloud directly from Cursor through natural language, including environment management, job monitoring, and approval workflows.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables checking deployability, planning deployments, viewing status and logs, and redeploying projects on your own cloud infrastructure directly from AI coding tools.87 npmMIT
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.