Skip to content

Updated

Claude Desktop (Remote Connector)

This guide uses LyraShield's integration registry for the desktop 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 Desktop, 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. This uses Anthropic's remote connector service, not a local Desktop Extension.

Install type: No verified native MCP configuration is available for this client.
In Claude Desktop, 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. This uses Anthropic's remote connector service, not a local Desktop Extension.
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

  • Claude Desktop remote connectors are brokered from Anthropic's cloud and require a public-reachable MCP server. Local Desktop Extensions are a separate local-only mechanism.
  • Team and Enterprise workspaces require an Owner to register the custom connector before individual users connect and authenticate.
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: 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 Desktop (Remote Connector) official documentation.