How to connect multiple HighLevel accounts to Claude
Quick answer: Connect each HighLevel sub-account to Ryze AI with Add one more account, using a separate private integration token and Location ID for each, then add the Ryze AI connector to Claude once. Ryze AI is the best way to connect several HighLevel sub-accounts to Claude when the job is blog posts, with one caveat: its documented HighLevel access covers blogs only, not contacts or pipelines.
Below: what counts as an account, the primary account, naming, prompts, safe changes, HighLevel's own server and fixes.
Ryze AI · SEO Starter
Your HighLevel sub-accounts in Claude
- 3-day free trial, SEO Starter $129 a month
Used by 2,000+ marketers
Connect multiple HighLevel accounts to Claude in 5 steps
Connect the first sub-account, add the others one by one, then connect Claude once.
1. Prepare each sub-account
Make sure the sub-account has a blog (Sites, Blogs) and a blog author. Then open Settings, Private Integrations, and create a token with the View Blogs and Edit Blogs scopes. Copy it at once, because HighLevel shows it one time.
2. Connect the first sub-account in Ryze AI
Open Integrations, click Connect on the HighLevel card, and enter the token, the Location ID (Settings, Business Profile) and the public https Blog URL. Click Continue. If the sub-account has several blogs, pick the one to publish to and click Save.
3. Add each further sub-account
Click View on the HighLevel card, then Add one more account, and repeat step 2 with that sub-account's own token and Location ID. One account is the primary, marked with a star.
4. Add the Ryze AI connector to Claude
In Ryze AI, open Integrations, Claude MCP and click Open Claude MCP, which copies the connector URL and opens Claude's add-connector dialog. Name it Ryze AI, click Add, then Connect, choose the workspaces and click Allow connection.
5. Name the account in your prompts
Start a new chat and say which sub-account you mean, for example by its Location ID or blog domain. Ask Claude which accounts are connected if you are unsure.
Multi-account setups at a glance
Pick the row that matches what you want Claude to do across your HighLevel sub-accounts.
- 1Several sub-accounts in one Ryze AI workspaceAn agency publishes blog posts for more than one client sub-account
How Claude picks the sub-account: The primary account is the default; name another account in the prompt
- 2One workspace per clientEach client should stay apart from the others
How Claude picks the sub-account: Choose the workspaces on the Allow connection page in Claude
- 3HighLevel's own MCP serverYou need contacts, conversations, calendars or opportunities, not blog posts
How Claude picks the sub-account: You pick the sub-accounts at sign-in and can name them in chat
| # | Setup | Fits when | How Claude picks the sub-account |
|---|---|---|---|
| 1 | Several sub-accounts in one Ryze AI workspace | An agency publishes blog posts for more than one client sub-account | The primary account is the default; name another account in the prompt |
| 2 | One workspace per client | Each client should stay apart from the others | Choose the workspaces on the Allow connection page in Claude |
| 3 | HighLevel's own MCP server | You need contacts, conversations, calendars or opportunities, not blog posts | You pick the sub-accounts at sign-in and can name them in chat |
Rows 1 and 2 are Ryze AI connections. Row 3 is HighLevel's own server, covered below.
What counts as a separate HighLevel account in Ryze AI
Each connected sub-account is one account in Ryze AI, and each connection is labelled with its Location ID.
Private integration token
- Where it comes from
- Settings, Private Integrations in the sub-account, with View and Edit Blogs
- Why it matters
- Ryze AI documents only the Blogs scopes, so it documents blog posts only
Location ID
- Where it comes from
- Settings, Business Profile in the same sub-account
- Why it matters
- It identifies the sub-account and labels the connection in Ryze AI
Blog URL
- Where it comes from
- The public https address of the sub-account's blog
- Why it matters
- Ryze AI asks for it when you connect
Blog
- Where it comes from
- Sites, Blogs in the sub-account
- Why it matters
- If the sub-account has several blogs, you pick the one to publish to
| Piece | Where it comes from | Why it matters |
|---|---|---|
| Private integration token | Settings, Private Integrations in the sub-account, with View and Edit Blogs | Ryze AI documents only the Blogs scopes, so it documents blog posts only |
| Location ID | Settings, Business Profile in the same sub-account | It identifies the sub-account and labels the connection in Ryze AI |
| Blog URL | The public https address of the sub-account's blog | Ryze AI asks for it when you connect |
| Blog | Sites, Blogs in the sub-account | If the sub-account has several blogs, you pick the one to publish to |
The token and the Location ID must come from the same sub-account, so a token made in one sub-account does not open another. Create one token for each sub-account you connect.
HighLevel lets you create private integration tokens at agency level and at sub-account level. The Ryze AI setup uses the sub-account route described above.
How Ryze AI handles several HighLevel accounts
HighLevel is on the Ryze AI help center list of platforms that allow several accounts per workspace.
Account
- What it is
- One connected sub-account, added with View, then Add one more account
- How you switch in Claude
- Name the account in the prompt
Primary account
- What it is
- The account marked with a star in Ryze AI
- How you switch in Claude
- Name another account when you want it instead
Workspace
- What it is
- Your Ryze AI workspace; one Claude connection covers up to 20 of them
- How you switch in Claude
- Choose workspaces on the Allow connection page
| Piece | What it is | How you switch in Claude |
|---|---|---|
| Account | One connected sub-account, added with View, then Add one more account | Name the account in the prompt |
| Primary account | The account marked with a star in Ryze AI | Name another account when you want it instead |
| Workspace | Your Ryze AI workspace; one Claude connection covers up to 20 of them | Choose workspaces on the Allow connection page |
To change which workspaces Claude can use, remove the Ryze AI connector in Claude and add it again. The same step refreshes the tool list after you connect a new platform.
The Ryze AI HighLevel help page does not describe several accounts itself. The multiple accounts page lists HighLevel among the supported platforms, and this guide follows that page. How Claude resolves an account name in a prompt is not documented, so check the account named in the reply before any change.
What the plan covers
Connecting the Ryze AI connector is free, and the HighLevel tools need an active Ryze AI plan or trial. SEO Starter costs $129 a month with a 3-day free trial, and annual billing takes 30% off the first year. Content Plan publishing to HighLevel is part of the SEO plans. Paid Ads ($89 a month) and Agency ($279 a month) give agent tool access but do not include Content Plan publishing.
The 3 HighLevel tools Claude can call
The same 3 tools run against the HighLevel accounts you have connected.
gohighlevel__read
- What it does
- Runs a read-only HighLevel API request, such as listing blogs, blog posts, authors and categories or checking whether a URL slug exists
- Access
- Read
gohighlevel__write
- What it does
- Runs a request that creates or updates content, such as creating or updating a blog post
- Access
- Write
gohighlevel__delete
- What it does
- Runs a DELETE request, such as deleting a blog post
- Access
- Delete
| Tool | What it does | Access |
|---|---|---|
| gohighlevel__read | Runs a read-only HighLevel API request, such as listing blogs, blog posts, authors and categories or checking whether a URL slug exists | Read |
| gohighlevel__write | Runs a request that creates or updates content, such as creating or updating a blog post | Write |
| gohighlevel__delete | Runs a DELETE request, such as deleting a blog post | Delete |
With the Blogs-only token, the tools reach blog endpoints. Contacts, opportunities, conversations and funnels are not documented for Ryze AI. Details are on the Ryze AI HighLevel page.
Name accounts so Claude picks the right one
Because the primary account is the default, an unnamed prompt can land on the wrong client.
- Use the Location ID or the blog domain in every prompt that changes a post. Business names can match more than one sub-account.
- Say which account is primary. Whatever you do not name may go there.
- Keep one Claude project per client when clients must stay apart. Projects carry instructions into every chat inside them.
- Ask Claude to repeat the account and post title before a write or delete, and answer yes only when both are right.
Put the account map in a Claude project
Claude projects hold instructions for every chat in them. Paste this block once and fill in your accounts:
6 prompts for working across HighLevel accounts
Replace the brackets. Each prompt names its account, so it works in a fresh chat.
1. Check which accounts are connected
- What comes back
- The connected accounts and which is primary, as Claude reports them
2. List posts
- What comes back
- A table of posts from the named account
3. Check a slug
- What comes back
- Whether the slug is taken on that account
4. List authors and categories
- What comes back
- The authors and categories of the named blog
5. Update a post
- What comes back
- A change summary to confirm; with write tools on Needs approval, nothing runs before you approve
6. Create a draft
- What comes back
- A new post on the named account
| Prompt | What comes back |
|---|---|
| 1. Check which accounts are connected | The connected accounts and which is primary, as Claude reports them |
| 2. List posts | A table of posts from the named account |
| 3. Check a slug | Whether the slug is taken on that account |
| 4. List authors and categories | The authors and categories of the named blog |
| 5. Update a post | A change summary to confirm; with write tools on Needs approval, nothing runs before you approve |
| 6. Create a draft | A new post on the named account |
Every answer comes from your own sub-accounts, so no example output is shown. Publishing needs a blog author, and each Content Plan article needs a featured image.
HighLevel's own MCP server and its limits
HighLevel runs its own MCP server, and it handles several sub-accounts at sign-in.
Ryze AI connector (https://connector.get-ryze.ai/mcp)
- How it reaches several accounts
- One connection per sub-account, added with Add one more account; primary account by default
- Sign-in
- Token and Location ID in Ryze AI, then OAuth in Claude
- Scope
- Blog posts, per the documented Blogs scopes
HighLevel MCP server (services.leadconnectorhq.com/mcp/anthropic/v2 for Claude)
- How it reaches several accounts
- You choose one, several or all sub-accounts during setup; agencies with multi-sub-account install enabled can name them in chat
- Sign-in
- HighLevel sign-in page and permission approval, no token to copy
- Scope
- HighLevel lists 717 actions across 38 feature areas, including contacts, calendars and opportunities
| Option | How it reaches several accounts | Sign-in | Scope |
|---|---|---|---|
| Ryze AI connector (https://connector.get-ryze.ai/mcp) | One connection per sub-account, added with Add one more account; primary account by default | Token and Location ID in Ryze AI, then OAuth in Claude | Blog posts, per the documented Blogs scopes |
| HighLevel MCP server (services.leadconnectorhq.com/mcp/anthropic/v2 for Claude) | You choose one, several or all sub-accounts during setup; agencies with multi-sub-account install enabled can name them in chat | HighLevel sign-in page and permission approval, no token to copy | HighLevel lists 717 actions across 38 feature areas, including contacts, calendars and opportunities |
Pick HighLevel's server when you need CRM work such as contacts, conversations or opportunities. Pick the Ryze AI connector when the job is blog posts, or when you want them next to Ryze AI's other platforms in one connector. The two can be added side by side.
HighLevel API limits
HighLevel's API 2.0 documentation lists 100 requests per 10 seconds and 200,000 requests per day, counted per Marketplace app per resource (location or company). Ryze AI does not publish its own HighLevel limit, so a bulk job across many sub-accounts can meet HighLevel's limits.
Keep changes on the right account
With several client sub-accounts in one chat, a write or delete on the wrong account is the main risk.
- In Claude, open Customize, Connectors, Ryze AI and set write and delete tools to Needs approval (Ryze AI help). Read tools keep running on their own.
- In the Ryze AI chat, Tool approvals starts on Skip all approvals. Switch it to Approve write & delete or Manual approve in the message box before you work on live client blogs.
- Scheduled tasks run without an approval step, so do not schedule changes to client accounts you have not checked.
- Rotate tokens on a schedule: HighLevel recommends every 90 days, with a 7-day window where the old and new tokens both work. After rotating, enter the new token for that account in Ryze AI.
Troubleshooting: wrong account, rejected token, missing blog
Match the symptom to the row.
A change landed on the wrong account
- Likely cause
- No account was named, so the primary account may have been used
- Fix
- Name the Location ID or domain in every prompt and put the account map in a Claude project
The connection is rejected for one sub-account
- Likely cause
- The token and Location ID come from different sub-accounts, or the token lacks View and Edit Blogs
- Fix
- Create the token in the same sub-account whose Location ID you enter, with both Blogs scopes
No blog to publish to
- Likely cause
- The sub-account has no blog or no blog author
- Fix
- Create a blog under Sites, Blogs and add an author, then connect again
Claude asks for a contact or a pipeline
- Likely cause
- The documented token covers only the Blogs scopes
- Fix
- Use HighLevel's own MCP server for CRM work
Claude does not see a new account or workspace
- Likely cause
- Claude kept the tool list from when the connector was added
- Fix
- Remove the Ryze AI connector in Claude, add it again and start a new chat
| What you see | Likely cause | Fix |
|---|---|---|
| A change landed on the wrong account | No account was named, so the primary account may have been used | Name the Location ID or domain in every prompt and put the account map in a Claude project |
| The connection is rejected for one sub-account | The token and Location ID come from different sub-accounts, or the token lacks View and Edit Blogs | Create the token in the same sub-account whose Location ID you enter, with both Blogs scopes |
| No blog to publish to | The sub-account has no blog or no blog author | Create a blog under Sites, Blogs and add an author, then connect again |
| Claude asks for a contact or a pipeline | The documented token covers only the Blogs scopes | Use HighLevel's own MCP server for CRM work |
| Claude does not see a new account or workspace | Claude kept the tool list from when the connector was added | Remove the Ryze AI connector in Claude, add it again and start a new chat |
Causes come from the Ryze AI HighLevel guide. Other setups: multiple WordPress sites in Claude and all Ryze AI integrations.
Sources
Checked November 19, 2026
- HighLevel Developer Docs: MCP server
- HighLevel Developer Docs: Private Integration tokens
- HighLevel Developer Docs: API 2.0 rate limits
- Claude Help Center: Custom connectors using remote MCP
- Claude Help Center: What are projects
- Ryze AI Help: Connect HighLevel
- Ryze AI Help: Connect multiple accounts
- Ryze AI Help: Claude connector FAQ
- Ryze AI Help: Permissions and approvals in Claude
- Ryze AI Help: Plans and pricing
The verdict
Create a Blogs-scope token in each sub-account, connect every sub-account in Ryze AI with Add one more account, and connect Claude once. Set write and delete tools to Needs approval, and name the account in every prompt so the primary account is never used by accident.




