Skip to content

CRM

Highlevel MCP connector

The Highlevel connector brings your Highlevel contacts, locations, pipelines, tags and custom fields to Claude, ChatGPT, Cursor and other AI clients, so your team can look up, update and organize CRM records by asking in plain language.

  • How it connects. OAuth or API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Highlevel to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Highlevel once

  1. Open Connections, choose Add connection, and pick Highlevel.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Supply your own Highlevel app, then approve. Highlevel needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

highlevel
Highlevel
Affinity
Attio
EveryAction
Google Contacts
HubSpot
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Connect Highlevel to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect Highlevel to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect Highlevel to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Highlevel to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Highlevel through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Sales

    Catch a contact up after a call

    Tell the agent what changed on the call and it updates the Highlevel contact, applies the right tag and adds the rep who now owns the relationship as a follower.

  • Marketing

    Tag contacts for the next campaign

    Search Highlevel for contacts that match a segment, such as everyone in a city or with a given custom field value, and apply a campaign tag to all of them in one ask.

  • Agency operations

    Set up a new client sub-account

    Create the Highlevel location for a new client, add the custom fields their intake form needs and create the starting set of tags, without clicking through every settings screen.

  • Support

    Find who is on the line

    Ask for a caller by name, phone or email and get the Highlevel contact record, its tags and its custom field values before you say hello.

  • Revenue operations

    Keep pipelines and fields consistent

    List every pipeline and custom field across your Highlevel locations, spot duplicates or drift, and rename or remove the ones that no longer belong.

  • Customer success

    Hand accounts over cleanly

    When an account manager changes, remove the old follower and add the new one across every affected Highlevel contact, then tag them for the welcome sequence.

Try asking

  • “List Highlevel contacts added to the London location this week.”
  • “Which Highlevel custom fields are empty on new contacts?”
  • “Add me as a follower on these three Highlevel contacts.”

See all 297 Highlevel tools below

AI tools

Highlevel tools for your AI agents

297 tools are ready to call through Elaichi's MCP endpoint the moment you connect Highlevel, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Highlevel gets you

6 screens from the product, each doing one job for your Highlevel account.

The agent

Ask about Highlevel contacts in plain language.

Starter prompts answer from live Highlevel contacts, locations and custom fields.

  • contacts
  • locations
  • custom fields
  • followers

Ask Elaichi to work across your apps.

List Highlevel contacts added to the London location this week.

Which Highlevel custom fields are empty on new contacts?

Add me as a follower on these three Highlevel contacts.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor share one endpoint.

Connect Highlevel from any MCP client over OAuth, no SDK, no shared key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

297 Highlevel tools are ready to call.

Contacts, locations, custom fields and followers are covered without custom code.

  • List all Highlevel contacts
  • Get single Highlevel contact by ID
  • Create a Highlevel contact
  • Update a Highlevel contact by ID
ElaichiTools
Tool Action Description
List all Highlevel contacts List Get contacts in Highlevel. Returns contacts array with fields id, locationId, email, timezone, country, source, dateAdded, customFields, tags, businessId, attributions, and followers. Note: endpoint is deprecated.
Get single Highlevel contact by ID Get Get contact details by id in Highlevel. Returns id, name, firstName, lastName, email, phone, companyName, address, tags, dateOfBirth, dateAdded, dateUpdated, dnd status, source, assignedTo, customFields, attributionSource, lastAttributionSource, and visitorId.
Create a Highlevel contact Create Upsert a contact in Highlevel. Returns contact details including id, name, email, phone, address, tags, customFields, and assignedTo.
Update a Highlevel contact by ID Update Update contact by id in Highlevel. Returns fields including id, name, email, phone, address, timezone, dnd settings, tags, customFields, assignedTo, and date metadata.
Delete a Highlevel contact by ID Delete Delete contact by id in Highlevel. Returns 'succeded' boolean indicating if the deletion was successful.

Toolboxes

Every team gets its own Highlevel toolbox.

Curate one toolbox per team, each scoped to the Highlevel work it does.

  • Sales
  • Marketing
  • Support
  • Operations
