═══════════════════════════════════════════════════════════
 SassyMCP — Setup Guide
═══════════════════════════════════════════════════════════

 QUICK START:

 1. Run sassymcp-install
    Detects every installed MCP client (Claude Desktop, VS Code Copilot,
    Cursor, Windsurf, Continue, Cline, Zed, Grok Desktop) and patches
    each one's config to register sassymcp.exe. Idempotent. Take a peek
    first with:  sassymcp-install --dry-run
    Remove with: sassymcp-install --uninstall

 2. Run sassymcp.exe --setup
    Starts the server and flags the setup wizard. The first AI session
    will guide you through persona, GitHub token, and optional Linux/
    Android configuration.

 ALTERNATIVE INSTALL ENTRY POINTS:

   - sassymcp.dxt  — double-click in Claude Desktop, auto-patches every
                     other detected client on first launch
   - VS Code marketplace — install "SassyMCP" extension; status bar
                           shows tier + brain health, runs the install CLI
   - Manual JSON editing — see the templates in this folder if you'd
                           rather hand-edit each client's config

 TRANSPORT MODES:

 Local (stdio — Claude Desktop / Cursor / Windsurf / Cline pipe):
   Run: start-local.bat
   Or:  sassymcp.exe
   If you didn't run sassymcp-install, hand-edit each client at:
     Claude Desktop  -> %APPDATA%\Claude\claude_desktop_config.json
     Cursor          -> ~\.cursor\mcp.json
     Windsurf        -> ~\.codeium\windsurf\mcp_config.json
     Continue.dev    -> ~\.continue\config.json (merge under experimental)
     Grok Desktop    -> uses HTTP, see grok_desktop_config.template.json

 HTTP (localhost or LAN):
   Run: start-lan.bat
   Interactive: choose bind address, port, and auth token.
   For LAN access, an auth token is required.

 Cloudflare Tunnel (remote access):
   Requires: cloudflared installed and a named tunnel + DNS route.
   Run: start-tunnel.bat <tunnel-name>
        (or set SASSYMCP_TUNNEL_NAME and run with no args)
   Bridge auto-launches on 127.0.0.1:21001; cloudflared runs in the
   foreground and exits on Ctrl-C.
   Before exposing a tunnel hostname, set SASSYMCP_ALLOWED_HOSTS to
   include it (DNS-rebinding protection rejects unknown Host headers
   with 421).
   Full walkthrough: docs/TUNNEL.md in the source repo.

 AUTH TOKENS:

 For HTTP/tunnel modes, set SASSYMCP_AUTH_TOKEN env var or
 use the sassy_setup_generate_token tool to create scoped
 tokens saved to ~/.sassymcp/tokens.json.

 GUIDED SETUP:

 After first launch, the AI will guide you through:
   sassy_setup_wizard      — Create your user profile
   sassy_setup_github      — Connect GitHub (opens browser for token)
   sassy_setup_ssh         — Connect remote Linux (host/user/pass)
   sassy_setup_check_tools — Scan for optional tools (nmap, adb, etc.)

 ENVIRONMENT VARIABLES:

 SASSYMCP_LOAD_ALL=1          Load all tool modules
 SASSYMCP_GROUPS=core,github  Load specific groups only
 SASSYMCP_AUTH_TOKEN=xxx      Bearer token for HTTP auth
 SASSYMCP_DEV=1               Enable live reload (dev mode)
 GITHUB_TOKEN=xxx             GitHub API access
 SSH_HOST=xxx                 Remote Linux hostname/IP
 SSH_USER=xxx                 Remote Linux username
 SSH_PASS=xxx                 Remote Linux password

 FILES:

 ~/.sassymcp/persona.md       Your user profile
 ~/.sassymcp/config.json      Server configuration
 ~/.sassymcp/tokens.json      Auth tokens
 ~/.sassymcp/tool_usage.json  Tool analytics data
 ~/.sassymcp/audit.log        Audit trail
═══════════════════════════════════════════════════════════
