Skip to main content

LemonCrow — All Agent CLI Integrations

Install LemonCrow into every supported coding agent host in one command:

make install # install into all CLIs found on PATH
make verify # verify code, runtime, and installed hosts

Installers write user/global host config by default. To install project-local artifacts for a specific workspace, pass --workspace DIR to the script:

bash scripts/install_hosts.sh --workspace /path/to/workspace

Supported Hosts​

HostSupport LevelAdvanced installer
Claude CodeFull plugin (skills, commands, hooks, MCP)scripts/install_claude.sh
Codex CLINative MCP registration + AGENTS + plugin bundlescripts/install_codex.sh
CursorMCP server config + rulesscripts/install_cursor.sh
opencodeMCP + workspace agent profilescripts/install_opencode.sh
CopilotMCP + instructions + agent + tasksscripts/install_copilot.sh
Hermes AgentMCP server config + toolsetscripts/install_hermes.sh
AntigravityMCP + generated AGENTS surfacescripts/install_antigravity.sh

Quickstart (install everything at once)​

# 1. Make sure you're in the lemoncrow/ directory
cd lemoncrow

# 2. Install dependencies
uv sync --all-extras

# 3. Install into all available agent CLIs
make install

# 4. Verify
make verify

Hosts whose CLIs are not on PATH are skipped gracefully — this is expected in CI.


Behavior Contract​

All install scripts:

  • Are idempotent — safe to run multiple times
  • Back up existing files before any write (.lemoncrow-backup.TIMESTAMP)
  • Skip gracefully if the host CLI is not on PATH (exit 0)
  • Support --dry-run (print actions, write nothing)
  • Support --print-only (print manual steps for offline/audited environments)
  • Support --strict (exit nonzero if CLI absent — useful for CI gates)
  • Support --workspace PATH to write project-local artifacts instead of user/global config

Host-Specific Install Docs​

Capability-contract detail lives in host-capability-matrix.md.


Integrations Layout​

Detailed documentation and example configs for each host live in:

lemoncrow/integrations/
├── claude/ # Full plugin config
├── codex/ # Codex plugin template + marketplace docs
├── cursor/ # Cursor MCP config + rules
├── opencode/ # opencode.json example
├── copilot/ # .vscode/mcp.json + copilot-instructions
├── copilot-cli/ # Copilot CLI config
└── antigravity/ # Antigravity MCP template + host guidance

Hermes has no directory here — its installer writes ~/.hermes/config.yaml directly.

Host install entrypoints are under scripts/install_<host>.sh.


MCP Transport​

All hosts ultimately invoke the same LemonCrow MCP server, but packaged hosts now carry their own host-specific wrapper surfaces:

lc mcp

That repo wrapper remains the canonical MCP entrypoint for direct MCP-only installs. Codex packages that same runtime behavior behind a plugin-local wrapper, while Antigravity uses workspace or user MCP configuration plus a generated host surface.

Common MCP Surfaces​

All hosts ultimately use the same LemonCrow stdio MCP server.

  • trace is the consistently active observable recording surface.
  • With LEMONCROW_DEV_MODE=1, hosts can actively use context, route, rescue, verify, memory, read, edit, sql, search, compact, bash, and the lemoncrow_code_* helpers.
  • Packaged hosts may add wrapper tasks, skills, or commands on top of that shared MCP surface.

Uninstalling​

Use lc uninstall to remove the main LemonCrow install and managed host integrations. Host-specific uninstall scripts remain available when you only want to remove one host surface.