Skip to main content
Aegis connects to your AI coding agent using the Model Context Protocol (MCP) over Server-Sent Events (SSE). When your agent calls a tool, pushing code, opening a pull request, creating a branch, that request flows through Aegis first. Aegis evaluates it against your policies, logs it, and either allows it, routes it for approval, or blocks it. You do not need to modify your agent or your repositories.

​
Supported tools

Claude Code

User-level or project-level config via ~/.claude/mcp.json.

Cursor

User-level or workspace-level config via ~/.cursor/mcp.json.

VS Code Copilot

Workspace-level config via .vscode/mcp.json.
Coming soon: Windsurf and Codex support is in progress. These tools will appear on the Integrations page in the Aegis dashboard when they are ready.

​
How the connection works

Every integration uses the same SSE endpoint with query parameters that identify you, the room, and your role:
When your agent starts, it opens a persistent connection to this URL. From that point on, every MCP tool call the agent makes passes through Aegis.

​
Connection flow

1

Create a room

In the Aegis dashboard, go to Rooms and create a room for the repository you want to govern. A room ties together a repository, its policies, and the agents allowed to act on it. You must create a room before you can connect an agent.
2

Copy your credentials

After creating the room, copy the room ID and access token from the room detail page. You will also need your user ID, which you can find in Settings → Profile.
3

Paste the config and restart

Open the config file for your tool, paste the MCP snippet with your credentials substituted in, and restart the tool. Your agent will connect on next startup and Aegis will begin logging its actions immediately.

​
Where to find your credentials

​
Choosing a role

The role parameter controls what actions Aegis permits for this agent connection. Choose the role that matches the trust level you want to grant.
Start with DEVELOPER and promote to ADMIN or OWNER only if the agent needs capabilities that a developer role does not cover.
Keep your access token private. If it is ever exposed, rotate it immediately from the room detail page in the Aegis dashboard.