Updated
Claude Web (Remote Connector)
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 Claude web, open Customize → Connectors → + → Add custom connector, enter the LyraShield hosted MCP URL, then connect and complete OAuth. For Team or Enterprise, an Owner must first add the custom connector in Organization settings → Connectors. Enable the connector in a conversation through the + menu when needed.
In Claude web, open Customize → Connectors → + → Add custom connector, enter the LyraShield hosted MCP URL, then connect and complete OAuth. For Team or Enterprise, an Owner must first add the custom connector in Organization settings → Connectors. Enable the connector in a conversation through the + menu when needed.Important gotchas
- Claude web remote connectors use Anthropic's cloud MCP proxy and require a public-reachable endpoint. Local MCP servers and Desktop Extensions are not available on web.
- Team and Enterprise workspaces require an Owner to register the custom connector before individual users connect and authenticate.
Native components and distribution
No native plugin, skill, command, rule or hook capability is recorded for this surface.
Distribution route: Claude custom remote connector; 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: Claude Web (Remote Connector) official documentation.