Cursor now lets admins configure Team MCP servers once and distribute them across cloud agents, IDE, and CLI — with org-group access control. Here's what centralized MCP governance means for operators managing coding agent tool routing at scale.
Cursor's native iOS app introduces mobile Remote Control for cloud agents, creating a new approval surface that AI operators and routing teams need to govern deliberately.
Cursor 3.9 unifies plugins, skills, MCPs, subagents, rules, and hooks into a single Customize page with user, team, and workspace scoping — and team marketplaces now import from GitLab, Bitbucket, and Azure DevOps.
Cursor model routing now covers Automations from /automate, Slack emoji triggers, GitHub review events, and cloud-agent computer use.
Cursor's official Bugbot docs and June changelog now point to Composer 2.5, pre-push /review, and Cloud Agents formerly called Background Agents. For routing operators, the key line is still model block lists: AI code review now needs explicit governance.
A practical permissions.json autorun schema for Cursor SDK 0.1.6: how autoRun.allow_instructions, autoRun.block_instructions, local.autoReview, local.customTools, JsonlLocalAgentStore, requestId, and nested subagents fit together.
