MCP server scopes not getting added.

[RM80]

I have now finally created the app that can conenct to the hubspot mcp server. now i am trying to add scopes but it is not letting me add. getting this error. any solution for this ?

[jpsanchez · Accepted solution]

Quick Answer: Marketing Campaign Scopes Are NOT Supported

The error you're experiencing is likely because you're trying to add marketing campaign scopes to an MCP app, which fundamentally doesn't support them. The HubSpot MCP server architecture is built exclusively on the CRM Search API, which has no access to Marketing Hub objects.​

Neither implementation supports marketing.campaigns scopes:

1. HubSpot Official MCP Server: Limited to CRM objects only with read-only access​

CalypsoCodex MCP Extended: Covers 106 CRM tools but no marketing campaign functionality​

Understanding Your Scope Error

When you receive an error adding scopes to your HubSpot MCP server app, it's typically due to one of these issues:

1. User-Level vs Account-Level Installation

The official HubSpot MCP server requires user-level OAuth installation, not the traditional account-wide app installation:​

 

json

{ "isUserLevel": true, "distribution": "marketplace" }

Critical difference:

• Traditional apps: Account-wide installation with admin-controlled scopes

• MCP apps: Each user installs individually, scopes governed by user permissions AND app configuration

  2. Scope Availability Restrictions

  Your error likely occurs because you're trying to add scopes that are:

  Not supported by MCP server:

  • ❌ marketing.campaigns.read

  • ❌ marketing.campaigns.write

  • ❌ marketing.campaigns.revenue.read

  • ❌ Any Marketing Hub, Service Hub, or CMS Hub scopes beyond CRM

    Supported CRM scopes (read-only):​

    • ✅ crm.objects.contacts.read

    • ✅ crm.objects.companies.read

    • ✅ crm.objects.deals.read

    • ✅ crm.objects.tickets.read

    • ✅ crm.objects.invoices.read

    • ✅ crm.objects.quotes.read

    • ✅ crm.objects.products.read

    • ✅ crm.objects.line_items.read

    • ✅ crm.objects.orders.read

    • ✅ crm.objects.carts.read

    • ✅ crm.objects.subscriptions.read

    • ✅ crm.objects.users.read

✅ crm.objects.owners.read

3. Developer Platform Version Requirement

Ensure your app is built on Developer Platform version 2025.2 or higher:​

 

json

{ "platformVersion": "2025.2" }

Apps on older platform versions cannot connect to the MCP server.

Solution Paths

Option A: Work Within MCP Limitations

If you need CRM data only, configure your app with supported scopes:

In your app-hsmeta.json:

 

json

{ "name": "Your MCP App", "platformVersion": "2025.2", "isUserLevel": true, "distribution": "marketplace", "requiredScopes": [ "oauth", "crm.objects.contacts.read", "crm.objects.companies.read", "crm.objects.deals.read" ], "optionalScopes": [ "crm.objects.tickets.read", "crm.objects.invoices.read" ] }

Scope configuration types:​

1. Required scopes: Must be authorized for installation

2. Conditionally required: Required only if present in install URL (enables tiered access)

