Skip to content
SmartMoving MCP + CLI

Safety model

This project can interact with live CRM data. It is provided as is and used at your own risk. The maintainers are not responsible for data loss, sync errors, incorrect results, downtime, duplicate or missing records, account issues, business interruption, or other problems arising from use.

Default: read-only discovery

Section titled “Default: read-only discovery”
Terminal window
export SMARTMOVING_API_KEY="replace-with-your-key"
export SMARTMOVING_ALLOW_WRITES="false"
unset SMARTMOVING_ALLOW_DESTRUCTIVE

Allowed:

  • smartmoving doctor --json
  • smartmoving schema --json
  • smartmoving docs generate
  • read commands such as reference branches, leads list, and customers get
  • MCP read tools such as list_leads, get_customer, and get_opportunity

Blocked:

  • create/update/patch commands and MCP tools;
  • delete-style commands and MCP tools.

Dry-run write preparation

Section titled “Dry-run write preparation”

Dry-runs validate input and print request metadata without calling SmartMoving:

Terminal window
smartmoving leads create --input lead.json --dry-run --json
smartmoving jobs notes append <jobId> --opportunity-id <opportunityId> --text "Synthetic note" --dry-run --json

Use fake examples in tests and PRs.

Guarded writes

Section titled “Guarded writes”

Only enable writes after a human reviews the workflow and payload:

Terminal window
export SMARTMOVING_ALLOW_WRITES="true"
export SMARTMOVING_ALLOW_DESTRUCTIVE="false"

Rules:

  • run --dry-run --json first;
  • review UUIDs, dates, customer-facing text, and request shape;
  • use --yes only after approval;
  • prefer append-style operations for notes;
  • read current state before replacing anything.

Destructive operations

Section titled “Destructive operations”

Delete-style operations require writes, destructive permission, and --yes:

Terminal window
export SMARTMOVING_ALLOW_WRITES="true"
export SMARTMOVING_ALLOW_DESTRUCTIVE="true"
smartmoving followups delete <followupId> --opportunity-id <opportunityId> --yes --json

Before destructive calls, confirm target UUIDs from a fresh read, confirm account context, record why the operation is needed, and prefer completion/status changes when history should be preserved.

Approval checklist

Section titled “Approval checklist”
  • smartmoving doctor --json succeeded.
  • Command came from smartmoving schema --json or generated docs.
  • Agent ran a dry-run and showed method/path/body.
  • Tests use fake data only.
  • Real data appears only during approved live work.
  • Human approved --yes for the specific operation.
  • Destructive operations have explicit, separate approval.