Skip to main content
Use the universal installer first. It can configure this target for hosted cloud or local Docker Convex and creates config backups before writing.

Agent Instructions

Copy and paste this directly into Factory Droid:
For native Windows PowerShell, use:
For local data storage, add --backend local in Bash or -Backend local in PowerShell. See Local-First Setup. Factory Droid can use Memory Crystal as its memory helper, just like other MCP-compatible coding assistants.

What this means in practice

The repo names this integration Factory Droid. That should be the canonical public docs name, even if people casually say “Factory” or “Factory Drone.”

How it actually works

Important repo surfaces:
  • apps/web/public/install-droid-mcp.sh
  • packages/mcp-server/README.md
  • .env.example
The installer handles:
  • CLI detection
  • auth flow
  • MCP registration
  • local Memory Crystal support file setup

Universal installer path

The recommended first install path is the universal installer:
Use it when you want Memory Crystal to detect Factory Droid, ask before changing config, and offer cloud or local-first backend mode. The dedicated commands below remain useful for single-client installs and compatibility.

Commands / examples

Installer:

Uninstall

For purge behavior and safety notes, see the uninstall guide.

Common mistakes

  • drifting from the actual script/CLI naming in the repo
  • assuming this page should describe a different product name than the repo uses
  • treating Factory Droid like a generic MCP client without documenting its dedicated installer

Source of truth

Primary files behind this page:
  • apps/web/public/install-droid-mcp.sh
  • packages/mcp-server/README.md
  • .env.example