Connect Zed to Agent Authority
Connect Zed's agent to SecureAuth Agent Authority with OAuth sign-in so every MCP tool call is checked and audited
When you finish, every MCP tool call Zed's agent makes is checked against your policies and recorded in the audit log. Zed, Zed Industries' code editor, reaches your approved tools through one SecureAuth Agent Authority gateway URL, and each developer signs in as themselves.
Setup
-
Add the MCP server. Run
zed: open settings filefrom the command palette and add the following to~/.config/zed/settings.json:{ "context_servers": { "secureauth": { "url": "https://your-gateway-url/gateway/mcp" } } }Zed reads the scopes to request from the gateway, so you don't list them.
-
Authenticate. Run
agent: open settingsfrom the command palette. Under MCP Servers, click Authenticate on thesecureauthrow, then sign in from the browser window that opens. Zed saves the token in the system keychain, so you sign in once. -
Start using. Zed's agent lists the
secureauthtools and asks before each tool call as usual.The agent is auto-registered on first connect.

Connecting to just one MCP? To stay under an agent's tool limit, point the URL at a single MCP —
/gateway/mcp/{slug}instead of/gateway/mcp. Grab the exact URL from the resource's detail page; see Scope a connection.
Next steps
Zed now reaches your tools through the secureauth server in ~/.config/zed/settings.json.
Next, write the policy that decides which tools it can call.
- Create a policy – control which tools Zed can call.
- Monitor activity – watch its tool calls appear in the dashboard and audit log.
- Audit log – filter and search every tool call Zed makes.
