Updated
Remote MCP endpoint
Cloud-hosted editors — Lovable, Bolt.new (hosted), Replit, and v0 — cannot run local processes. Use the LyraShield remote Streamable-HTTP MCP endpoint to connect these editors to LyraShield tools.
Endpoint details
| Property | Value |
|---|---|
| URL | https://app.lyrashieldai.com/api/mcp |
| Transport | Streamable HTTP |
| Authentication | Authorization: Bearer lsk_your_key_here |
Lovable
In Lovable, open Settings → Integrations → Custom MCP. Add a new remote MCP server with the URL https://app.lyrashieldai.com/api/mcp and set the Authorization header to Bearer lsk_your_key_here.
Bolt.new (hosted)
In the Bolt.new hosted environment, navigate to Settings → MCP Servers and add a custom remote server. Use the endpoint URL and Bearer token auth. Note: Bolt.new Desktop supports local stdio — see the other editor guides for that setup.
Replit
Replit supports MCP connections via the integrations panel.
- Open your Repl and go to Tools → MCP Servers (or the equivalent integrations UI in your Replit version).
- Add a new server with the remote endpoint URL.
- Set the Authorization header with your Bearer API key.
For automated checks on every push, the GitHub Action is the recommended complement. Sync your Repl to a GitHub repository and add the LyraShield Action to your workflow.
v0 (Vercel)
In v0, open Settings → Integrations → MCP and add a custom remote MCP server. Supply the endpoint URL and set the Bearer authorization header with your API key.
GitHub Action as a complement
For any cloud editor that syncs to a GitHub repository, the LyraShield GitHub Action provides automated security checks on every pull request without relying on the editor's MCP connection. This is the recommended path for production assurance.
Frequently asked questions
Can cloud editors run mutating LyraShield tools?
Remote mutating tools (scan triggers, finding submissions) are refused by default for safety. They require an explicit trusted-automation opt-in. Read-only inspection and reporting tools work everywhere via the remote endpoint.
What is the difference between remote MCP and the GitHub Action?
Remote MCP connects your cloud editor's AI assistant to LyraShield tools for interactive use. The GitHub Action runs automated checks in CI on every pull request without any AI editor involved. For cloud-hosted workflows, using both together is recommended.