GoHighLevel Private Integration Token: Complete Setup Guide for AI Connections

When connecting AI tools like Claude MCP to a GoHighLevel sub-account, the most common authentication method is the Private Integration Token (PIT). If you have heard this term and are not sure exactly what it is, how to create one, or how to manage it securely, this guide covers everything you need to know.

What Is a GoHighLevel Private Integration Token?

A GoHighLevel Private Integration Token (PIT) is a static API key scoped to a single GHL sub-account. It gives external tools — like the Urooj Labs Sub-Account MCP — authenticated access to that sub-account's data and functions through GHL's API.

Key characteristics of a GHL PIT:

• Static — it does not expire or rotate automatically like OAuth tokens
• Sub-account scoped — it only provides access to the one sub-account where it was created
• Permission-controlled — you choose exactly which API scopes the token can access
• Simple to generate — created in seconds from GHL sub-account settings
• Revocable — you can delete or regenerate the token at any time

PIT vs GHL OAuth Token: What Is the Difference?

Step-by-Step: Creating Your GHL Private Integration Token

Creating a PIT takes about 60 seconds. Here is the exact process:

1. Log in to your GoHighLevel sub-account (not the agency dashboard)
2. Click the Settings gear icon in the left navigation sidebar
3. Scroll down in the left settings menu to find Private Integrations and click it
4. Click the Create New Integration button (or similar, depending on your GHL version)
5. Enter a name for this integration — use something descriptive like "Urooj Labs MCP Access"
6. Select the permission scopes you want this token to have access to (see the next section for guidance)
7. Click Create
8. Copy the token immediately — GHL only shows it once. If you miss it, you will need to regenerate

Understanding PIT Permission Scopes

When creating your PIT, you select which areas of the GHL account it can access. For use with the Urooj Labs Sub-Account MCP, the recommended scopes are:

You can enable all available scopes for maximum Claude capability, or restrict to only the areas relevant to your use case. Claude will only be able to interact with the parts of GHL covered by the scopes you enable.

Security Best Practices for GHL PITs

A PIT is as sensitive as a password for that sub-account. Follow these practices to keep it secure:

• Do not share publicly — never post your PIT in a public forum, Slack channel, or email thread
• Use environment variables — if you are building a custom integration, store PITs in environment variables, not hardcoded in scripts
• One PIT per integration — create separate PITs for each service you connect to the same sub-account. This allows you to revoke individual access without disrupting other integrations
• Audit regularly — periodically review the Private Integrations list in GHL settings and remove any tokens that are no longer in use
• Regenerate if compromised — if you suspect a token has been exposed, regenerate it immediately from GHL settings

Using Your PIT to Connect Claude AI to Your GHL Sub-Account

Once you have your PIT, connecting it to the Urooj Labs Sub-Account MCP is straightforward:

1. Sign up for the Urooj Labs Sub-Account MCP at uroojlabs.com
2. During onboarding, provide your GHL sub-account ID and the PIT you created
3. Urooj Labs configures your personal MCP server and provides you with a server URL
4. Add this URL to Claude Desktop under Settings > MCP Servers
5. Restart Claude Desktop — your GHL sub-account tools are now active

Your PIT is stored securely by Urooj Labs and used only to authenticate Claude's API calls to your sub-account. It is never exposed in conversation logs or passed through unsecured channels.