Skip to main content
GHL MCP Guide
LOC

Location CRUD

Location & Config · Advanced · Updated March 2026

Create, read, update, delete, and search sub-account locations. Each location represents a business with its own contacts, pipelines, and configurations.

Locations are sub-accounts in GHL. Each location represents a separate business with its own contacts, pipelines, calendars, conversations, and configurations. For agencies, location management is the backbone of multi-client operations. Through MCP, you can programmatically provision new client accounts, configure defaults, and manage sub-account settings at scale.

What This MCP Tool Does

Full CRUD on sub-account locations. Create new locations with business details and configurations, retrieve location settings, update configurations, search across locations, and delete sub-accounts. This is the agency-level tool for managing your client portfolio.

Endpoint Reference

Create a location: POST /locations Get a location: GET /locations/{locationId} Update a location: PUT /locations/{locationId} Delete a location: DELETE /locations/{locationId} Search locations: GET /locations/search

Authentication

Requires a Private Integration Token (PIT) with the locations scope enabled. Agency-level PIT required for creating and managing multiple locations.

Key Parameters

  • name — business name
  • address, city, state, postalCode, country — physical address
  • phone — business phone number
  • email — business email
  • website — business website URL
  • timezone — location timezone (use Timezone Handler for valid values)
  • settings — location configuration object

Important Notes

Creating a location provisions a complete sub-account with its own isolated data. Contacts, pipelines, calendars, and configurations in one location are completely separate from another.

For agency onboarding automation, location creation is step one. Follow it with Location Custom Fields to define data fields, Location Custom Values to set variables, Location Tags for organization, and then Calendar CRUD to set up booking systems.

Deleting a location permanently removes all data within it. There is no recovery. Treat this as the nuclear option.

Location IDs are the key to everything. Almost every other MCP tool operates within a specific location context identified by the location ID.

Common Questions

Can I create sub-accounts programmatically during client onboarding? Yes. This is one of the most powerful agency automation use cases. Receive a signed agreement, create the location via MCP, configure defaults, and have the sub-account ready before the onboarding call.

Can I copy settings from one location to another? Not directly. Read settings from the source location and apply them to the target. For bulk configuration, GHL’s Snapshots feature (UI-based) is more efficient.

How do I search across all my sub-accounts? Use the search endpoint with optional filters for name, address, or other criteria.

Back to GHL MCP Guide