ElaichiToolboxes
Name Source template Tools Created

Sales toolbox

Highlevel · contacts and pipelines

Highlevel starter 18 Mar 4, 2026

Marketing toolbox

Highlevel · campaigns and custom fields

9 Mar 2, 2026

Support toolbox

Highlevel · contact records and followers

24 Feb 27, 2026

Operations toolbox

Highlevel · locations and settings

Highlevel starter 6 Feb 19, 2026

Onboarding toolbox

Highlevel · new location setup

31 Jan 30, 2026

Finance toolbox

Highlevel · invoices and payments

12 Jan 22, 2026

Shared connections

Teammates use Highlevel without seeing credentials.

See who connected each Highlevel account and how many teams and members share it.

  • Sales EMEA
  • Sales North America
  • Marketing
  • Support
ElaichiConnections
Connection Scope Status Access
HI

Highlevel (Sales EMEA)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
HI

Highlevel (Sales North America)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
HI

Highlevel (Marketing)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
HI

Highlevel (Support)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
HI

Highlevel (Agency clients)

Connected by Clara Nowak

Personal • Active Not shared
HI

Highlevel (Operations)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every Highlevel call is on the record.

When, who, what happened, type and resource for each Highlevel action.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Highlevel Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Highlevel Contacts Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Highlevel Contacts List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule drafts your Highlevel digest.

Six steps fetch contacts, group them, draft, wait for approval, post back to Highlevel.

Highlevel digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch contacts

    Highlevel

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Highlevel

    Queued

Collections and dashboards

Highlevel contact numbers refresh on a schedule.

Four metrics, fourteen days of contacts created, and a breakdown by team.

Highlevel health

Refreshed 4 minutes ago · every 15 minutes · from the contacts collection

Live

Contacts

1,284 ↓ 12%

Locations

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Contacts created

Last 14 days

By team

Share of activity

Sales EMEA 34%

Sales North America 27%

Marketing 21%

Support 18%

FAQ

Frequently asked questions

How do I connect Highlevel to Claude?

First connect Highlevel inside Elaichi, then paste the endpoint https://api.elaichi.ai/mcp into Claude under Customize, then Connectors, then Add. Highlevel requires an OAuth application registered in your own Highlevel account, so one person brings that client ID and secret to Elaichi once, or uses a Highlevel API key instead. After that, everyone else signs in with their normal Highlevel login and never touches a key or secret.

Does Highlevel work with ChatGPT and Cursor as well as Claude?

Yes. Once Highlevel is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Highlevel once and every client your team uses can reach it.

What can an AI agent actually do with my Highlevel data?

It can find a Highlevel contact by name, email or phone, create new contacts, update details, apply or remove tags and add or remove followers. It can also list your pipelines, locations and custom fields, and create or tidy up locations, tags and custom fields when you ask. Because Highlevel offers a large set of actions, short concrete asks such as "tag Maria Lopez as VIP" work better than long paragraphs.

Does connecting Highlevel give the AI access to every location and sub-account?

No. Each person signs in to Highlevel as themselves, so the AI only sees the locations, contacts and pipelines that person can already see in Highlevel. Elaichi can narrow that further with restrictions, but it can never widen access beyond what Highlevel grants the signed-in user.

Can my team share one Highlevel connection?

Yes. One person registers the Highlevel OAuth application or API key in Elaichi and shares the connection with a team, so nobody else ever handles a credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every change to a Highlevel contact or location.

Can I stop an agent from deleting or changing things in Highlevel?

Yes. In Elaichi you restrict actions one by one, so you can allow reading and updating Highlevel contacts while blocking deletion of contacts, locations, tags or custom fields. A blocked action is never shown to Claude, ChatGPT or any other client, so no prompt, accidental or otherwise, can reach it.

What happens to a Highlevel connection when someone leaves?

Offboard the person in Elaichi and their access to Highlevel through every AI client ends at once. A Highlevel connection they shared keeps working for everyone else on the team. If you want to remove Highlevel entirely, disconnect it once in Elaichi and it disappears from Claude, ChatGPT, Cursor and every other client at the same time.

Put Highlevel in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.