3. Optional scopes: Not required; authorized if available

   Option B: Use CalypsoCodex MCP Extended

   If you need more CRM functionality (106 tools vs. HubSpot's basic coverage), use the community implementation:​

   What it provides:

   • 106 comprehensive CRM tools (vs. official server's limited toolset)

   • Full CRUD operations for invoices, line items, quotes

   • Batch operations and advanced search

   • Works with Private Apps or Connected Apps

   • Does NOT require user-level installation

     What it still lacks:

     • ❌ Marketing campaigns

     • ❌ Marketing emails

     • ❌ Service Hub objects

❌ CMS content

Installation:

 

bash

git clone https://github.com/calypsoCodex/hubspot-mcp-extended.git cd hubspot-mcp-extended cp .env.example .en...

 

 

Key Takeaway

The error you're experiencing is likely because you're trying to add marketing campaign scopes to an MCP app, which fundamentally doesn't support them. The HubSpot MCP server architecture is built exclusively on the CRM Search API, which has no access to Marketing Hub objects.​

Your three options:

1. Accept CRM-only limitation with official MCP

2. Use CalypsoCodex Extended for better CRM coverage

3. Build custom MCP server with Marketing API integration

   Documentation sources:

   • Official MCP Integration: https://developers.hubspot.com/docs/apps/developer-platform/build-apps/integrate-with-hubspot-mcp-se...

   • MCP Server Overview: https://developers.hubspot.com/mcp

   • OAuth Scopes Reference: https://developers.hubspot.com/docs/apps/developer-platform/build-apps/authentication/scopes

   • CalypsoCodex Extended: https://github.com/calypsoCodex/hubspot-mcp-extended

   •  

[suprdense · Accepted solution]

Perfect answer by @jpsanchez 

Just know that the MCP server is still in its nacscent stages and has limitations in terms of what scopes have been provisioned for it. 

You can find the scopes supported for the MCP server HERE.

[jpsanchez]

Thanks so much, @suprdense. If you’re interested, I put together a small MCP project you might like: CalypsoCodex Extended — an independent implementation with 106 CRM tools built from HubSpot’s official OpenAPI specs. Source-available (free for non‑commercial use). CalypsoCodex Extended: https://github.com/calypsoCodex/hubspot-mcp-extended

[jpsanchez · Accepted solution]

Quick Answer: Marketing Campaign Scopes Are NOT Supported

The error you're experiencing is likely because you're trying to add marketing campaign scopes to an MCP app, which fundamentally doesn't support them. The HubSpot MCP server architecture is built exclusively on the CRM Search API, which has no access to Marketing Hub objects.​

Neither implementation supports marketing.campaigns scopes:

1. HubSpot Official MCP Server: Limited to CRM objects only with read-only access​

CalypsoCodex MCP Extended: Covers 106 CRM tools but no marketing campaign functionality​

Understanding Your Scope Error

When you receive an error adding scopes to your HubSpot MCP server app, it's typically due to one of these issues:

1. User-Level vs Account-Level Installation

The official HubSpot MCP server requires user-level OAuth installation, not the traditional account-wide app installation:​

 

json

{ "isUserLevel": true, "distribution": "marketplace" }

Critical difference:

• Traditional apps: Account-wide installation with admin-controlled scopes

• MCP apps: Each user installs individually, scopes governed by user permissions AND app configuration

  2. Scope Availability Restrictions

  Your error likely occurs because you're trying to add scopes that are:

  Not supported by MCP server:

  • ❌ marketing.campaigns.read

  • ❌ marketing.campaigns.write

  • ❌ marketing.campaigns.revenue.read

  • ❌ Any Marketing Hub, Service Hub, or CMS Hub scopes beyond CRM

    Supported CRM scopes (read-only):​

    • ✅ crm.objects.contacts.read

    • ✅ crm.objects.companies.read

    • ✅ crm.objects.deals.read

    • ✅ crm.objects.tickets.read

    • ✅ crm.objects.invoices.read

    • ✅ crm.objects.quotes.read

    • ✅ crm.objects.products.read

    • ✅ crm.objects.line_items.read

    • ✅ crm.objects.orders.read

    • ✅ crm.objects.carts.read

    • ✅ crm.objects.subscriptions.read

    • ✅ crm.objects.users.read

✅ crm.objects.owners.read

3. Developer Platform Version Requirement

Ensure your app is built on Developer Platform version 2025.2 or higher:​

 

json

{ "platformVersion": "2025.2" }

Apps on older platform versions cannot connect to the MCP server.

Solution Paths

Option A: Work Within MCP Limitations

If you need CRM data only, configure your app with supported scopes:

In your app-hsmeta.json:

 

json

{ "name": "Your MCP App", "platformVersion": "2025.2", "isUserLevel": true, "distribution": "marketplace", "requiredScopes": [ "oauth", "crm.objects.contacts.read", "crm.objects.companies.read", "crm.objects.deals.read" ], "optionalScopes": [ "crm.objects.tickets.read", "crm.objects.invoices.read" ] }

Scope configuration types:​

1. Required scopes: Must be authorized for installation

2. Conditionally required: Required only if present in install URL (enables tiered access)

3. Optional scopes: Not required; authorized if available

   Option B: Use CalypsoCodex MCP Extended

   If you need more CRM functionality (106 tools vs. HubSpot's basic coverage), use the community implementation:​

   What it provides:

   • 106 comprehensive CRM tools (vs. official server's limited toolset)

   • Full CRUD operations for invoices, line items, quotes

   • Batch operations and advanced search

   • Works with Private Apps or Connected Apps

   • Does NOT require user-level installation

     What it still lacks:

     • ❌ Marketing campaigns

     • ❌ Marketing emails

     • ❌ Service Hub objects

❌ CMS content

Installation:

 

bash

git clone https://github.com/calypsoCodex/hubspot-mcp-extended.git cd hubspot-mcp-extended cp .env.example .en...

 

 

Key Takeaway

The error you're experiencing is likely because you're trying to add marketing campaign scopes to an MCP app, which fundamentally doesn't support them. The HubSpot MCP server architecture is built exclusively on the CRM Search API, which has no access to Marketing Hub objects.​

Your three options:

1. Accept CRM-only limitation with official MCP

2. Use CalypsoCodex Extended for better CRM coverage

3. Build custom MCP server with Marketing API integration

   Documentation sources:

   • Official MCP Integration: https://developers.hubspot.com/docs/apps/developer-platform/build-apps/integrate-with-hubspot-mcp-se...

   • MCP Server Overview: https://developers.hubspot.com/mcp

   • OAuth Scopes Reference: https://developers.hubspot.com/docs/apps/developer-platform/build-apps/authentication/scopes

   • CalypsoCodex Extended: https://github.com/calypsoCodex/hubspot-mcp-extended

   •  

[chighsmith]

Hi @RM80,

Thank you for posting to the Community!

I'd like to tag in some of our Top Contributors to see if they have experienced this error before -- Hi @jpsanchez and @suprdense Have either of you seen this before? If so, how did you resolve?

Thank you!

Cassie, Community Manager