Connecting Cursor to Aegis routes every MCP tool call, pushing commits, creating branches, merging pull requests, through Aegis for policy evaluation and logging. The integration uses the MCP SSE transport. You add a single config entry, restart Cursor, and governance begins.
Prerequisites
Before you connect Cursor, make sure you have:
- An Aegis account at app.runaegis.co
- GitHub connected in Settings → GitHub
- At least one room created in Rooms, you need the room ID and access token from that room
Your user ID is in Settings → Profile. You will need it when filling in the config below.
Config file location
Cursor reads MCP configuration from one of two locations:
Setup
Open or create your MCP config file
For user-level scope, open ~/.cursor/mcp.json. For workspace-level scope, create a .cursor/ folder in your project root and open .cursor/mcp.json inside it. If the file does not exist yet, create it.
Paste the config
Copy the snippet below, replace the four placeholder values with your actual credentials, and save the file.Replace each placeholder: Restart Cursor
Quit and reopen Cursor. It reads the MCP config on startup and opens a persistent SSE connection to Aegis.
Verify the connection
After restarting, trigger any tool call in Cursor, for example, ask the agent to read a file or list repository contents. Then open the Aegis dashboard and go to Audit Trail. The action should appear within a few seconds. If it does not appear after a minute, double-check that all four placeholder values in the config are correct and that the room is active.
If you want Aegis active for every project on your machine, use the user-level config at ~/.cursor/mcp.json. If you only want Aegis on specific projects, use the workspace-level config and commit it to the repository.
Keep your access_token private. If it is exposed, rotate it from the room detail page in the Aegis dashboard immediately.
