Skip to main content

Connect Jeremy AI to GoHighLevel

Give your workers your whole CRM — contacts, pipeline, conversations, and calendars — with one Custom MCP connection. Video walkthrough and step-by-step guide.

V
Written by Victor Couto

Your CRM shouldn't be a separate tab. Connect GoHighLevel to Jeremy AI once, and your workers can pull contacts, read the pipeline, check calendars, and work with conversations — right from chat. The connection uses HighLevel's own MCP server and takes about three minutes, start to finish.

Watch the walkthrough

The video shows the full flow: adding a Custom MCP server in Jeremy AI, creating a Private Integration token in HighLevel, grabbing your Location ID, and confirming the connection with a live question. If the player doesn't load, watch it here.

Before you start

  • An account on your instance's web app (for example https://jeremy.utari.ai), signed in.

  • A GoHighLevel account with admin access to the location (sub-account) you want to connect.

  • Five minutes in HighLevel's settings — you'll create a Private Integration token and copy your Location ID.

  • Treat the token like a password: it can read and update your account data. Don't share it or paste it anywhere public.

Step 1 — Log in to your dashboard

  1. Go to jeremy.utari.ai.

  2. Enter your email address.

  3. Enter the 6-digit code sent to your email.

Step 2 — Add the Custom MCP server

  1. Open Integrations in the sidebar and click Add Custom MCP — it's on the right, just above your connected apps.

  2. Choose which worker gets HighLevel and click Continue. This decides who can use the connection.

  3. Give the server a short name — it's just a label. GoHighLevel works fine.

  4. For the MCP Server URL, paste HighLevel's endpoint — the same address for everyone: https://services.leadconnectorhq.com/mcp/

  5. Expand Add Headers (optional). You're adding two. Name the first header Authorization — exactly like that, with a capital A. Leave the value empty for now; it comes from HighLevel in the next step.

Step 3 — Create your HighLevel token

  1. In GoHighLevel, open your location's Settings (bottom left), then under Other Settings click Private Integrations.

  2. Click Create New Integration (top right) and give it a name you'll recognize — for example Jeremy AI.

  3. On the Scopes tab, choose what Jeremy can touch. Pick only the scopes you need — or use Select all to keep it simple. (HighLevel recommends granting as few as necessary; you can edit later.)

  4. Click Create and confirm. HighLevel shows your token once — it starts with pit-. Click Copy now, and treat it like a password.

Step 4 — Finish the two headers

  1. Back in Jeremy AI, click the Authorization value field and type the word Bearer, one space, then paste your token. Nothing else.

  2. Click + Add Header. Name the second header locationId.

  3. Its value lives in HighLevel under Settings → Business Profile — the Location ID at the top of General Information has a copy icon next to it. Copy it, and paste it as the value.

Step 5 — Connect and choose tools

  1. Click Connect to MCP Server. The green banner means the handshake worked — Jeremy found HighLevel's full toolkit (36 tools: contacts, opportunities, conversations, calendars, payments, blogs, and more).

  2. Keep the tools you want your worker to have, then click Add MCP Server. The connection now appears under Custom MCP Servers on your Integrations page, and you can adjust its tools anytime with Configure tools.

Step 6 — Test it

  1. Open a chat with the worker you connected and ask: Are you connected to GoHighLevel?

  2. It should confirm and list what it can now do. From there, try it on real work:

  • Summarize my pipeline — what's in each stage and what needs attention?

  • Find the contact [NAME] and show me their recent conversations.

  • What's booked on my calendar this week?

Tips

  • One location per connection. The token and Location ID are scoped to a single sub-account. To connect another location, repeat the setup with that location's token and ID.

  • Type the headers exactly. Authorization with a capital A; the value is Bearer, one space, then the token — no quotes, nothing else.

  • Rotate the token if it's ever exposed. In HighLevel's Private Integrations, open your integration and use Rotate and expire this token now — then paste the new token into the header value in Jeremy AI.

  • Scopes are editable. If a tool errors later, the token may be missing its scope — edit the integration's scopes in HighLevel and try again.

Troubleshooting

  • "Connect to MCP Server" fails — check the URL is exactly https://services.leadconnectorhq.com/mcp/ and the Authorization value is Bearer + space + token, with no quotes or trailing spaces.

  • It connected before but stopped working — the token may have been rotated or expired. Create or rotate the token in Private Integrations and update the header value.

  • Tools connect but return errors — the locationId header may be missing or from the wrong sub-account, or the token is missing scopes for those tools.

  • You can't find Private Integrations in HighLevel — it's under your location's Settings (not the agency view), and your HighLevel user needs admin access to that location.

Support

Stuck on any step? Reach out to us through the messenger and we'll help you get set up.

Did this answer your question?