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 | OAuth discovery (recommended); Authorization: Bearer lsk_your_key_here for clients without OAuth — the key authenticates read tools while mutating calls return connect_required directing the client to connect over OAuth |
Authorization behavior
A browser-confirmed OAuth delegation records one workspace, allowed workflows, target scope, scan profiles and expiry. LyraShield revalidates that grant on every mutating call. A stable idempotency key makes retries return the stored operation instead of repeating it.
Requests outside the recorded grant, expired or revoked connections and lost workspace access never inherit delegated permission; out-of-grant delegated calls are denied. A mutating call authenticated with an API key receives a connect_required response pointing at OAuth connect. Historical exact-input approval records are not an active hosted authorization path. LyraShield-generated fixes and pull requests remain proposals; LyraShield never merges a pull request automatically.
Lovable
In Lovable, open Settings → Integrations → Custom MCP. Add a new remote MCP server with the URL https://app.lyrashieldai.com/api/mcp. Complete the host's OAuth flow when offered; an API key in the Authorization header authenticates read tools only and mutating calls return connect_required until the client connects over OAuth.
Bolt.new (hosted)
Bolt supports custom Connectors for remote MCP servers. Open Settings → Connectors → Manage connectors and add a custom Connector. Enter the remote server URL and select the transport its documentation specifies; Bolt supports HTTP and SSE where the server uses them. LyraShield uses Streamable HTTP at the endpoint above. Complete LyraShield's browser OAuth flow if Bolt offers OAuth for this Connector. A scoped Bearer API key authenticates read tools only; mutating calls return connect_required unless the request carries a valid browser-confirmed OAuth delegation. See Bolt's official Connector guide.
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.
- Complete OAuth if Replit presents it; a scoped API key in the Authorization header authenticates read tools only and mutating calls return connect_required until the client connects over OAuth.
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 complete OAuth if v0 presents it. If it does not, use a read-only scoped API key in the Bearer authorization header.
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?
A browser-confirmed OAuth connection can run the workflows and targets granted at consent without another LyraShield review. LyraShield still checks the user's current workspace role, connection state, scope, target access, budget, expiry and idempotency for every call. A mutating call authenticated with an API key receives connect_required. A delegated call outside the recorded grant is denied.
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.
When will LyraShield still ask for approval?
Hosted OAuth requests a browser-confirmed connection grant. Subsequent matching actions run within that grant and are checked at execution. API-key writes receive connect_required; out-of-grant delegated calls are denied. Local stdio approval is a separate client flow.