App Marketplace

When connecting Claude (Anthropic) to the HighLevel MCP server (mcp/anthropic/v2), calls fail with the error "NOT_ENABLED_FOR_LOCATION" for my sub-account. Request: Allow agency owners to enable MCP access per location directly from the agency settings, without contacting support. Add a clear toggle "Enable MCP / AI connectors" in Sub-account > Settings > Integrations. Show which scopes are granted (contacts, conversations, calendars, opportunities, workflows). Use case: we manage a Swiss service business (EcoSolutions Suisse) and want Claude to read/update contacts, opportunities and calendars, and trigger workflows. Many agencies need the same. Thank you!

Requesting an update to the Claude-to-GoHighLevel (GHL) MCP integration to allow multiple Claude users to connect to and work with the same GHL sub-account. Currently, it appears that once a Claude user connects to a GHL sub-account through the MCP, another Claude/GHL user cannot connect to that same sub-account. This creates a limitation for teams where multiple users need to use Claude with the same GHL account. For example, if User A connects their Claude account to a specific GHL sub-account, User B should also be able to authenticate their own Claude account and connect to that same GHL sub-account, rather than being required to connect to a different sub-account. Requested Change Please update the MCP authentication/connection system so that: Multiple Claude users can connect their individual Claude accounts to the same GHL sub-account. Each user can authenticate independently using their own GHL credentials/permissions. Users can access the same GHL sub-account through their own Claude connection, subject to their existing GHL permissions. Connecting one Claude user to a sub-account does not prevent additional authorized users from connecting to that same sub-account. This would make the integration much more practical for teams where multiple people need to work with the same GHL location/sub-account using their own Claude accounts.

The current endpoint (/marketplace/billing/charges/has-funds) only returns a boolean for whether a wallet has any funds — it doesn't check against a specific charge amount. This breaks pre-flight cost checks for marketplace apps that incur variable, usage-based costs before billing the end user. For example, our app enriches contacts with email and phone data. If a user requests enrichment for 50 contacts, we incur a cost from our enrichment provider for every successful (positive) result — we only know the actual charge amount after the API call completes, since we're billed per successful retrieval, not per request. That means we can't charge the exact final cost to the wallet ahead of time. What we can do is calculate the maximum possible charge upfront (e.g. 50 contacts × per-contact rate, assuming a 100% success rate) and confirm the wallet can cover that worst-case amount before running the job — otherwise we risk incurring costs we can't recover from the end user. Requested change: Add a cost (or amount) query parameter to the endpoint so it checks whether the wallet balance can cover that specific charge, e.g.: GET /marketplace/billing/charges/has-funds?cost=6.35 Response: same boolean as today (true/false), but evaluated against the given cost rather than just checking for a non-zero balance. This lets apps pass in a worst-case/estimated cost and confirm funds are sufficient before incurring their own upstream costs on batch operations.

"Is there any way to create SMS preview links in GHL? Like if we link a video in a text, it would appear as a preview image that'll take you to the video when clicked/tapped. Is there a way to do this in GHL either natively or through a 3rd party service?"

I would love to see this app integrated into GHL. So many fitness based businesses use this and look for it in any CRM/ Booking Software.

