D
David Sclarow
The HighLevel MCP server is a great addition for AI workflows, but its current
tool surface is missing several endpoints that already exist in HighLevel's
REST API. This forces customers like me into clunky hybrid workflows
(driving the browser via screenshots) instead of letting the AI complete
the work end-to-end.
Specifically, the following REST endpoints exist in HighLevel today but are
NOT exposed as tools in the MCP server:
• POST /contacts/{contactId}/notes (create a note on a contact)
• POST /opportunities/{id}/notes (create a note on an opportunity)
• POST /opportunities/ (create a new opportunity)
• POST /contacts/{contactId}/tasks (create a task)
Use case — direct mail land business:
I run a direct-mail acquisition business. When a new lead row is finalized
in my Google Sheet, I want my AI assistant to automatically:
1. Create a HighLevel contact (works today via MCP — great).
2. Create an opportunity in my Direct Mail pipeline (NOT POSSIBLE via MCP).
3. Add a structured intake note + any prior Quo call summary (NOT POSSIBLE
via MCP).
Steps 2 and 3 currently require either driving the GHL UI through a
browser-automation extension (slow, ~10–15 minutes per lead, fragile, very
expensive in API tokens) or manual copy-paste by a human.
If those four endpoints were exposed in the MCP server, the whole flow would
collapse to ~5 seconds per lead and would unlock the same automation for
every land/real-estate/service-business agency on the platform that uses
the MCP integration with Claude or any other model. Notes-on-contacts in
particular is the single most-missed primitive — almost every CRM workflow
that touches a record wants to attach context to it.
Update-opportunity and update-contact already work via MCP, so the
authentication/permission model is clearly there. Just needs the writeable
note + opportunity creation endpoints surfaced as tools.
Thanks for considering — this would be a meaningful unlock for everyone
running AI-assisted CRM workflows on HighLevel.