Skip to main content
Version: 11.5.0

Cursor

HYPR AgentPass™ manages Cursor through Endpoint Guard. Cursor receives your published MCP connectors and reports agent activity through its own event hooks. Cursor does not route model inference through the gateway.

AgentPass applies three capabilities to Cursor: MCP connectors, activity reporting through hooks, and a block on direct traffic to configured provider destinations. Inference routing is not supported by Cursor.

Enable Cursor​

  1. Enroll the workstation with Endpoint Guard for macOS or Windows.

  2. In the console, open Desktops, click the Desktop configuration tab, and choose Configuration.

  3. If Configure agents from AgentPass is off, turn it on, and click Turn on to confirm.

  4. Turn on Configure Cursor.

  5. Keep Provide MCP servers selected.

    To keep a connector from Cursor, turn off Publish to endpoint catalog on that connector.

  6. Click Save.

  7. After Endpoint Guard updates the MCP configuration, restart Cursor.

Where Endpoint Guard Writes​

Endpoint Guard merges its entries into Cursor's own files. Connectors and hooks the developer added stay in place.

  • MCP connectors go into ~/.cursor/mcp.json.

  • Observation hooks go into Cursor's system-level hooks.json. On macOS, that is /Library/Application Support/Cursor/hooks.json. On Windows, it is C:\ProgramData\Cursor\hooks.json.

  • Fallback: where the system file cannot be written, Endpoint Guard uses ~/.cursor/hooks.json.

See Endpoint Configuration Locations.

What AgentPass Applies​

AgentPass applies these capabilities to Cursor.

CapabilityCursor behavior
Provide MCP serversAdds published MCP Server and REST API connectors
Report activity through the tool's hooksReports prompts, responses, tool calls, shell commands and file-edit events through Cursor hooks
Block direct trafficBlocks configured provider destinations for the signed Cursor application
Inference routingNot supported by Cursor