The Problem GoHighLevel allows developers to sell apps through its App Marketplace, but there should also be a way to sell reusable AI agent skills. As Ask AI, Managed Agents, and other AI products expand, developers and agencies should be able to monetize specialized AI capabilities without building entire applications. If developers can sell apps, why shouldn't they be able to sell AI agent skills? Proposed Solution: AI Skills Marketplace Allow developers and agencies to create, publish, distribute, and sell AI skills directly through the existing GoHighLevel App Marketplace. Customers should be able to purchase a skill, install it into their centralized Skills Hub, and assign it to compatible AI agents. Publish Skills as Marketplace Products Developers should be able to create marketplace listings containing: Skill name, description, and category. Supported agents (Ask AI, Managed Agents, etc.). Screenshots, demonstrations, and documentation. Required integrations and permissions. Pricing, ratings, and reviews. Version history and updates. Skills could include sales prospecting, SEO, customer support, reporting, content creation, and industry-specific workflows. Flexible Monetization Support multiple pricing models: Free skills. One-time purchases. Monthly and annual subscriptions. Usage-based pricing. Freemium models. Skill bundles. Agency-wide and enterprise licensing. GoHighLevel could generate additional revenue through marketplace transaction fees. One-Click Installation The installation process should be simple: Browse AI skills in the App Marketplace. Purchase or subscribe to a skill. Install it into the centralized Skills Hub. Assign it to Ask AI, Managed Agents, or other compatible agents. Start using it immediately. No manual copying, pasting, or complicated configuration. Agency Distribution and Reselling Agencies should be able to purchase skills and distribute them across multiple sub-accounts. Support: Single-location licenses. Multi-location and agency-wide licenses. White-label distribution. Reseller pricing. Recurring revenue opportunities. For example, an agency could purchase a Customer Support Skill and deploy it across 100 client accounts. Protect Developers' Intellectual Property Developers should have control over how their skills are distributed. Support: Open Skills: Customers can view and customize instructions. Protected Skills: Customers can use skills without viewing proprietary instructions. Licensed Skills: Access depends on an active subscription or license. For stronger protection, developers could host proprietary logic externally rather than distributing the complete implementation. Updates, Analytics, and Security Marketplace skills should include: Automatic updates and version control. Rollback to previous versions. Installation and revenue analytics. Subscription and license management. Customer feedback and reviews. Security checks and marketplace approval. Permission controls to prevent unauthorized CRM access. AI-Powered Skill Creation and Publishing Combine this with the proposed AI Skill Builder. A developer should be able to prompt an agent: "Create an advanced SEO skill for local businesses, package it for the marketplace, and prepare it for sale at $29/month." The AI should generate the skill, documentation, marketplace listing, and pricing configuration, then prepare it for review and publication. Why This Matters For Developers: Monetize expertise without building full applications. Generate recurring revenue. Reach GoHighLevel's existing customers. For Agencies: Purchase ready-made AI capabilities. Deploy skills across multiple clients. Build and sell proprietary skills. For GoHighLevel: Create an entirely new marketplace revenue stream. Expand the developer ecosystem. Increase adoption of Ask AI and Managed Agents. Encourage third-party innovation. Expected Outcome The App Marketplace would become a platform for selling both traditional software applications and reusable AI capabilities. Combined with a centralized Skills Hub, developers could create a skill once, sell it to thousands of customers, and distribute updates centrally. The vision: Build a skill once, publish it to the marketplace, and earn revenue as GoHighLevel users purchase and deploy it.

