Connect HighLevel to Conduit

This walkthrough connects HighLevel (GoHighLevel) to Conduit. HighLevel runs its own hosted MCP server. Conduit proxies your calls to https://services.leadconnectorhq.com/mcp/. You create a Private Integration Token in a HighLevel sub-account, copy that location’s ID, and add both as an organization connection in Conduit.

Use Conduit’s HighLevel connection. Do not also paste the Cursor or Claude mcpServers config from HighLevel’s MCP server article into your AI client. That config talks to HighLevel directly and skips Conduit’s access grants and audit log. HighLevel has said OAuth is planned for later. Conduit uses the Private Integration Token today.

HighLevel shows a Preview badge until a live connection has been verified.

Menu labels can change

The HighLevel steps below reflect the current app flow; menu labels can shift between releases. If a label differs, see How to set up and use the HighLevel MCP server — that article is the authority for this flow.

Before you start

You need:

• A Conduit role that can manage connections — owner or admin on your organization.
• Access to the HighLevel sub-account (location) you want the AI client to use.

Step 1 — Create a Private Integration Token

1. Sign in to HighLevel and open the sub-account. Expected: that location’s dashboard.
2. Go to Settings → Private Integrations.
3. Click Create New Integration, choose the scopes this connection needs, and create it. Include View Locations. Conduit reads the location once at connect time to confirm the token and the location ID belong together. Expected: a token, shown at creation.
4. Copy the token immediately, and copy the sub-account’s location ID.

Least privilege still applies. Add write scopes (edit contacts, send messages, and so on) only for the actions you want the AI client to take. HighLevel’s article lists the scopes it recommends.

Caution

Copy the token now and store it somewhere safe. Don’t paste it into chat, email, or a shared document — the next step moves it directly into Conduit, which encrypts it at rest. If you accidentally expose the token, delete the Private Integration in HighLevel and create a new one. The exposed token stops working immediately.

Step 2 — Connect HighLevel in Conduit

1. In Conduit, go to Connections (/org/catalog). Expected: the vendor catalog.
2. Find HighLevel in the catalog (under CRM) and click Connect. Expected: a credential form with Private Integration Token and Location ID, plus a note that Conduit talks to HighLevel’s hosted MCP.
3. Paste the token from Step 1 into Private Integration Token (secret).
4. Paste the location ID into Location ID.
5. Click Connect. Expected: Conduit checks the token against HighLevel’s hosted server and shows Connected. A bad token or location ID is rejected here, not on the first tool call.

The credential is stored at the organization scope, so every technician in your org shares this HighLevel connection. (For per-technician tokens, connect at the personal scope instead — see Vendor connections.)

Verify it worked

Connect an MCP client to Conduit (see Connecting an AI client) and ask it to run a read-only HighLevel tool, such as looking up a contact. Real data should come back, and the call appears in your audit log with vendor highlevel.

An organization owner can see HighLevel’s tools as soon as the connection succeeds. Other members may see none until HighLevel’s tools are classified for member access. That is an access-tier gap, not a bad token.

Troubleshooting

Symptom	Likely cause
Connect fails with “Enter both the token and the location ID.”	One of the two fields was left blank. Paste the Private Integration token and the location ID from the same sub-account.
Connect fails with “HighLevel didn’t accept that token and location ID. Make sure they’re from the same sub-account and the token includes View Locations.”	The token was mistyped or revoked, the location ID is from a different sub-account, or the token is missing View Locations. Create the integration under Settings → Private Integrations in that sub-account, include View Locations, and paste that same location’s ID. The location ID is the part of the browser address after /location/.
Connect fails with “HighLevel couldn’t look up that location. Add View Locations to the Private Integration and try again.”	HighLevel answered, but the location read failed. Edit the Private Integration, add View Locations, and try again.
Connect fails with “HighLevel returned an error (HTTP …). Try again in a minute.”	HighLevel’s server had a temporary problem. Wait a minute and try again.
Connect fails with “Couldn’t reach HighLevel. Try again in a minute.”	Conduit could not open a connection to HighLevel. Wait a minute and try again.
Tool calls return 403 “no credentials for vendor”	HighLevel isn’t connected at a scope this user can resolve. Connect it at the organization scope, or confirm the user’s team has a token.
An owner sees HighLevel tools and a member does not	The connection is fine. HighLevel’s tools are not classified for non-owner access yet, so they stay on the admin tier.
Need to rotate the token	Create a new Private Integration, update the credential at /org/catalog, then delete the old integration in HighLevel.
You also pasted HighLevel’s mcpServers block into Cursor or Claude	Remove that client config. Conduit is the MCP server your AI client should use. A second, direct HighLevel connection bypasses Conduit’s grants and audit log.

Related

• Vendor connections — credential scopes, rotation, and the full vendor catalog.
• Security — how Conduit encrypts and resolves the credential you just stored.
• HighLevel MCP server — where to create the token and which scopes HighLevel recommends.