SayA developer on the Enterprise team files a P1: 'Cursor is broken. A model my teammate uses is greyed out for me, and an MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. server won't connect. Please fix the bug.' Before I look at code behavior, I check whether this is a configured control.
DoConfirm the reporter's role first. They are a Member, not an admin, so they can't see the team's access settings.
DoCheck identity, policy, network and plan state before code. Open the Teams dashboard: the model is turned off by the team's model access control, and the MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. server is not on the approved list.
SeeBoth symptoms map to admin-configured controls, not to Cursor misbehaving.
DoRead the admin's model and MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. access settings, and pull the request ID from the failed model call, as the evidence.
SeeThe evidence is a policy setting plus a request ID, not a crash. The restriction is deliberate.
DoRule network in or out too. Check there is diagnostic evidence that the MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. endpoint is reachable, so a proxy block isn't hiding under the 'won't connect' report.
SeeReachable endpoint and valid auth, so this is the approval list, not the network.
SayThis is not a defect. The greyed-out model and blocked MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. are configured access controls. I explain them and route the reporter to their admin to adjust the list.
SeeThe evidence that separated control from bug was the dashboard's own access settings plus a request ID. Only behavior that survived those checks would go back as a true defect with a clean repro.