Can I upgrade from an existing HighLevel plan?
Yes. If you already have a HighLevel Starter, Unlimited, agency, or basic plan, the next step is to review the official Pro upgrade path and confirm the current upgrade options inside HighLevel.
Existing HighLevel user? Start here.
Upgrade to HighLevel Pro when Claude needs agency API control.
If you already use HighLevel and want Claude Cowork, Claude Code, skills, or MCP tools to help manage sub-accounts, SaaS plans, dashboards, and API workflows, this is the reason to evaluate SaaS Pro / Agency Pro: HighLevel documents Advanced API access and agency-level tokens on Pro.
Why upgrade for Claude Cowork or Claude Code?
Because agency-level Claude workflows need more than prompts. They need Advanced API access, agency-level context, SaaS Mode, and safer control across sub-accounts, SaaS plans, pipelines, and workflow reviews.
Does using HiVergent AI resources cost extra?
No. The guides, skill templates, and resource links on this page are free to use. If they help you, using our HighLevel Pro link is appreciated and may support our work at no extra cost to you.
Our Claude/HighLevel resources are free. If they help, using our HighLevel Pro link is appreciated and may support HiVergent AI at no additional cost to you.
Why your ad click landed here
Pro unlocks the agency API lane
intent: upgrade existing HighLevel account
reason: Claude + skills + MCP + API control
needed: Advanced API access / agency context
target: Agency Pro / SaaS Pro
The play: use Pro-level API access so Claude can help your agency audit sub-accounts, build safer scripts, inspect SaaS plans, review pipelines, and coordinate skill-based workflows with human approval.
Quick answer
Can I upgrade my existing HighLevel plan for Claude Cowork and agency API workflows?
Yes. If you already have a HighLevel plan, review the official Pro upgrade or trial options to confirm the current path for your account. The reason to upgrade is not just “more features.” It is that Claude skills, Claude Code, and Claude Cowork-style workflows become more useful when they can work with agency-level API access, OAuth, SaaS Mode, and sub-account context.
HiVergent AI’s skill templates and resources on this page are free. If they help you, using our HighLevel Pro link is appreciated and may support our work at no additional cost to you.
Why upgrade
The upgrade decision is really about who Claude is allowed to control.
If Claude is only helping one location, basic access may be enough. If Claude is going to help the agency owner review many sub-accounts, coordinate subagents, inspect SaaS plan status, or draft API calls across the agency, Pro is the cleaner operating model.
Without Pro
Claude can advise, but not operate at agency depth
- Useful for prompts, docs, and single-location planning
- Limited for cross-client operations
- Harder to build agency dashboards or SaaS plan controls
- Less room for OAuth, agency-token, and SaaS API workflows
With Pro
Claude can become an agency operations layer
- Advanced API access for deeper workflow design
- Agency-level context for sub-account oversight
- SaaS Mode and SaaS Configurator workflow potential
- Better foundation for Claude skills, MCP tools, scripts, and internal admin systems
Agency owner
Sets strategy, approves changes, owns credentials
->
Claude Cowork + skills
Delegates audits, scripts, docs, QA, and subagent tasks
->
HighLevel Agency API
Reads agency context, SaaS plans, locations, and workflow data
MCP bridge
How Claude Cowork connects to HighLevel: skill -> MCP server -> HighLevel API.
A skill is the instruction layer. MCP is the tool bridge. HighLevel is the system of record. The clean setup is to give Claude a HighLevel skill that explains the job, then expose a limited MCP server that can make approved HighLevel API calls with scoped credentials.
Step 1
Upgrade or confirm Pro access
Confirm your HighLevel account has the Agency Pro / SaaS Pro API access needed for agency-level tokens, OAuth, SaaS Mode, and sub-account workflows.
Step 2
Create the HighLevel MCP server
Build a small MCP server that exposes safe tools like list_locations, get_saas_plans, audit_pipeline, or review_workflows. The MCP server owns the HighLevel API calls.
Step 3
Connect Claude or Cowork to MCP
Point Claude Code, Claude Desktop, or a Cowork-style workspace at the MCP server so Claude can call only the tools you expose.
Step 4
Layer skills on top
Use SKILL.md templates to tell Claude when to use each HighLevel tool, what to inspect first, and when to ask for human approval before changes.
Starter MCP server
HighLevel agency API bridge
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";
const HIGHLEVEL_API_BASE = "https://services.leadconnectorhq.com";
const HIGHLEVEL_TOKEN = process.env.HIGHLEVEL_API_TOKEN;
const HIGHLEVEL_VERSION = "2021-07-28";
if (!HIGHLEVEL_TOKEN) {
throw new Error("Missing HIGHLEVEL_API_TOKEN");
}
async function highLevelFetch(path, init = {}) {
const response = await fetch(`${HIGHLEVEL_API_BASE}${path}`, {
...init,
headers: {
Authorization: `Bearer ${HIGHLEVEL_TOKEN}`,
Version: HIGHLEVEL_VERSION,
"Content-Type": "application/json",
...(init.headers || {})
}
});
if (!response.ok) {
const body = await response.text();
throw new Error(`HighLevel API error ${response.status}: ${body}`);
}
return response.json();
}
const server = new McpServer({
name: "highlevel-agency-api",
version: "0.1.0"
});
server.tool(
"list_locations",
"List HighLevel locations/sub-accounts available to the authorized agency token.",
{
companyId: z.string().describe("HighLevel agency/company ID")
},
async ({ companyId }) => {
const data = await highLevelFetch(`/locations/search?companyId=${encodeURIComponent(companyId)}`);
return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
}
);
server.tool(
"get_location_opportunities",
"Read opportunities for one location. Use for audits and QA, not destructive changes.",
{
locationId: z.string(),
pipelineId: z.string().optional()
},
async ({ locationId, pipelineId }) => {
const params = new URLSearchParams({ location_id: locationId });
if (pipelineId) params.set("pipeline_id", pipelineId);
const data = await highLevelFetch(`/opportunities/search?${params.toString()}`);
return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
}
);
// Add write tools later, behind explicit human approval and audit logging.
const transport = new StdioServerTransport();
await server.connect(transport);Claude MCP config
After compiling the MCP server, connect it to Claude with an MCP config like this. Use a secret manager for production credentials.
{
"mcpServers": {
"highlevel-agency-api": {
"command": "node",
"args": ["./dist/highlevel-mcp-server.js"],
"env": {
"HIGHLEVEL_API_TOKEN": "paste-your-token-or-use-a-secret-manager"
}
}
}
}Important safety note
Start with read-only tools. Let Claude inspect locations, opportunities, SaaS plans, and workflow metadata first. Add write tools only after you have explicit approval prompts, audit logging, scoped OAuth, and rollback procedures.
Useful docs
Copy-paste skill templates
Start with a skill, then connect the MCP/API tool underneath it.
Claude skills are reusable instructions. MCP is the connection layer that lets Claude reach approved tools or data sources. The simple build path is: create the skill, paste the template into `SKILL.md`, connect or build a HighLevel MCP/API tool, then ask Claude to use the skill before making API calls.
Step 1
Create `.claude/skills/highlevel-agency-control/SKILL.md`.
Step 2
Paste one of the templates below.
Step 3
Connect the HighLevel MCP/API tool with scoped credentials.
Step 4
Tell Claude: use the skill, read first, propose changes, wait for approval.
Clickable skill template
HighLevel Agency Control Skill
Agency owners who want Claude to reason across sub-accounts before calling tools or APIs.
---
name: highlevel-agency-control
description: Use when auditing or operating multiple HighLevel sub-accounts through agency-level API access, MCP tools, or approved scripts.
---
# HighLevel Agency Control
Use this skill when the user asks Claude to inspect, compare, or manage multiple HighLevel locations or SaaS sub-accounts.
## Rules
- Read before write. Never modify HighLevel data until the user approves the proposed action.
- Confirm which agency, location, and environment are in scope.
- Identify the API endpoint, OAuth scope, credential source, and rate-limit risk before any call.
- Summarize findings by account, risk, recommended action, and owner.
- For destructive changes, create a rollback note and wait for explicit approval.
## Output
Return a table with Account, Finding, API Evidence, Risk, Recommended Next Step, and Approval Needed.Clickable skill template
HighLevel SaaS Plan Auditor Skill
Agencies using SaaS Mode who need Claude to inspect plan assignment, subscription state, or upgrade opportunities.
---
name: highlevel-saas-plan-auditor
description: Use when reviewing HighLevel SaaS plans, subscription status, SaaS Configurator data, or account upgrade opportunities.
---
# HighLevel SaaS Plan Auditor
Use this skill to help the agency understand which clients are on which SaaS plan and where plan setup, billing, or packaging needs attention.
## Workflow
1. Confirm the SaaS plans and accounts in scope.
2. Pull or request plan, subscription, and account data from approved HighLevel API/MCP tools.
3. Compare each account against the intended package rules.
4. Flag missing features, mismatched plans, inactive subscriptions, and upgrade candidates.
5. Produce a client-safe summary and an internal operations summary.
## Safety
- Do not change plan assignment or subscription state without explicit approval.
- Keep billing-impacting actions in a separate approval list.Clickable skill template
HighLevel Workflow Governor Skill
Agencies that want Claude to review automations before changes are made.
---
name: highlevel-workflow-governor
description: Use when reviewing HighLevel workflows, triggers, automation risks, naming conventions, and proposed workflow changes.
---
# HighLevel Workflow Governor
Use this skill before creating, editing, or debugging HighLevel workflows.
## Review Checklist
- What business process does the workflow support?
- What triggers it?
- What contacts, opportunities, calendars, pipelines, or messages can it affect?
- What duplicate-send, missed-send, or wrong-recipient risks exist?
- What test account or sandbox can verify it?
## Required Output
Return: workflow purpose, risk rating, affected objects, test plan, rollback plan, and approval prompt.Clickable skill template
HighLevel Pipeline QA Skill
Agencies that want Claude to review lead flow, stage hygiene, stuck opportunities, and missing CRM fields.
---
name: highlevel-pipeline-qa
description: Use when auditing HighLevel pipelines, opportunities, stages, lead follow-up, contact fields, or sales process hygiene.
---
# HighLevel Pipeline QA
Use this skill to inspect whether leads are moving cleanly through HighLevel pipelines.
## Audit Steps
1. Confirm which locations, pipelines, and date range are in scope.
2. Pull or request opportunities, contacts, stages, owners, and last activity data from approved tools.
3. Identify stuck opportunities, missing owners, stale leads, missing phone/email fields, and stage mismatches.
4. Separate operational issues from automation issues.
5. Recommend follow-up, field cleanup, automation fixes, or pipeline redesign.
## Output
Return a table with Location, Pipeline, Issue, Evidence, Revenue Risk, and Recommended Action.Clickable skill template
HighLevel Agency Dashboard Skill
Agency owners who want Claude to design API-backed dashboards, operating reports, and weekly account reviews.
---
name: highlevel-agency-dashboard
description: Use when designing HighLevel API-backed dashboards, agency reports, SaaS account reviews, or client operating scorecards.
---
# HighLevel Agency Dashboard
Use this skill to turn HighLevel API data into an agency operating dashboard or report plan.
## Dashboard Planning
- Confirm the audience: agency owner, account manager, client, or implementation team.
- Define the decisions the dashboard should support.
- Identify required HighLevel objects: locations, contacts, opportunities, calendars, workflows, SaaS plans, or subscriptions.
- Map each metric to an API source, refresh cadence, owner, and alert threshold.
- Flag metrics that require Agency Pro / Advanced API access.
## Output
Return dashboard sections, metrics, API objects, refresh cadence, risk notes, and next build steps.Plan reality
Standard plans are fine for basic API work. Pro is the agency API lane.
| Capability | Starter / Unlimited | Agency Pro / SaaS Pro |
|---|---|---|
| API access level | Basic API access | Advanced API access |
| Agency API keys / agency-level tokens | Location-level access only for lower plans | Agency-level access available |
| OAuth 2.0 advanced API | Limited compared with Pro | Available for advanced API access |
| SaaS Mode | Not included on Starter or Unlimited | Included for agencies selling SaaS-style offers |
| Claude skills plus HighLevel API strategy | Useful for local documentation and single-location workflows | Better fit for agency-wide, multi-client, SaaS, and internal tooling workflows |
Always verify current plan features, API scopes, rate limits, and endpoint availability in HighLevel's official documentation before building production automations.
API use cases
Agency API access gives Claude more useful things to inspect.
These are the practical workflows an agency owner usually wants when connecting Claude, skills, MCP tools, and HighLevel. The more the work crosses clients or SaaS accounts, the more Pro becomes the natural target.
| API use case | HighLevel API need | Claude skill | Agency outcome |
|---|---|---|---|
| Sub-account oversight | Locations, SaaS sub-accounts, account metadata, and agency-level visibility | highlevel-agency-control | Ask Claude which client accounts need setup, QA, cleanup, or follow-up. |
| SaaS plan control | SaaS plans, subscription status, plan assignment, and SaaS Configurator endpoints | highlevel-saas-plan-auditor | Let Claude produce a client-by-client SaaS plan report and action list. |
| Pipeline QA | Pipelines, opportunities, stages, contact records, and attribution context | highlevel-pipeline-qa | Find stuck opportunities, missing fields, broken handoffs, or poor stage hygiene. |
| Workflow governance | Workflow inventory, triggers, owners, naming conventions, and risk review | highlevel-workflow-governor | Create a safer change-control process before Claude suggests edits or scripts. |
| Internal reporting | Agency data, location data, SaaS data, calendars, opportunities, and activity exports | highlevel-agency-dashboard | Use Claude to draft report logic, dashboard specs, and API-backed operating reviews. |
Claude skills approach
Build a HighLevel operating skill, not a loose prompt.
The conversion angle is simple: if your agency wants Claude to help with HighLevel beyond generic advice, it needs structured instructions and real API access. Pro gives agencies the better foundation because HighLevel documents Advanced API access for agency-level operations.
Try HighLevel ProResource 1
Create a HighLevel API skill that stores endpoint rules, auth steps, scopes, rate limits, and safety checks.
Resource 2
Use Claude Code for version-controlled scripts, API examples, QA checklists, and docs for your agency operating system.
Resource 3
Use Claude Cowork-style workflows for longer-running audits, documentation, and handoff tasks when your connectors, skills, and files are available.
Resource 4
Keep destructive or state-changing API actions behind human review, logs, and scoped credentials.
Agency use cases
What Claude can help your agency do once the API foundation is in place
Ask Claude to audit account structure
Use a skill-backed workflow to inspect contacts, opportunities, calendars, pipelines, or SaaS plan data that the HighLevel API exposes, then produce an agency-readable action list.
Generate safer API scripts
Claude Code can help draft repeatable scripts for allowed endpoints, but the agency still needs the right HighLevel plan, credentials, scopes, and review process.
Create repeatable client onboarding workflows
A skill can document how your agency provisions sub-accounts, maps SaaS plans, checks subscriptions, and hands off implementation tasks.
Build dashboards and internal admin tools
Advanced API access makes it more realistic to pull agency or SaaS data into custom dashboards, QA checks, reporting systems, and operational copilots.
Official HighLevel resources
Verify the API details before you build.
These HighLevel resource links include the HiVergent AI affiliate referral parameter where possible. Use them to confirm current API access, Pro plan details, SaaS Configurator endpoints, scopes, and documentation changes.
API docs
HighLevel API Documentation
Official overview of HighLevel API access, versioned docs, OAuth, agency-level tokens, and rate limits.
Pro plan
Agency Pro Upgrade Guide
Official HighLevel support article covering Agency Pro, SaaS Mode, Advanced API Access, white-labeling, rebilling, and reporting.
SaaS API
SaaS Configurator API Endpoints
Official resource for SaaS Configurator public API use cases like plan retrieval, subscriptions, bulk enablement, and SaaS sub-account visibility.
Reference
Developer Marketplace Docs
The main HighLevel developer documentation hub for API endpoint references, schemas, and examples.
FAQ
HighLevel Pro, Claude skills, and agency API questions
Can I upgrade from an existing HighLevel agency, basic, Starter, or Unlimited plan?
Yes. Existing HighLevel users can review the official Pro upgrade path and confirm current upgrade options inside HighLevel. If your goal is Claude Cowork, Claude Code, MCP tools, or agency-level API workflows across sub-accounts, Agency Pro / SaaS Pro is the plan to evaluate because HighLevel documents Advanced API access and agency-level token support on Pro.
Does it cost extra to use HiVergent AI resources or skill templates?
No. The resources, explanation, and copy-paste Claude skill templates on this page are free to use. If the page helps you decide to upgrade, using the HiVergent AI HighLevel Pro link is appreciated and may support our work at no additional cost to you.
Why is HighLevel Agency Pro important for Claude skills and API workflows?
HighLevel documents Basic API access for Starter and Unlimited plans, while Agency Pro provides Advanced API access, including OAuth and agency-level tokens. For agency-wide Claude Code or Claude Cowork workflows, Pro is the better fit because the automation often needs agency-level context rather than only one location.
Can Claude Code or Claude Cowork control HighLevel directly?
Claude can help operate HighLevel through skills, scripts, connectors, MCP tools, or API workflows when you provide the right credentials and guardrails. The practical limit is what the official HighLevel API exposes, your plan level, your OAuth scopes, and your safety controls.
How do you bridge Claude Cowork or Claude Code to HighLevel?
The practical bridge is an MCP server. The MCP server exposes approved tools to Claude, such as listing locations, reading opportunities, auditing pipelines, or checking SaaS plan data. The MCP server then calls the HighLevel API with scoped credentials. Claude skills sit above the MCP tools and tell Claude when to use them, how to interpret results, and when to request approval.
Do I need Agency Pro if I only manage one sub-account?
Not always. If you only need basic location-level API work, a lower plan may be enough. Agency Pro becomes more relevant when you need advanced API access, SaaS Mode, agency-level tokens, multi-client operations, white-label SaaS packaging, rebilling, or custom agency tools.
Is this page affiliated with HighLevel?
Yes. HiVergent AI may receive compensation if you use the HighLevel Pro link on this page. HighLevel owns the platform, plan pricing, API access rules, and documentation.
Affiliate disclosure
This page contains affiliate links. If you click a HighLevel link on this page and sign up, HiVergent AI may receive compensation at no additional cost to you. HighLevel owns and operates the platform, pricing, trial terms, plan features, API documentation, SaaS Mode, and Agency Pro access rules.
This page is educational and conversion-focused. It does not guarantee that a specific endpoint, scope, or integration will be available for your use case. Review HighLevel's official documentation and test with appropriate credentials before building production automations.
Start the HighLevel Pro trial