The Problem HighLevel empowers agencies and SaaSpreneurs to build software businesses across virtually every industry. However, we're still forced to use external hosting providers like AWS, Google Cloud, Azure, DigitalOcean, Hetzner, and Hostinger to host our customers' software. Our customers use countless self-hosted applications, open-source platforms, databases, and enterprise systems. We're already paying other companies to host these solutions. Why can't we pay HighLevel instead and manage everything in one place? The Market Opportunity Cloud hosting is a massive industry. According to Synergy Research Group, global cloud infrastructure services generated approximately $419 billion in revenue in 2025 . HighLevel already serves an enormous ecosystem of agencies and SaaS businesses. Offering cloud hosting would allow HighLevel to capture infrastructure spending that currently goes to third-party providers. This could become a significant new recurring revenue stream while making HighLevel a much more complete SaaS platform. Proposed Solution Introduce HighLevel Cloud Hosting , allowing agencies, SaaSpreneurs, developers, and their customers to deploy, host, and manage virtually any compatible software directly through HighLevel. Think AWS, Google Cloud, DigitalOcean, or Hostinger, but integrated into HighLevel . This should go beyond websites and Marketplace apps. We want to host entire enterprise applications, databases, custom software, and third-party platforms. Examples Across Industries Education Moodle, Canvas LMS (open-source), Open edX, Chamilo, OpenSIS, Gibbon. Learning management, student information, and school administration systems. Healthcare OpenEMR, OpenMRS, GNU Health, Orthanc, Bahmni. Electronic medical records, hospital management, and medical imaging systems. Legal Services Nextcloud, Paperless-ngx, Mayan EDMS, OpenProject. Document management, case coordination, and client portals. Manufacturing ERPNext, Odoo Community, Dolibarr, ThingsBoard. Manufacturing ERP, inventory, production, procurement, and industrial IoT. Retail & E-Commerce WooCommerce, Magento Open Source, PrestaShop, Medusa, Saleor. Online stores, commerce backends, and inventory systems. Hospitality QloApps, HotelDruid, TastyIgniter. Hotel management, reservations, and restaurant operations. Finance & Accounting Akaunting, ERPNext, Invoice Ninja, Firefly III. Accounting, invoicing, and financial management. Media & Entertainment PeerTube, Jellyfin, MediaCMS, Immich. Video hosting, media servers, and digital asset management. Technology & General Business GitLab, n8n, Appsmith, Budibase, Supabase, Directus, Strapi, Mattermost. Developer platforms, automation, databases, collaboration, and internal applications. These are only examples. The goal is to host virtually any legally permitted, technically compatible self-hosted application , whether open-source, commercially licensed, or custom-built. Key Features Cloud Servers & VPS: Provision virtual machines, dedicated compute resources, and scalable servers. One-Click App Deployment: Install popular self-hosted software from a catalog. Docker & Container Hosting: Deploy Docker images, Docker Compose stacks, and containerized applications. Managed Databases: PostgreSQL, MySQL, MongoDB, Redis, and more. Web & App Hosting: Host websites, enterprise software, APIs, and custom applications. Cloud Storage: File storage, object storage, media hosting, and backups. Domains & SSL: Custom domains, DNS management, and automatic HTTPS. Server Management: CPU, RAM, disk, networking, logs, monitoring, and resource scaling. Security & Backups: Firewalls, access controls, automated backups, and disaster recovery. Multi-Tenant Hosting: Separate hosting environments for different customers and subaccounts. White-Label Hosting: Allow SaaSpreneurs to resell hosting under their own brands. Hosting APIs & Workflows: Provision and manage infrastructure through APIs and HighLevel automations. Flexible Scaling: Support small deployments through large production workloads. Centralized Billing: Pay HighLevel directly for hosting, compute, storage, databases, and bandwidth. Regulated workloads should be supported with appropriate security and compliance capabilities. How It Would Work For Agencies: Open HighLevel → Cloud Hosting → Choose an application or create a server → Select resources → Deploy → Connect the customer's domain → Manage everything within HighLevel. For Customers: Purchase hosting through their SaaS provider → Access their hosted software → Scale resources as needed. For Developers: Deploy applications, databases, containers, and backend services directly through HighLevel. We're Willing to Pay for This! We're not asking HighLevel to provide free hosting. We're already spending money with other cloud providers, and we'd much rather spend that money directly with HighLevel. Potential pricing models include: Monthly VPS and dedicated server subscriptions. Pay-as-you-go compute, bandwidth, and storage. Managed database plans. Premium application hosting. Enterprise infrastructure packages. Wholesale hosting pricing for SaaSpreneurs and agencies. Agencies could also resell hosting to their customers as part of their SaaS subscriptions, creating additional revenue opportunities for both agencies and HighLevel. Why This Makes Sense HighLevel already helps businesses manage CRM, marketing, sales, automation, websites, and SaaS subscriptions. Cloud hosting would extend HighLevel into the infrastructure layer that powers those businesses. HighLevel wouldn't even need to build physical data centers initially. It could partner with existing cloud providers while offering its own hosting interface, provisioning, management, billing, and support. This could be introduced progressively, starting with managed VPS hosting, Docker deployments, databases, and one-click applications. Expected Outcome Significant new recurring infrastructure revenue. Stronger agency and customer retention. Reduced dependency on third-party hosting providers. More opportunities for SaaSpreneurs to monetize hosting. Greater appeal to enterprise and industry-specific customers. A more complete platform for software, automation, and infrastructure. Please consider creating HighLevel Cloud Hosting. We want to host Moodle, Canvas, Open edX, ERPNext, OpenEMR, WordPress VIP, n8n, custom applications, databases, and thousands of other platforms directly through HighLevel. We want to provision as many hosting environments as our businesses require, paying for the resources we consume. We're already paying AWS, Google Cloud, DigitalOcean, Hostinger, and others. We'd rather pay HighLevel. HighLevel doesn't need to reinvent cloud computing. It just needs to make cloud hosting available within its ecosystem. HighLevel shouldn't just power our businesses. It should host the software that runs them.

