Your AI agents can now act through MCP, fully governed.
MCP write operations and schedule success tracking
ZopNight's MCP server now supports write operations: agents connected over MCP can start and stop resources, manage schedules, and drive ZopDay deployments across a surface that grows from 50 to 117 tools, with governance in front of every change. A new Schedule Success Rate widget shows how reliably your schedules are actually firing.
What's in this release
- New ZopNight: MCP write operations. Agents connected over MCP can now act, not just look: start and stop resources, manage schedules, and drive ZopDay deployments across a tool surface that grows from 50 to 117. Every write is governed by a per-org permission tier, a global kill switch, and per-tool authorization. Rolling out opt-in per org; reads are unchanged
- New ZopNight: a Schedule Success Rate widget on the dashboard reconciles every scheduled run against what was supposed to fire, so a schedule that quietly stopped working shows up instead of hiding
- Improved ZopNight: Amazon ECR repositories are now discovered with their AWS resource tags, so tag-based filtering, cost attribution, and rule routing apply to ECR the same way they already do for EC2 and RDS
- Improved ZopNight: hover any audit-log or History timestamp to see the precise date and time in your org's timezone, instead of only a relative label like "5 hr ago"