gohighlevel

# GoHighLevel Follow [`../docs/mcp-connection.md`](../docs/mcp-connection.md). Resolve `~~gohighlevel` to the live connection. Use its current instructions and capability descriptions to choose tools, and verify the requested location from live data. Do not infer access from an ad platform or another connected CRM. This skill is revenue-ops on the connected HighLevel account: contacts, conversations, opportunities, and calendar. Make writes only when the user explicitly requested them. Older clients may still reach a dedicated `/api/mcp/gohighlevel` route; do not add that as a second plugin MCP server. Authentication uses a NotFair PAT on the connect page; one PAT per HighLevel connection. If the connector is missing, unauthorized, or read-only for a requested write, direct the user to reconnect with the needed scopes and stop. ## Establish the live location 1. Confirm connected locations with a harmless read. Agency (Company) connections must pass an explicit `locationId` for per-location tools; Location connections may omit it. 2. Prefer specific typed tools over the generic request escape hatch. That request surface is read-only GET. 3. Record the account currency, location, pipeline or calendar context, and whether the session can mutate. Core reads include contacts, conversations, opportunities, calendar events, and locations, plus metadata for users, pipelines, calendars, custom fields, tags, and tasks. Intake reads include forms, surveys, invoices, transactions, a...