The Problem HighLevel allows developers to create and publish Marketplace apps, but we still need external platforms like AWS, Google Cloud, Heroku, Firebase, Supabase, or Vercel to host our applications, databases, and backend infrastructure. This forces developers to manage multiple platforms, integrations, subscriptions, and billing systems. We're already building applications for HighLevel. Why can't we host and run those applications directly through HighLevel as well? Proposed Solution Introduce a full-stack cloud development and hosting platform within HighLevel's developer ecosystem, similar to Salesforce's Heroku, Google Cloud, or Firebase . Allow developers to build, deploy, host, and scale their Marketplace applications directly through HighLevel. Key Features Cloud Servers & Hosting: Virtual machines, container hosting, managed application hosting, and serverless functions. Managed Databases: SQL and NoSQL databases with backups, scaling, and management tools. Backend Infrastructure: API hosting, background jobs, scheduled tasks, webhooks, queues, and backend runtimes. File & Media Storage: Cloud storage, file management, storage APIs, and CDN delivery. App Deployment: GitHub integration, CLI deployment, CI/CD pipelines, staging environments, and version control. Developer Tools: Application logs, debugging, monitoring, secrets management, and environment configuration. Native HighLevel Integration: Built-in connectivity to HighLevel APIs, OAuth, webhooks, and Marketplace applications. Desktop & Mobile Support: Host backends for Marketplace apps, web applications, and mobile applications. Scalable Infrastructure: Automatically scale resources based on application demand. Centralized Billing: Manage and pay for all hosting, databases, compute, and storage directly through HighLevel. We're Willing to Pay for This! This does not need to be a free feature. Developers and SaaSpreneurs are already paying third-party providers to host the applications we build for HighLevel. We would much rather spend that money directly with HighLevel. HighLevel could offer: Monthly hosting subscriptions. Pay-as-you-go compute and serverless pricing. Database and storage plans. Dedicated servers and enterprise infrastructure. Usage-based billing for bandwidth, processing, and other resources. This represents an additional recurring revenue opportunity for HighLevel while making its developer ecosystem significantly more valuable. Why This Matters Salesforce has Heroku. Google has Google Cloud and Firebase. Other software ecosystems provide developers with infrastructure to build and run applications. HighLevel already has a growing App Marketplace and developer ecosystem. Adding cloud hosting would allow developers to build and operate their applications without leaving the platform. HighLevel wouldn't even need to build its own physical cloud infrastructure initially. It could offer managed hosting powered by existing cloud providers while handling provisioning, integrations, management, and billing. Expected Outcome More developers building applications for HighLevel. Faster app development and deployment. Less reliance on external hosting providers. New recurring revenue from cloud services. A stronger Marketplace and SaaS Mode ecosystem. A unified platform for building, hosting, distributing, and scaling applications. Please consider building a HighLevel equivalent of Salesforce's Heroku. We want to build our applications on HighLevel, host our backends on HighLevel, manage our databases on HighLevel, and publish our applications through the HighLevel Marketplace. And most importantly, we're willing to pay HighLevel for these services instead of paying third-party hosting providers, since we are already building for Highlevel. Build on HighLevel. Host on HighLevel. Publish on HighLevel. Scale on HighLevel.