Runlayer Plugin
Unified endpoint
Add one remote MCP endpoint. Users discover and authorize the approved tools available to them without accumulating separate client configurations.
Runlayer for Zed
Automatically sync approved local and remote MCP configuration into Zed.
01
Connect
Give everyone in Zed the golden path to approved tools
Add one Runlayer Plugin endpoint so people find every tool they’re approved for, or connect a single server when you want a narrower set.
Direct connection
Per-connector endpoint
Give the client a dedicated Runlayer URL for one connector. Identity, policy, scanning, and audit still stay attached to every request.
Connection support
Remote MCP and local MCP
02
Observe
See how Zed is being used
Runlayer uses every channel Zed exposes. Each one is labeled, so you can tell real-time hooks from after-the-fact imports.
Gateway activity
Runlayer records identity, policy, scanner, and audit activity for MCP requests routed through the gateway.
Read the guide03
Deploy at scale
Roll out Zed controls with the tools IT already uses
Admins can deploy the Runlayer CLI and endpoint package through MDM, then keep approved MCP configuration in sync automatically.
macOSmacOSWindows and macOS
SimpleMDM
Open deployment guide →
Jamf Pro
Open deployment guide →
Microsoft Intune
Open deployment guide →
One signed package, settings managed centrally
Runlayer’s endpoint package installs on managed macOS and Windows devices. It discovers shadow AI, keeps hooks in place, captures sessions, and applies runtime controls. Approved MCP configuration re-syncs on a schedule for supported clients.
MCP servers
Connect Zed to the tools your teams use
Setup steps, tools, and controls for each MCP server in Zed.
