Skip to content

Updated

v0

This guide uses LyraShield's integration registry for the web surface. It shows the current setup strategy and client source; actual client loading and authenticated runtime acceptance are tracked separately below.

Connection setup

The registry's setup path for this client is Guided manual setup over remote HTTP.

Client activation instructions

In the v0 prompt form, open + → MCP, choose a custom MCP server, enter the LyraShield endpoint and select OAuth. Review tool approval and permission settings before using tools. This direct MCP setup does not imply a Vercel Marketplace listing.

Install type: No verified native MCP configuration is available for this client.
In the v0 prompt form, open + → MCP, choose a custom MCP server, enter the LyraShield endpoint and select OAuth. Review tool approval and permission settings before using tools. This direct MCP setup does not imply a Vercel Marketplace listing.
Manual setup: the pinned CLI package (lyrashield@0.2.14) has no matching installer contract for this integration. Use the configuration or client instructions above and verify the client loads it.

Important gotchas

  • v0 supports custom remote MCP servers with OAuth, bearer tokens or custom headers. No local project config file is documented.
  • Vercel Marketplace integrations are a separate route from v0's bring-your-own MCP server configuration; listing eligibility and approval are not established here.
Hosted access: use OAuth when the client supports it. Hosted mutations require a browser-confirmed delegation and are checked against its workspace, scope and expiry. An API key alone does not authorize hosted mutations. See the Remote MCP guide.

Native components and distribution

No native plugin, skill, command, rule or hook capability is recorded for this surface.

Distribution route: Bring-your-own remote MCP server; registry state DIRECT. Client distribution documentation.

Support evidence

Registry tier: COMPATIBLE. Evidence: DOCUMENTATION, checked 2026-10-01. Client version: not recorded; tested platforms: not recorded. No client runtime receipt is recorded.Marketplace state and runtime compatibility are separate claims.

Source: v0 official documentation.