Runlayer Plugin
Unified endpoint
Add one remote MCP endpoint. Users discover and authorize the approved tools available to them without accumulating separate client configurations.
Connect Lovable to approved remote MCP services through Runlayer.
Connect
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.
Runlayer Plugin
Add one remote MCP endpoint. Users discover and authorize the approved tools available to them without accumulating separate client configurations.
Direct connection
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
Observe
Runlayer uses every channel Lovable exposes. Each one is labeled, so you can tell real-time hooks from after-the-fact imports.
Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.
Read the guideEnforce
Each row reflects Runlayer’s enforcement code for Lovable: what it can stop before a call runs, block afterward, or redact in place.
| Control | Support | What that means |
|---|---|---|
| Pre-tool deny | At the gateway | Runlayer has no hook in Lovable that can stop a tool call; Runlayer policies stop calls to Runlayer connectors at the gateway. |
| Post-tool output block | At the gateway | Runlayer has no hook in Lovable that can block tool output; ToolGuard blocks unsafe output from Runlayer connectors at the gateway. |
| Output rewrite | At the gateway | Runlayer has no hook in Lovable that can rewrite tool output; ToolGuard masks sensitive output from Runlayer connectors at the gateway. |
MCP servers
Setup steps, tools, and controls for each MCP server in Lovable.