GoHighLevel MCP Server
GoHighLevel MCP Server
Un servidor de Model Context Protocol que otorga a un agente LLM control operativo de un CRM de GoHighLevel — 114 herramientas en 24 módulos, que abarcan contactos, pipelines, calendarios, mensajería, facturación y pagos a través de la API v2 de GoHighLevel.
El problema
GoHighLevel es el sistema de registro para una agencia pequeña: cada cliente, cada reserva, cada factura. El trabajo que de verdad consume el día no es una acción aislada de CRM, sino la costura entre las acciones: se confirma una sesión, así que alguien tiene que crear la oportunidad, pasarla a la etapa correcta del pipeline, reservar el hueco de calendario con el contacto adecuado, redactar la factura y dejar una nota. Cada paso son treinta segundos de clics, y la secuencia se repite varias veces por semana.
Esa secuencia es exactamente lo que puede hacer un agente, si puede llegar hasta el CRM. Este servidor es ese acceso: expone GoHighLevel como herramientas tipadas y anotadas para que un agente realice toda la cadena a partir de una sola frase de instrucción, mientras que los pasos destructivos y los que tienen visibilidad externa siguen quedando a la vista para su aprobación.
Related MCP server: MCP Suite CRM
Arquitectura
Los módulos de herramientas se registran contra un único McpServer sobre stdio. Todo lo enruta a una única función ghlRequest(), que gestiona la autenticación, la cabecera obligatoria Version, el ensamblado de la cadena de consulta y el modelado de errores. Los módulos se pueden activar o desactivar en el arranque mediante GHL_DISABLED_MODULES — algo más relevante de lo que parece, porque 114 definiciones de herramientas suponen una porción significativa de la ventana de contexto de un agente antes de que este haya leído una sola palabra de la solicitud del usuario. Un despliegue que solo hace reservas puede registrar seis módulos y omitir el resto.
MCP host (Claude Desktop / Claude Code)
| stdio (JSON-RPC)
+-------v--------------------------------------------+
| index.ts MODULES registry, GHL_DISABLED_MODULES |
+-------+--------------------------------------------+
|
+-------v-----+ +---------------+ +-----------+ ...... 24 modules
| contacts | | opportunities | | invoices |
+-------+-----+ +-------+-------+ +-----+-----+
| | |
| | +-----v--------------+
| | | billing-helpers.ts |
| | | businessDetails |
| | | contactDetails |
| | | sender resolution |
| | +-----+--------------+
+-------+-------+---------------+
|
+---------v----------------------------+
| client.ts ghlRequest() |
| Bearer token + Version header |
| status-specific error hints |
+---------+----------------------------+
|
services.leadconnectorhq.comCada herramienta de escritura lleva anotaciones MCP — 114 están marcadas como destructiveHint, y las herramientas ghl_send_message y ghl_send_invoice se marcan como hacia afuera porque contactan con clientes reales. El host muestra esas marcas antes de aprobar una llamada, que es la diferencia entre un agente que redacta una factura y un agente que se la envía a un cliente por accidente.
La parte realmente complicada
Crear una factura. El endpoint acepta bloques businessDetails y contactDetails, y la documentación no detalla bien ninguno de los dos: si pasas un contactId y un par de líneas de detalle, como sugieren los documentos, obtienes un error de validación que no nombra ningún campo. Ambos bloques son obligatorios al completo, y businessDetails.phoneNo y contactDetails.phoneNo son obligatorios — un contacto con email y sin teléfono no se puede facturar en absoluto.
Y lo que es peor, los valores tienen que coincidir con lo que produce la interfaz; si no, las facturas creadas por API tienen un aspecto diferente de las facturas creadas a mano: un logotipo distinto, condiciones de pago que faltan, numeración incorrecta. Esos valores por defecto no están en el perfil de ubicación del que cabría esperar; viven detrás de GET /invoices/settings, que es la misma fuente de la que la interfaz precarga la información.
src/tools/billing-helpers.ts resuelve ambos bloques para que las herramientas solo necesiten un contactId. Los detalles de empresa caen a través de cuatro niveles — argumento por llamada, GHL_BUSINESS_* (variables de entorno), ajustes de factura guardados, perfil de ubicación — y cada nivel rellena solo lo que el nivel superior dejó vacío. Los datos de contacto se obtienen y se estructuran, y el campo name cae sucesivamente al nombre completo, nombre + apellidos, nombre de empresa, email y teléfono; porque GoHighLevel rechaza un nombre vacío, y los registros reales del CRM a menudo carecen de uno. Ambas rutas lanzan un mensaje que indica el campo que falta y cómo suministrarlo, en lugar de mostrar el opaco error 422 de GHL. Cada búsqueda se memoiza por ubicación, de modo que un lote de diez facturas cuesta una única llamada de configuración, no diez.
Lo que haría de otra manera
No hay tests. 4.000 líneas y ninguno. La cadena de fallback de
billing-helperses lógica pura sobre datos de prueba — lo más fácil de testear del repositorio y lo más costoso de fastidiar, porque el error suele manifestarse como factura malformada enviada a un cliente.No hay reintentos en el 429.
ghlRequestle dice al que llama «limitado; reintenta tras un breve retardo» y luego no reintenta. La espera con backoff debería vivir en el cliente, no en el criterio del agente.Los conoceslas son mapas mutables a nivel de módulo sin invalidación. Correcto para un servidor stdio que el host reinicia con libertad; incorrecto en cuanto esto corra como un proceso longevo, donde una edición de perfil comercial nunca sería recogida.
Las respuestas son siempre
Record<string, unknown>en todo el código. GoHighLevel publica una especificación OpenAPI; generar tipos a partir de ella convertiría una clase de sorpresas de ejecutorunos Counter en errores de compilación.114 herramientas en un servidor son demasiadas. Los toggles de módulos son una solución de emergencia, no una solución real. La forma mejor es un conjunto pequeño de herramientas más un mecanismo de descubrimiento, para que el agente pague solo por lo que usa.
Configuración
Requiere Node 20+ y una cuenta de GoHighLevel.
1. Crear un token de integración privada
**Configuración → Integraciones privadas → Crear integración nueva. ** Activa los scopes que se correspondan con las herramientas que vayas a usar; como mínimo:
contacts.readonly, contacts.write, opportunities.readonly,
opportunities.write, calendars.readonly, calendars/events.write,
conversations.readonly, conversations/message.write, invoices.readonly,
invoices.write, products.readonly, products.write,
locations/customFields.readonly, workflows.readonly
Copia el token — empieza por pit-.
2. Localizar tu ID de ubicación
Configuración → Perfil de negocio, o extráelo de la URL del panel de control: .../location/<LOCATION_ID>/...
3. Compilar
git clone <this-repo>
cd ghl-mcp
npm install
npm run build4. Registrar en un host MCP
{
"mcpServers": {
"gohighlevel": {
"command": "node",
"args": ["/absolute/path/to/ghl-mcp/dist/index.js"],
"env": {
"GHL_API_KEY": "pit-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"GHL_LOCATION_ID": "your-location-id"
}
}
}
}Reinicia el host. Mira .env.example para conocer todas las variables permitidas, incluido el bloque de datos de la factura y los toggles de módulo.
Para probar el servidor sin host:
GHL_API_KEY=pit-... GHL_LOCATION_ID=... npm run inspectNota sobre «construir automatizaciones»
La API de GoHighLevel no puede crear la lógica de flujos de trabajo: el editor visual es el único sitio que lo permite. Lo compatible es construir el workflow una vez en la interfaz, encontrar su id con ghl_list_workflows y añadir contactos con ghl_add_contact_to_workflow.
Referencia de herramientas
Área | Herramientas |
Contactos |
|
Oportunidades / Pipelines |
|
Calendarios / Citas |
|
Conversaciones / Mensajería |
|
Facturas |
|
Presupuestos |
|
Productos |
|
Campos personalizados |
|
Tareas |
|
Notas |
|
Workflows / flujos (mostrar incluye"?) |
|
Pagos |
|
Formularios y encuestas |
|
Usuarios y equipos |
|
Eventos de calendario |
|
Planificador social |
|
Biblioteca de medios |
|
Campañas y enlaces |
|
Etiquetas |
|
Valores personalizados |
|
Empresas |
|
Objetos personalizados |
|
Asociaciones |
|
Embudos |
|
Licencia
MIT — consulta LICENSE. Sin afiliación ni respaldo de GoHighLevel.
Available Tools
114 toolsghl_add_contact_tagsAdd contact tagsAIdempotent
Add one or more tags to a contact without removing existing tags.
Inputs: tags (required), contactId (required).
ghl_add_contact_to_campaignAdd contact to campaignAIdempotent
Enroll a contact into a campaign, starting it for them.
Inputs: contactId (required), campaignId (required).
ghl_add_contact_to_workflowAdd contact to workflowAIdempotent
Enroll a contact into an automation workflow, triggering it for that contact. Use ghl_list_workflows to find workflowId.
Inputs: contactId (required), workflowId (required), eventStartTime.
ghl_block_calendar_slotBlock calendar slotA
Block off time on a calendar so it can't be booked (e.g. a filming or edit day). startTime/endTime are ISO 8601 strings.
Inputs: endTime (required), startTime (required), title, calendarId, +2 more.
ghl_create_appointmentBook appointmentA
Book an appointment on a calendar for a contact. startTime/endTime are ISO 8601 strings (e.g. 2026-06-20T15:00:00-04:00). Use ghl_get_free_slots first.
Inputs: contactId (required), startTime (required), calendarId (required), title, +4 more.
ghl_create_appointment_noteCreate appointment noteA
Add a note to a calendar appointment (e.g. outcome of a shoot/call).
Inputs: body (required), appointmentId (required), userId.
ghl_create_businessCreate businessC
Create a business (company) record.
Inputs: name (required), city, email, phone, +6 more.
ghl_create_contactCreate contactA
Create a new contact. At least one of email or phone is recommended so the contact can be matched/deduplicated. Returns the created contact.
Inputs: name, tags, email, phone, +5 more.
ghl_create_contact_noteCreate contact noteA
Add a note to a contact.
Inputs: body (required), contactId (required), userId.
ghl_create_contact_taskCreate contact taskA
Create a task on a contact. dueDate is ISO 8601 (e.g. 2026-06-20T17:00:00Z).
Inputs: title (required), dueDate (required), contactId (required), body, +2 more.
ghl_create_custom_fieldCreate custom fieldA
Create a custom field definition. For option-based types (SINGLE_OPTIONS, MULTIPLE_OPTIONS, RADIO, CHECKBOX) provide the options array.
Inputs: name (required), dataType (required), model, options, +3 more.
ghl_create_custom_valueCreate custom valueC
Create a new custom value (merge field) with a name and value.
Inputs: name (required), value (required), locationId.
ghl_create_estimateCreate estimateA
Create an estimate (quote) for a contact with line items. If your account requires it, get estimateNumber from ghl_generate_estimate_number first. issueDate/expiryDate are YYYY-MM-DD.
Inputs: name (required), items (required), contactId (required), title, +15 more.
ghl_create_invoiceCreate invoiceA
Create a draft invoice for a contact. Provide line items (name, qty, price). Business details are taken from GHL_BUSINESS_* env vars (or businessName/businessPhone overrides); contact details (name, phone, email, address) are auto-filled from the contact record. The invoice is created in draft status; use ghl_send_invoice to deliver it.
Inputs: name (required), items (required), contactId (required), title, +14 more.
ghl_create_object_recordCreate custom object recordB
Create a record for a custom object. properties is a key/value map matching the schema's property keys.
Inputs: schemaKey (required), properties (required), locationId.
ghl_create_opportunityCreate opportunityA
Create a new opportunity (deal) in a pipeline stage. Use ghl_get_pipelines first to obtain valid pipelineId and pipelineStageId values.
Inputs: name (required), contactId (required), pipelineId (required), pipelineStageId (required), +4 more.
ghl_create_productCreate productA
Create a product. After creating, add one or more prices with ghl_create_product_price so it can be used on invoices/estimates.
Inputs: name (required), locationId, description, productType, +1 more.
ghl_create_product_priceCreate product priceA
Add a price to a product. type 'one_time' for a single charge or 'recurring' for a subscription. amount is in the smallest practical unit of the currency as accepted by GHL (typically major units, e.g. 49.99).
Inputs: name (required), amount (required), productId (required), type, +2 more.
ghl_create_relationCreate relationA
Create a relation between two records using an association definition. Get associationId from ghl_list_associations.
Inputs: associationId (required), firstRecordId (required), secondRecordId (required), locationId.
ghl_create_social_postCreate social postA
Schedule or publish a social post to one or more connected accounts. Provide scheduleDate (ISO 8601) for a scheduled post; omit for an immediate draft per status. mediaUrls can include image/video URLs already hosted in GHL.
Inputs: summary (required), accountIds (required), status, mediaUrls, +2 more.
ghl_create_tagCreate tagC
Create a new tag in the location's master tag list.
Inputs: name (required), locationId.
ghl_create_trigger_linkCreate trigger linkA
Create a trackable trigger link that redirects to a destination URL and can fire automations on click.
Inputs: name (required), redirectTo (required), locationId.
ghl_delete_appointmentDelete appointment / calendar eventADestructiveIdempotent
Delete a calendar event by its id. Works for both appointments and blocked time slots. Destructive and cannot be undone — to keep the record but mark it off, use ghl_update_appointment with appointmentStatus 'cancelled' instead.
Inputs: eventId (required).
ghl_delete_businessDelete businessBDestructiveIdempotent
Delete a business record. Destructive.
Inputs: businessId (required).
ghl_delete_contactDelete contactADestructiveIdempotent
Permanently delete a contact. This is destructive and cannot be undone.
Inputs: contactId (required).
ghl_delete_contact_noteDelete contact noteADestructiveIdempotent
Delete a note from a contact. Destructive.
Inputs: noteId (required), contactId (required).
ghl_delete_contact_taskDelete contact taskADestructiveIdempotent
Delete a task from a contact. Destructive.
Inputs: taskId (required), contactId (required).
ghl_delete_custom_fieldDelete custom fieldADestructiveIdempotent
Delete a custom field definition. Destructive: removes the field and its stored values across records.
Inputs: customFieldId (required), locationId.
ghl_delete_custom_valueDelete custom valueCDestructiveIdempotent
Delete a custom value. Destructive.
Inputs: customValueId (required), locationId.
ghl_delete_estimateDelete estimateCDestructiveIdempotent
Delete an estimate. Destructive.
Inputs: estimateId (required), locationId.
ghl_delete_invoiceDelete invoiceADestructiveIdempotent
Delete an invoice. Only works while it is a draft — a sent invoice must be voided with ghl_void_invoice instead. Destructive and cannot be undone.
Inputs: invoiceId (required), locationId.
ghl_delete_mediaDelete media fileCDestructiveIdempotent
Delete a file from the Media Library. Destructive.
Inputs: fileId (required), locationId.
ghl_delete_object_recordDelete custom object recordCDestructiveIdempotent
Delete a custom object record. Destructive.
Inputs: recordId (required), schemaKey (required), locationId.
ghl_delete_productDelete productCDestructiveIdempotent
Delete a product. Destructive.
Inputs: productId (required), locationId.
ghl_delete_relationDelete relationBDestructiveIdempotent
Delete a relation between two records. Destructive.
Inputs: relationId (required), locationId.
ghl_delete_social_postDelete social postADestructiveIdempotent
Delete a scheduled or draft social post. Destructive.
Inputs: postId (required), locationId.
ghl_delete_tagDelete tagADestructiveIdempotent
Delete a tag from the location. Destructive: removes it from records.
Inputs: tagId (required), locationId.
ghl_delete_trigger_linkDelete trigger linkBDestructiveIdempotent
Delete a trigger link. Destructive.
Inputs: linkId (required).
ghl_estimate_to_invoiceConvert estimate to invoiceA
Create an invoice from an accepted estimate, carrying over its line items.
Inputs: estimateId (required), locationId.
ghl_generate_estimate_numberGenerate estimate numberARead-only
Generate the next available estimate number for the location. Some accounts require an estimateNumber when creating an estimate — call this first.
Inputs: locationId.
ghl_get_appointmentGet appointmentBRead-only
Fetch a single calendar appointment/event by id.
Inputs: appointmentId (required).
ghl_get_businessGet businessARead-only
Fetch a single business record by id.
Inputs: businessId (required).
ghl_get_calendar_eventsGet calendar eventsARead-only
List calendar events/appointments within a time window. You must provide one of calendarId, userId, or groupId to scope the query. startTime/endTime are epoch milliseconds.
Inputs: endTime (required), startTime (required), userId, groupId, +2 more.
ghl_get_calendarsList calendarsARead-only
List calendars for a location. Use this to find a calendarId for booking and availability lookups.
Inputs: locationId.
ghl_get_contactGet contactARead-only
Fetch a single contact by id, including custom fields and tags.
Inputs: contactId (required).
ghl_get_contact_noteGet contact noteBRead-only
Fetch a single note on a contact by id.
Inputs: noteId (required), contactId (required).
ghl_get_contact_taskGet contact taskBRead-only
Fetch a single task on a contact by id.
Inputs: taskId (required), contactId (required).
ghl_get_custom_fieldGet custom fieldARead-only
Fetch a single custom field definition by id.
Inputs: customFieldId (required), locationId.
ghl_get_custom_valueGet custom valueCRead-only
Fetch a single custom value by id.
Inputs: customValueId (required), locationId.
ghl_get_form_submissionsGet form submissionsARead-only
Fetch submissions for a location's forms, optionally filtered to one form or a date range. Dates are YYYY-MM-DD.
Inputs: page, endAt, limit, formId, +2 more.
ghl_get_free_slotsGet free appointment slotsARead-only
Get available booking slots for a calendar within a date range. startDate and endDate are epoch milliseconds.
Inputs: endDate (required), startDate (required), calendarId (required), timezone.
ghl_get_invoiceGet invoiceARead-only
Fetch a single invoice by id, including line items and totals.
Inputs: invoiceId (required), locationId.
ghl_get_messagesGet conversation messagesARead-only
Fetch messages within a conversation thread, newest first. Use ghl_search_conversations to find a conversationId.
Inputs: conversationId (required), limit.
ghl_get_object_recordGet custom object recordBRead-only
Fetch a single custom object record by id.
Inputs: recordId (required), schemaKey (required), locationId.
ghl_get_object_schemaGet custom object schemaBRead-only
Fetch a custom object schema by key (e.g. custom_objects.podcast_episode), including its properties.
Inputs: schemaKey (required), locationId.
ghl_get_opportunityGet opportunityARead-only
Fetch a single opportunity (deal) by id.
Inputs: opportunityId (required).
ghl_get_orderGet orderARead-only
Fetch a single payment order by id, including line items and amounts.
Inputs: orderId (required), locationId.
ghl_get_pipelinesList pipelinesARead-only
List all opportunity pipelines and their stages for a location. Use this to discover pipelineId and pipelineStageId values needed by other tools.
Inputs: locationId.
ghl_get_productGet productBRead-only
Fetch a single product by id.
Inputs: productId (required), locationId.
ghl_get_record_relationsGet record relationsBRead-only
List the relations a given record participates in.
Inputs: recordId (required), skip, limit, locationId.
ghl_get_social_postGet social postARead-only
Fetch a single social post by id.
Inputs: postId (required), locationId.
ghl_get_subscriptionGet subscriptionCRead-only
Fetch a single subscription by id.
Inputs: subscriptionId (required), locationId.
ghl_get_survey_submissionsGet survey submissionsARead-only
Fetch submissions for a location's surveys, optionally filtered to one survey.
Inputs: page, endAt, limit, startAt, +2 more.
ghl_get_userGet userBRead-only
Fetch a single user by id.
Inputs: userId (required).
ghl_list_appointment_notesList appointment notesARead-only
List notes attached to a calendar appointment.
Inputs: appointmentId (required), limit, offset.
ghl_list_associationsList associationsARead-only
List association definitions in a location (the relationship types available between record kinds).
Inputs: skip, limit, locationId.
ghl_list_businessesList businessesARead-only
List business (company) records in a location.
Inputs: locationId.
ghl_list_campaignsList campaignsARead-only
List marketing campaigns in a location. Use a campaign id with ghl_add_contact_to_campaign.
Inputs: status, locationId.
ghl_list_contact_notesList contact notesARead-only
List all notes logged on a contact, newest first.
Inputs: contactId (required).
ghl_list_contact_tasksList contact tasksBRead-only
List all tasks attached to a contact.
Inputs: contactId (required).
ghl_list_custom_fieldsList custom fieldsARead-only
List custom field definitions for a location. Filter by model (contact, opportunity, or all) to see which fields apply where. Use the returned ids when reading/writing custom field values on contacts.
Inputs: model, locationId.
ghl_list_custom_valuesList custom valuesARead-only
List location custom values (reusable merge fields used in templates/messages).
Inputs: locationId.
ghl_list_estimatesList estimatesARead-only
List estimates (quotes) for a location with pagination. Optionally filter by status or contact.
Inputs: limit, offset, status, contactId, +1 more.
ghl_list_formsList formsARead-only
List forms in a location. Use the returned form ids to fetch submissions.
Inputs: skip, limit, locationId.
ghl_list_funnel_pagesList funnel pagesCRead-only
List the pages within a funnel.
Inputs: funnelId (required), name, limit, offset, +1 more.
ghl_list_funnelsList funnelsARead-only
List funnels in a location. Optionally filter by type, category, or name.
Inputs: name, type, limit, offset, +2 more.
ghl_list_invoicesList invoicesARead-only
List invoices for a location with pagination. Optionally filter by status (e.g. draft, sent, paid) and contact.
Inputs: limit, offset, status, contactId, +1 more.
ghl_list_mediaList media filesARead-only
List files/folders in the location's Media Library with pagination, search, and optional type filter.
Inputs: type, limit, query, offset, +3 more.
ghl_list_object_schemasList custom object schemasARead-only
List the custom object (and standard object) schemas defined in a location. Use the returned schema key with the record tools.
Inputs: locationId.
ghl_list_ordersList ordersARead-only
List payment orders for a location with pagination. Optionally filter by status or contact. Use to see what was purchased and whether it was paid.
Inputs: limit, offset, status, contactId, +1 more.
ghl_list_product_pricesList product pricesARead-only
List the prices configured for a product.
Inputs: productId (required), limit, offset, locationId.
ghl_list_productsList productsARead-only
List products in a location with pagination and optional search. Use the returned product ids when adding prices or building invoices/estimates.
Inputs: limit, offset, search, locationId.
ghl_list_social_accountsList social accountsARead-only
List the social media accounts connected to the location's Social Planner. Use the returned account ids when creating a post.
Inputs: locationId.
ghl_list_social_postsList social postsBRead-only
List scheduled/published social posts for the location. Optionally filter by account ids and a date range (ISO 8601).
Inputs: skip, type, limit, toDate, +3 more.
ghl_list_subscriptionsList subscriptionsARead-only
List recurring subscriptions for a location (e.g. retainers). Optionally filter by contact.
Inputs: limit, offset, contactId, locationId.
ghl_list_surveysList surveysARead-only
List surveys in a location. Use the returned survey ids to fetch submissions.
Inputs: skip, limit, locationId.
ghl_list_tagsList tagsARead-only
List all tags defined in a location.
Inputs: locationId.
ghl_list_transactionsList transactionsARead-only
List payment transactions for a location. Useful for reconciling revenue and spotting failed or refunded charges.
Inputs: limit, offset, contactId, locationId.
ghl_list_trigger_linksList trigger linksARead-only
List trackable trigger links in a location.
Inputs: locationId.
ghl_list_usersList usersARead-only
List users (team members) in a location. Use the returned ids as assignedTo / assignedUserId values when creating tasks, opportunities, or appointments.
Inputs: locationId.
ghl_list_workflowsList workflowsARead-only
List the automation workflows configured in a location. Note: workflows must be built in the GoHighLevel UI; the API cannot create them. Use the returned workflow ids with ghl_add_contact_to_workflow to trigger automations.
Inputs: locationId.
ghl_remove_contact_from_campaignRemove contact from campaignAIdempotent
Remove a contact from a campaign (or all campaigns if no id given).
Inputs: contactId (required), campaignId.
ghl_remove_contact_from_workflowRemove contact from workflowBIdempotent
Remove a contact from an automation workflow, halting it for them.
Inputs: contactId (required), workflowId (required).
ghl_search_contactsSearch contactsARead-only
Search/list contacts in a GoHighLevel location. Supports a free-text query (matches name, email, phone) and pagination. Returns matching contacts.
Inputs: limit, query, locationId, startAfter, +1 more.
ghl_search_conversationsSearch conversationsARead-only
Search conversations in a location, optionally filtered to a contact. Returns conversation threads with their ids and last-message info.
Inputs: limit, query, contactId, locationId.
ghl_search_object_recordsSearch custom object recordsCRead-only
Search records of a custom object by a text query.
Inputs: schemaKey (required), skip, limit, query, +1 more.
ghl_search_opportunitiesSearch opportunitiesARead-only
Search opportunities (deals) in a location. Filter by pipeline, stage, status, assigned user, or free-text query.
Inputs: page, limit, query, status, +5 more.
ghl_send_estimateSend estimateA
Send an estimate to the contact. Outward-facing: this emails/texts the customer.
Inputs: estimateId (required), action, userId, liveMode, +1 more.
ghl_send_invoiceSend invoiceA
Send/deliver an existing invoice to the contact via the configured channel(s). This is outward-facing: it emails/texts the customer.
Inputs: invoiceId (required), action, userId, liveMode, +1 more.
ghl_send_messageSend messageA
Send an outbound message to a contact via SMS or Email. For Email you must provide subject and html (or message as plain text). For SMS provide message. The contact must have a valid phone/email for the chosen channel.
Inputs: type (required), contactId (required), html, message, +2 more.
ghl_update_appointmentUpdate appointmentAIdempotent
Update an appointment's time or status (e.g. confirm, cancel, mark showed). Only provided fields are changed.
Inputs: appointmentId (required), title, endTime, startTime, +1 more.
ghl_update_businessUpdate businessAIdempotent
Update a business record. Only provided fields change.
Inputs: businessId (required), city, name, email, +6 more.
ghl_update_contactUpdate contactAIdempotent
Update fields on an existing contact. Only provided fields are changed.
Inputs: contactId (required), tags, email, phone, +3 more.
ghl_update_contact_noteUpdate contact noteBIdempotent
Update the text of an existing note on a contact.
Inputs: body (required), noteId (required), contactId (required), userId.
ghl_update_contact_taskUpdate contact taskBIdempotent
Update a task (e.g. mark completed, change due date or assignee). Only provided fields change.
Inputs: taskId (required), contactId (required), body, title, +3 more.
ghl_update_custom_fieldUpdate custom fieldAIdempotent
Update a custom field definition. Only provided fields change.
Inputs: customFieldId (required), name, options, position, +2 more.
ghl_update_custom_valueUpdate custom valueBIdempotent
Update a custom value's name and/or value.
Inputs: name (required), value (required), customValueId (required), locationId.
ghl_update_estimateUpdate estimateAIdempotent
Update an existing estimate. Pass the full set of items you want on the estimate (they replace the prior items). Only provided top-level fields change.
Inputs: estimateId (required), name, items, title, +4 more.
ghl_update_object_recordUpdate custom object recordCIdempotent
Update a custom object record's properties.
Inputs: recordId (required), schemaKey (required), properties (required), locationId.
ghl_update_opportunityUpdate opportunityAIdempotent
Update an opportunity: move stage, change status, value, name, or owner. Only provided fields are changed.
Inputs: opportunityId (required), name, status, assignedTo, +3 more.
ghl_update_productUpdate productAIdempotent
Update a product's fields. Only provided fields change.
Inputs: productId (required), name, locationId, description, +2 more.
ghl_update_tagUpdate tagCIdempotent
Rename an existing tag.
Inputs: name (required), tagId (required), locationId.
ghl_upload_media_by_urlUpload media by URLA
Add a file to the Media Library by referencing a publicly reachable URL (GHL fetches and hosts it). Good for deliverables or talent photos already available at a link. For raw binary uploads use the GHL UI.
Inputs: fileUrl (required), name, locationId.
ghl_void_invoiceVoid invoiceADestructiveIdempotent
Void an invoice. Use this for invoices that have already been sent (which can no longer be deleted). Voiding cancels the invoice while keeping the record.
Inputs: invoiceId (required), locationId.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 114 tools
Tool names consistently include the target resource (contact, opportunity, invoice, task, note, etc.), so most actions are clearly distinct even with 114 tools. A few near-neighbor pairs—custom_field vs custom_value, contact_note vs appointment_note, and association vs relation—could require careful description reading, but they are not genuinely interchangeable.
The dominant ghl_<verb>_<noun> pattern is clear and mostly followed. However, several plural list operations use get_ instead of list_ (ghl_get_calendars, ghl_get_pipelines, ghl_get_messages, ghl_get_form_submissions), and ghl_estimate_to_invoice breaks the verb_noun pattern.
114 tools is an extreme count for an agent-facing MCP server; even though GoHighLevel covers many domains, this surface is far beyond the 3-15 tool range considered well-scoped. The sheer number will overwhelm tool selection and context windows regardless of how individually useful the tools are.
The server covers a very wide range of GHL resources with strong CRUD coverage for contacts, tasks, notes, products, tags, custom values, and businesses. Notable gaps exist, though: there is no ghl_get_estimate (making estimate updates awkward), no ghl_update_invoice, and no delete for opportunities, leaving some lifecycle dead ends.
Related MCP Connectors
Agent-native CRM. 25 tools — contacts, deals, sequences, enrichment waterfall, audit log.
Open-source CRM your AI agents can write to: companies, people, opportunities, tasks and notes.
CRM, inbox, meetings, revenue intelligence, analytics and automations for AI agents.
Open-source CRM for AI agents: humans, orgs, interactions, deals, tasks, links and an activity log.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to perform CRM operations like creating contacts, managing deals, and updating leads through natural language using the Model Context Protocol.4-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to interact with a CRM covering companies, people, leads, deals, and more, with role checks, scoped agent keys, approval gates, and a shared audit trail.AGPL 3.0
- FlicenseNot gradedqualityDmaintenanceAn MCP-native CRM backend for AI agents, enabling customer, opportunity, note, follow-up, and pipeline health management through 15 MCP tools.-
- AlicenseNot gradedqualityCmaintenanceExposes the entire CRM as rows in Postgres via 73 MCP tools, letting AI agents create, read, update, and manage tables, documents, dashboards, chat, calendar, agent memory, web research, and images through the same operations as the UI.MIT