HomeFeaturesPricingDocumentationContactDOWNLOAD

Quickstart

Add your first project, run a scan, read your SiteCMD Score, connect your editor, and hand it the first fix.

This is the short version. If you want detail on installing or on what a scan actually does, see Installation and Your first scan.

1. Open the app

When you open SiteCMD for the first time, it boots straight to the project setup screen. There are no projects yet, no scan history, nothing to look at. That’s expected.

2. Add a project

A project is one website. You give it a name and one or more URLs, each tagged with an environment: production, staging, development, or local. The form starts with a single production row.

If you have the source folder on your machine, link it now. SiteCMD reads your package.json, composer.json, requirements.txt, and similar files to detect your stack and pre-fill a sensible local URL. Linking the folder is optional, but it enables Code Scan and tailors fix guides to your framework.

3. Run a scan

Click Run Scan in the top bar. SiteCMD checks the live site, then audits the linked source folder if you’ve connected one. The scan progress overlay shows you the current stage and lets you cancel at any time.

4. Read your SiteCMD Score

When the scan finishes, the dashboard shows your SiteCMD Score out of 100. The score starts at 100 and goes down for each active issue we find, weighted by severity. Critical issues cost the most, lows barely register, and fixing, dismissing, or marking an issue not applicable gives the points back.

There are no blanket severity cliffs: Critical findings cost the most, but a Critical label alone never locks the score to a fixed number. The one exception is the narrow security cap: an active finding must be Critical, belong to the audited cap-candidate list, and carry explicit High or Confirmed confidence to cap the score at 49. Static patterns emitted as Needs review cannot trigger it. See The SiteCMD Score for the current eligibility rules.

The dashboard shows the top issues driving the score, grouped by category. The fastest way to bring the score up is to start at the top of that list.

SiteCMD dashboard after a first scan: the SiteCMD Score, the top issues driving it, and the category breakdown.

5. Connect your editor

Open Integrations in the SiteCMD sidebar and click Connect next to Claude Code, Cursor, or Codex. SiteCMD finds your Node, copies its MCP server into a persistent folder, writes the editor’s config, and runs a health check; the card reads Connected only when that check passes. Every other MCP editor (Windsurf, VS Code, Copilot, Cline, Zed, JetBrains) takes one pasted config block; see AI editor setup.

6. Hand it the first fix

Restart the editor so it loads the server, open your project, and paste this as your first prompt, with your own URL:

Use the SiteCMD MCP tools. Call get_issues for https://example.com, pick the highest-severity open issue, explain it to me in two sentences, fix it in this repository, ask me to click Run Scan in SiteCMD, then call compare_scans

The agent reads the real finding instead of guessing, makes the edit, waits for your scan, and reports what the comparison shows: fixed, new, and still open. For the verified version of this loop, where SiteCMD re-checks the agent’s work itself, start from an issue with Fix with your agent and read Fixing with AI editors.

What’s next

  • Installation if you want the install details and system requirements.
  • Your first scan for what the scan actually checks, how long it takes, and where the results live.
  • The SiteCMD Score for how the score math works in detail.
  • AI editor setup for the per-editor config blocks, what the server exposes, and the fix loop in full.