Skip to main content
Factory Droid is Tools tier in the universal installer. That path registers HTTP MCP and does not install hooks or skills. The dedicated install-droid-mcp.sh script is a separate path: it registers the same style of HTTP MCP server and also downloads capture hooks into ~/.factory/settings.json. Use the universal installer unless you specifically want those hooks. The dedicated script does not make Factory Droid Full tier. The capability table still lists hooks.method: none and skills.method: none.

​
Agent Instructions

Paste this into Factory Droid:
Add --backend local or -Backend local for local data storage. See Local-First Setup. --targets generic-mcp is the other Tools-tier fallback. See Support Tiers.

​
What the universal installer writes

When droid is on PATH, it runs:
The cloud URL is https://api.memorycrystal.ai/mcp. There is no hooks file and no skill directory from this path. PowerShell performs the same MCP registration and also skips hooks, because the platform row claims none.

​
What the dedicated script adds

install-droid-mcp.sh removes and re-adds the memory-crystal HTTP server with the same bearer header. It then downloads crystal-hooks.mjs and writes UserPromptSubmit, Stop, and SessionStart commands into ~/.factory/settings.json with --host factory-droid. Those hooks capture on that host. They are not installed by --targets factory-droid. Re-running the universal installer does not remove a hooks file the dedicated script already wrote. Uninstalling the factory-droid target removes Memory Crystal hook entries from ~/.factory/settings.json and leaves the rest of that file.

​
Uninstall

Universal target:
Dedicated script:
See Uninstall.

​
Troubleshooting

If installation says the Factory Droid CLI is missing, install droid first and confirm it is on PATH. The universal installer cannot register MCP through a missing CLI. Reopen Factory Droid or use droid mcp list to inspect the server. If requests fail authentication, verify the Bearer header and selected backend URL. If you expect capture, check which installer you used: only the dedicated script writes shared hooks. Universal installation remains Tools tier.

​
Detect clients automatically

Omit --targets to detect installed clients and choose which ones to configure:
The installer offers cloud, local, and external backend choices and backs up config files before writing them. For OpenClaw, native plugin installation is the cloud Bash path; other backend choices use generic MCP guidance.