Skip to content

Updated

Factory Droid

This guide uses LyraShield's integration registry for the cli 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

For the hosted endpoint, run `droid mcp add lyrashield https://app.lyrashieldai.com/api/mcp --type http` or add the same remote server in `/mcp`. Factory Droid uses zero-configuration OAuth Dynamic Client Registration by default and stores tokens in the system keyring; do not add `--no-oauth` or copy a bearer token into project config. Complete browser consent, select one LyraShield workspace, then verify a read-only call. Local stdio with the authenticated LyraShield CLI credential store remains an alternative. The LyraShield Droid plugin marketplace package is still in preparation, and this entry has no authenticated runtime receipt.

Install type: No verified native MCP configuration is available for this client.
For the hosted endpoint, run `droid mcp add lyrashield https://app.lyrashieldai.com/api/mcp --type http` or add the same remote server in `/mcp`. Factory Droid uses zero-configuration OAuth Dynamic Client Registration by default and stores tokens in the system keyring; do not add `--no-oauth` or copy a bearer token into project config. Complete browser consent, select one LyraShield workspace, then verify a read-only call. Local stdio with the authenticated LyraShield CLI credential store remains an alternative. The LyraShield Droid plugin marketplace package is still in preparation, and this entry has no authenticated runtime receipt.
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

  • Droid's plugin system bundles skills, slash commands, hooks, MCP servers and other components. User and project marketplace scopes are separate.
  • Remote HTTP MCP uses OAuth Dynamic Client Registration by default and stores tokens in the system keyring or a fallback file. Keep secrets out of project-level `.factory/mcp.json`; the hosted LyraShield endpoint is read-only unless an authorized browser-confirmed delegation is recorded.
  • Skills can also be installed in `.factory/skills` or `~/.factory/skills`; avoid committing credentials in project settings.
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.
Local access: run npx -y lyrashield@0.2.14 login --oauth to select a workspace for local stdio, or use a scoped workspace API key in an appropriate private environment. Never commit credentials.

Native components and distribution

Documented client capabilities: plugin, skills, commands, hooks. These describe what the client can load; use the installer and distribution details below to see which LyraShield components are available for this surface.

Install shared LyraShield skills

The pinned CLI includes a skills installer for this client. Preview its file changes first, then run the install command. Existing files that are not LyraShield-owned, or have been customized, are preserved.

npx -y lyrashield@0.2.14 skills install factory-droid --project --dry-run
npx -y lyrashield@0.2.14 skills install factory-droid --project

Restart or reload the client and verify its skill list. Local files do not prove discovery, authentication, marketplace listing or runtime acceptance.

Distribution route: Factory Droid plugin marketplace; registry state PREPARATION. 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: Factory Droid official documentation.