Cursor: Enforce JFrog-Governed MCP Usage

JFrog enables Cursor team administrators to enforce MCP usage policies at the team level. Instead of relying on individual developers to select approved MCP servers, you define which servers are available to your team and lock that allowlist in the Cursor team dashboard. Only servers you approve are available to developers; they cannot add or enable any others.

Cursor's MCP Configuration feature (in the Cursor team dashboard) works with JFrog Agent Guard to restrict MCP usage. This is one of three organization-wide MCP enforcement models. For a comparison of Claude Code, Cursor, and VS Code enforcement, see Enforce Organization-Wide MCP Policies.

Prerequisites

Cursor Enterprise Plan with team admin access.
JFrog Platform administrator access.
JFrog AI Catalog entitlement with MCP Registry enabled.
At least one MCP server allowed in your JFrog AI Catalog project.

Enforce MCP Usage in Cursor

To enforce MCP usage in Cursor with team MCP Configuration:

In JFrog, navigate to Administration > AI/ML Settings > AI Catalog.
Set Enable MCP registry to active.
Click Discover MCP servers and allow each MCP server your team approves. Only servers allowed to developers are available.
Return to the AI Catalog Settings page and select the Cursor card (under Organization-wide Configuration).
Copy the generated MCP Configuration entry. The entry is a command string that looks like the following:
```
npx --yes --registry https://releases.jfrog.io/artifactory/api/npm/coding-agents-npm/ @jfrog/agent-guard
```
Where:
- npx --yes — Runs the JFrog Agent Guard package without interactive prompts.
- --registry — The npm source for the @jfrog/agent-guard package. The default is the JFrog public source. For a restricted network, replace this value with your internal npm remote repository: https://<JFROG_URL>/artifactory/api/npm/<REPO_NAME>.
- @jfrog/agent-guard — Restricts Cursor to the JFrog Agent Guard command. Only this proxy is permitted as an MCP server, so any other MCP server a developer adds is blocked.
📘
Note: Multiple JFrog Platform Deployments (JPD)
If you have multiple JFrog Platform deployments, add --server <jpd-name> to the entry, one entry per JPD:
```
npx --yes --registry https://releases.jfrog.io/artifactory/api/npm/coding-agents-npm/ @jfrog/agent-guard --server jfrogml
```
IMPORTANT: Make sure you have enabled the MCP Registry for each JPD.
In the Cursor team admin dashboard, navigate to Settings > Integrations > MCP Configuration.
Click Add Server/Command.
Select Command.
Paste the copied entry into the field.
Click Save.

After you save the entry, Cursor applies it to every developer on your team on the next session start. Developers can use only the MCP servers you allow in AI Catalog; they cannot add or enable any other MCP servers.

Frequently Asked Questions

This section provides answers to frequently asked questions.

FAQs

Q. What if the Cursor team dashboard rejects the MCP Configuration entry?

A: Confirm that you copied the complete entry from the Cursor card and that it is valid. The entry must be a single-line command string starting with npx --yes --registry....

Q. Can developers still use unapproved MCP servers if I add this configuration?

A: No. The MCP Configuration entry restricts Cursor to only the JFrog Agent Guard proxy. Any attempt to add or use an unapproved MCP server is blocked at the team level. The restriction applies on the next developer session start.

Q. Do developers need to take any action after I apply the MCP Configuration?

A: No. The policy takes effect on the next session start. Developers do not need to reload Cursor or perform any manual configuration.

Q. What if no MCP servers are available to developers after I apply this configuration?

A: Confirm that you have allowed at least one MCP server in the JFrog AI Catalog. The MCP Configuration entry restricts where MCPs come from (JFrog Agent Guard), but the specific servers must be allowed in AI Catalog.