# HubSpot MCP server pricing: write public reviews back to the CRM

> HubSpot headless pricing for a Claude write-back of public reviews: 200 customers cost at most $0.90 a week in API fees; HubSpot writes are an example.

- Canonical page: [https://everyinfra.com/en/blog/hubspot-mcp-pricing](https://everyinfra.com/en/blog/hubspot-mcp-pricing?utm_medium=ai_doc&utm_campaign=page_md)
- Published: 2026-11-22T14:38:00+08:00 · Fact-checked: 2026-11-22T14:30:00+08:00

One Reddit job post appeared 7 times in our data for Zapier and 7 times again for Calendly. A freelancer posted the same text in 7 hiring communities, and the text names both products. Without a key per item ID, Claude would write the same text 7 times on each of two HubSpot company records, 14 times in total. We saw this on November 22, 2026, when we pulled public posts and reviews for three sample CRM accounts: Calendly, Zapier and Typeform.

Each account took three EveryInfra calls: `linkedin/company_posts`, `trustpilot/reviews` and `reddit/search`. Each account cost $0.0045 and returned 81,122 to 101,389 bytes. The write-back goes through the HubSpot MCP server. On November 17, 2026, HubSpot published how it prices this kind of work ([HubSpot: HubSpot is headless. Here's how we'll price it](https://www.hubspot.com/company-news/pricing-headless)). Everyday connector use in Claude is part of the seat. Your own agent on the APIs uses the API capacity of your plan, and it does not use HubSpot Credits. A managed agent environment, which HubSpot is still building, will run on Credits.

For 200 accounts per week, our numbers give 600 calls and at most $0.90 in EveryInfra fees. On the HubSpot side, a batch API script needs about 6 requests per week. That is 0.0024% of the Starter daily limit of 250,000 calls. The Claude connector needs 40 write rounds, because it writes at most 10 records per round. The pulls are real calls. The HubSpot writes and their dedup logic are configuration examples built from HubSpot's public docs; we did not run them on a real HubSpot account.

> **Key points**
>
> - HubSpot's headless pricing (November 17, 2026) has three routes: connector use in Claude or ChatGPT comes with the seat; your own agents use API capacity, not Credits; the managed environment will use Credits at $0.010 each, with no published rate card yet.
> - Two HubSpot pages give different daily API limits for Professional: 625,000 in the developer docs and 650,000 in the product catalog. Both say 250,000 for Starter.
> - Three accounts, three calls each, cost $0.0045 per account and returned about 20,000 to 25,000 tokens. For 200 accounts per week, the maximum is $0.90, or $46.80 per year. Empty results and failures are free.
> - The same Reddit post appeared 7 times under two accounts. In LinkedIn company feeds, 7 of 20 and 12 of 20 posts were by other authors. Use a global key of platform plus item ID, and merge in the script before the weekly summary.
> - On EveryInfra, we tested it: an `Idempotency-Key` replay returns the first response with no new charge, and a changed request gets a 409. The HubSpot CRM API has no request idempotency key. Our documented design stores the weekly note ID and week on the company, so a rerun edits the same note; we did not run it on HubSpot.

![Illustration: on the left, a conveyor belt carries small cards with speech bubbles and stars, and some stacks are exact copies; in the middle, a sorting machine reads a brass tag on each card, drops copies into a side bin and lets one of each pass; on the right, a wooden card cabinet has one drawer open for the new card; a return chute loops back to the belt, and its small gate is closed.](https://everyinfra.com/articles/hubspot-mcp-pricing/img-explain.webp?utm_medium=ai_doc&utm_campaign=page_md)

Pull, deduplicate, write back. A resent card stops at the gate, so each item is filed once.

## HubSpot headless pricing: the three routes

HubSpot uses the word headless for work done in HubSpot from another AI tool, without the HubSpot screens. The pricing post opens with three sentences ([HubSpot](https://www.hubspot.com/company-news/pricing-headless)). Each seat includes enough headless access for everyday work from Claude or ChatGPT, at no added cost. Third-party agents can connect to the existing APIs, and that use counts toward the API capacity of the plan. Teams that want strong governance and purpose-built tools for their agents will pay for that use with HubSpot Credits.

| Route | What connects | How HubSpot charges | Write limits in public docs |
| --- | --- | --- | --- |
| Everyday connector use | HubSpot connectors for Claude, ChatGPT, Gemini and Microsoft Copilot; the HubSpot MCP server; the Agent CLI | Included with the seat; Credits will expand capacity for heavy users later | Claude connector: 10 records per bulk create or update; no delete; writes go to the audit log |
| Your own or purchased agents on the APIs | The existing CRM APIs, like any integration | Counts toward the daily API capacity of the plan; no Credits; more capacity can be bought | Private apps: 100 or 190 calls per 10 seconds; 250,000 to 1,000,000 calls per day |
| Managed agent environment (in development) | Purpose-built agent APIs with access control and action logs | Work at scale, such as record enrichment, uses Credits | No rate, name or launch date in the post |

The post has no prices. The Credits page and the catalog give them. One credit costs $0.010. You buy packs of 1,000 for $10 per month, or pay as you go in steps of 10 credits. See [HubSpot Credits](https://www.hubspot.com/products/artificial-intelligence/credits) and the [HubSpot catalog](https://legal.hubspot.com/hubspot-product-and-services-catalog).

Sales Hub Starter, Professional and Enterprise include 500, 3,000 and 5,000 credits per month. Unused credits do not roll over ([HubSpot: Sales Hub pricing](https://www.hubspot.com/pricing/sales)).

The post does not define "everyday" use. It also gives no rate for the managed environment. The IMPACT writer asks the same question with an example. A sales manager asks Claude about 100 deals each morning. Is that still everyday use?

### Where this job fits

The input is a list of 200 customer companies in HubSpot, with a domain and a LinkedIn page slug for each. The output is one "public activity this week" note per company, plus three company properties: low-review count, week of the last write, and the ID of this week's note. The data does not come from HubSpot. The posts and reviews are on LinkedIn, Trustpilot and Reddit, and EveryInfra collects them. HubSpot only stores the result.

The same job can use two of the three routes. If a person does it inside Claude, it is connector use, and it comes with the seat. If a weekly script does it with a service key, it is API use, and it counts toward the API capacity. Since 2026, service keys replace legacy private apps for this kind of integration.

You give each key object scopes, and it shares the limits of privately distributed apps. One account can have at most 100 apps, service keys and MCP connectors in total ([HubSpot developer docs: service keys](https://developers.hubspot.com/docs/apps/developer-platform/build-apps/authentication/account-service-keys); [Authentication overview](https://developers.hubspot.com/docs/apps/developer-platform/build-apps/authentication/overview)). The third route is not available yet.

The two routes differ in batch size and approval. The HubSpot help page for the Claude connector says that bulk create or update works on 10 records at a time. It also recommends that you set write tools to "Needs Approval", because "Always allow" can apply edits without a prompt ([HubSpot Knowledge Base: Claude connector](https://knowledge.hubspot.com/integrations/set-up-and-use-the-hubspot-connector-for-claude)). For 200 companies, that is 20 rounds of property updates and 20 rounds of notes, so 40 approvals.

The CRM batch endpoints take 100 inputs per call. The same writes are 2 property updates and 2 note writes (create or update), plus 2 search requests that filter companies by property ([HubSpot: Search the CRM](https://developers.hubspot.com/docs/api-reference/latest/crm/search-the-crm)). That is 6 requests per week.

![Horizontal bar chart, log scale, each step 10x: HubSpot daily API limits are 250,000 calls for Starter, 625,000 for Professional in the developer docs, 650,000 for Professional in the product catalog, and 1,000,000 for Enterprise. The last bar is this job: 6 calls per week for 200 customers, more than four orders of magnitude below the Starter daily limit.](https://everyinfra.com/articles/hubspot-mcp-pricing/fig-01-api-capacity-bar.en.light.svg?utm_medium=ai_doc&utm_campaign=page_md)

### Two HubSpot pages disagree on the Professional limit

The developer page "API usage guidelines and limits" lists daily limits for privately distributed apps ([HubSpot developer docs: usage guidelines](https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines)). Free and Starter get 250,000 calls per day. Professional gets 625,000. Enterprise gets 1,000,000.

The burst limit per 10 seconds is 100, 190 and 190, and it applies per app. The daily limit is shared by all apps in the account. With the API limit increase, the burst limit is 250 per 10 seconds, and each pack adds 1,000,000 calls per day. You can buy two packs at most.

The catalog page "Technical Limits" says 650,000 calls per day for Professional ([HubSpot catalog: Technical Limits](https://legal.hubspot.com/hubspot-product-and-services-catalog/technical-limits)). It lists 1,650,000 with one pack and 2,650,000 with two, at $500 per pack per month. Its table gives burst limits of 350, 600, 440 and 690 per 10 seconds after packs. A sentence above the same table says packs raise the limit to 250 per 10 seconds. We read both pages on November 22, 2026, and PPC Land's report also noted the burst-limit conflict.

For this job, the difference does not matter: 6 requests per week is more than four orders of magnitude below even the smallest daily limit. For capacity planning, use the number on your own "Development > Monitoring > API call usage" page. A 429 response includes a `policyName` that tells you which limit you hit.

| Tier | Per 10 seconds (each private app) | Per day (developer docs) | Per day (catalog) | Per day with one pack |
| --- | --- | --- | --- | --- |
| Free and Starter | 100 | 250,000 | 250,000 | 1,250,000 |
| Professional | 190 | 625,000 | 650,000 | 1,650,000 |
| Enterprise | 190 | 1,000,000 | 1,000,000 | 2,000,000 |
| Public OAuth app in the marketplace | 110 per installing account | — | — | — |

The developer docs add two rules that matter for agents. The daily limit resets at midnight in the time zone of the account. Error responses should stay under 5% of daily requests, and marketplace apps must stay under this line to get certified ([HubSpot developer docs: usage guidelines](https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines)). For a weekly script, the 5% error line is easier to hit than the volume limit. One wrong property name can fail a full batch.

## What the HubSpot MCP server is: URL, auth and write access

The HubSpot MCP server lives at `https://mcp.hubspot.com`. It became generally available to all accounts on April 13, 2026, and that release added write access ([HubSpot developer changelog](https://developers.hubspot.com/changelog/remote-hubspot-mcp-server-is-now-generally-available)). HubSpot's own connectors for Claude, ChatGPT, Gemini and Microsoft Copilot also run on this server ([HubSpot: Using the HubSpot MCP server](https://developers.hubspot.com/docs/build-with-ai/remote-mcp-server)).

Do not confuse it with the developer MCP server. That one runs on your machine with the HubSpot CLI. It helps you build apps and CMS content, and it does not read or write CRM records ([HubSpot: developer MCP server](https://developers.hubspot.com/docs/developer-tooling/local-development/mcp-server)). Searches for "hubspot mcp server" on GitHub or npm often lead to the developer server or to community projects.

OAuth is the only way in. The integration guide requires OAuth 2.1 with PKCE ([HubSpot integration guide, updated November 20, 2026](https://developers.hubspot.com/docs/apps/developer-platform/build-apps/integrate-with-the-remote-hubspot-mcp-server)). The [MCP specification](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization) uses the same method, with PKCE from [RFC 7636](https://datatracker.ietf.org/doc/html/rfc7636).

You create an MCP connector under "Development > MCP Connectors" in your HubSpot account. You get a client ID and a client secret, and you set a redirect URL. A HubSpot developer blog post from November 12, 2026 adds a detail. Some tools mark the client secret as optional, but this server requires it ([HubSpot developer blog](https://developers.hubspot.com/blog/connect-hubspots-mcp-server-with-any-ai-tool-securely)).

We sent one request without a token to `https://mcp.hubspot.com/` at 12:43 Singapore time on November 22, 2026. The server returned 401 and pointed to its protected resource metadata. In that metadata, `scopes_supported` is an empty list. The authorization server accepts only S256 for PKCE and expects `client_secret_post`. Its grant types include `authorization_code`, `refresh_token`, `client_credentials` and a JWT bearer grant. The docs explain only the authorization code flow, so this article uses only that flow.

Before you connect another MCP client, you can test the server with [MCP Inspector](https://github.com/modelcontextprotocol/inspector). It shows if the OAuth flow works and which tools you get. HubSpot opened self-service MCP connectors as a public beta on January 20, 2026 ([HubSpot changelog: Self-Service MCP Auth Apps](https://developers.hubspot.com/changelog/public-beta-self-service-mcp-auth-apps-for-the-hubspot-remote-mcp-server)). On August 28, 2025, the Claude connector got read access to more objects, such as quotes and invoices ([HubSpot changelog: Claude connector additional objects](https://developers.hubspot.com/changelog/claude-connector-additional-objects-and-admin-controls)).

![Terminal screenshot: at 12:43 on November 22, 2026, a POST to https://mcp.hubspot.com/ without a token returns HTTP 401, and the www-authenticate header points to the protected resource metadata. Below, the metadata shows an empty scopes_supported list, S256 as the only code challenge method, and client_secret_post as the token auth method. Teal boxes mark these lines.](https://everyinfra.com/articles/hubspot-mcp-pricing/img-hubspot-401.webp?utm_medium=ai_doc&utm_campaign=page_md)

Real 401 response and OAuth metadata from the HubSpot MCP server, 12:43 Singapore time on November 22, 2026. Cookies are removed. | source: live test https://mcp.hubspot.com/.well-known/oauth-authorization-server

You do not set scopes on the connector. The guide says that two things set the scopes. The first is the tools on the server at install time. The second is the permissions that the user grants. When HubSpot adds tools, users must reinstall to get the new scopes. Every action also follows the user's own HubSpot permissions.

If your account has sensitive data turned on, the MCP server blocks activity objects: calls, emails, meetings, notes and tasks. This rule applies only to the MCP server, not to the standard CRM APIs ([HubSpot changelog, April 13, 2026](https://developers.hubspot.com/changelog/remote-hubspot-mcp-server-is-now-generally-available)). Our job writes notes, which are activities. In such an account, only the API route works.

| Object | MCP server read | MCP server write | Claude connector write | Used here |
| --- | --- | --- | --- | --- |
| Companies | Yes | Create, edit | Create, edit, no delete | Three properties |
| Notes (activity) | Yes | Create, edit | Create, edit, no delete | One weekly summary per company |
| Properties | Yes | Create custom | Create, no edit | Three new properties |
| Social posts | Your connected accounts only | Drafts, schedules | Create, edit | Not used |

We do not use social posts. The social data in the HubSpot MCP server covers only the social accounts that you connect to HubSpot. It also covers your own posts and their results ([HubSpot integration guide](https://developers.hubspot.com/docs/apps/developer-platform/build-apps/integrate-with-the-remote-hubspot-mcp-server)). What a customer company posts on LinkedIn, or what users say about it on Trustpilot and Reddit, is not in HubSpot. You must collect it from the public web.

## Connect HubSpot MCP and EveryInfra MCP in Claude

There are two ways to set it up in Claude. In Claude on the web, desktop or mobile, use HubSpot's own connector. Go to Settings, then Connectors, then Browse. Search for HubSpot, click Connect, sign in, and choose permissions. You need a paid Claude plan: Pro, Max, Team or Enterprise. Other users must wait until a Super Admin approves the connector and its data access ([HubSpot: Claude connector](https://knowledge.hubspot.com/integrations/set-up-and-use-the-hubspot-connector-for-claude); [HubSpot: Manage access to apps](https://knowledge.hubspot.com/integrations/manage-access-to-apps)).

Add EveryInfra in Claude as a custom connector at `https://api.everyinfra.com/mcp` ([Claude Help Center: custom connectors](https://support.claude.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp); [EveryInfra MCP setup](/en/build/remote-mcp-setup)). Claude Pro costs $20 per month, or $17 per month on an annual plan ([Claude pricing, read November 22, 2026](https://claude.com/pricing)).

In Claude Code, add both servers with commands. HubSpot does not support dynamic client registration, so you use the connector credentials. With `--client-id` and `--client-secret`, Claude Code asks for the secret with masked input. Claude Code keeps the secret in the macOS keychain or in a credentials file.

The callback port comes from the redirect URL in the HubSpot connector. An example is `http://localhost:8080/callback` ([Claude Code MCP docs](https://code.claude.com/docs/en/mcp)). This is a configuration example. We did not run the HubSpot side on a real account.

```bash
# 1) HubSpot MCP server: first create a connector in HubSpot (Development > MCP Connectors)
#    with the redirect URL http://localhost:8080/callback
claude mcp add --transport http \
  --client-id "$HUBSPOT_MCP_CLIENT_ID" --client-secret --callback-port 8080 \
  hubspot https://mcp.hubspot.com/
# Then type /mcp in Claude Code and sign in to HubSpot in the browser

# 2) EveryInfra remote MCP: keep the key in an environment variable
export EVERYINFRA_API_KEY=...   # put it in your shell profile or a password manager, not in git
claude mcp add-json everyinfra \
  '{"type":"http","url":"https://api.everyinfra.com/mcp","headers":{"Authorization":"Bearer ${EVERYINFRA_API_KEY}"}}'
```

Claude Code expands `${EVERYINFRA_API_KEY}` when it connects. You can commit `.mcp.json` without the key. The docs warn about one trap. In the `url` and `headers` of a remote server, Claude's own credential variables, such as `ANTHROPIC_AUTH_TOKEN`, read as empty. This stops a project config from sending your Claude credentials to a server that it names. Your own variable names are not affected.

Set permissions per tool ([Claude Code docs: permissions](https://code.claude.com/docs/en/permissions)). Allow the HubSpot read tools, and set every HubSpot write tool to ask. On EveryInfra, `everyinfra_call_api` costs money, so you can also set it to ask. `everyinfra_list_capabilities` and `everyinfra_get_job` are free, so you can allow them.

Claude Code also has a timer for each remote MCP request, up to the first response byte. It uses the largest of 60 seconds, the tool timeout and `MCP_TIMEOUT` ([Claude Code docs: MCP](https://code.claude.com/docs/en/mcp)). Our 9 regular pulls for three accounts returned in 4.2 to 13.0 seconds, so they stayed inside this timer. For larger pulls, add `"mode":"async"` and read the job with the free `everyinfra_get_job` tool.

## Live test: public posts and reviews for three accounts

All three rounds used the EveryInfra REST API. The rounds ran at 12:43, from 12:45 to 12:50, and from 13:03 to 13:07, over 24 minutes in total. We sent 31 requests, and 18 were charged, for a total of $0.0196. The other 13 were 429 rate limits, a 422 parameter error, a 409 idempotency conflict, an idempotent replay and empty results, and none was charged.

| Response | Requests | Charged | Example |
| --- | --- | --- | --- |
| 200 with data | 18 | 18, $0.0196 in total | Three capabilities for three accounts, profiles, transcripts, the MCP call |
| 200, empty result | 2 | 0, hold refunded | Made-up Reddit keyword; wrong LinkedIn slug |
| 200, idempotent replay | 1 | 0 | Same `Idempotency-Key`, same body |
| 409 idempotency conflict | 1 | 0 | Same key, changed parameter |
| 422 invalid parameter | 1 | 0 | `date=last14days` |
| 429 rate limit | 8 | 0 | Shared test key, 10 calls per minute |

The key came only from an environment variable, and we kept every raw response. We read the catalog at 12:42 Singapore time on November 22, 2026: 106 platforms, 714 capabilities, 683 available. The three companies are public software companies. They stand in for "customer accounts in a CRM" and have no link to the HubSpot setup.

For each account we pulled three things. First, the latest 20 posts on the LinkedIn company page with [`linkedin/company_posts`](/en/linkedin-api/company_posts), at $0.002319 per call. Second, Trustpilot reviews from the last 30 days with [`trustpilot/reviews`](/en/trustpilot-api/reviews), at $0.001389 per call. Third, Reddit posts from the last month that match the brand name with [`reddit/search`](/en/reddit-api/search), at $0.000792 per call.

| Singapore time | Account | LinkedIn posts | Trustpilot, 30 days | Reddit posts | Bytes | Fee |
| --- | --- | --- | --- | --- | --- | --- |
| 12:43–12:44 | Calendly | 20, Aug 28 to Nov 18, 13 by the company | 26, five 1-star, 0 replies | 14, 1 with the brand in the title | 81,122 | $0.0045 |
| 12:45–12:49 | Zapier | 20, Nov 17 to Nov 21, 8 by the company | 9, all 1 or 2 stars, 0 replies | 25, 10 with the brand in the title | 90,841 | $0.0045 |
| 13:03–13:07 | Typeform | 20, Oct 9 to Nov 20, 9 by the company; the first slug matched a different company | 19, five 1-star, 10 with a company reply | 22, 0 with the brand in the title, 16 only link to a form | 101,389 | $0.0045 |

![Grouped bar chart of public items per account. Calendly: LinkedIn 20, Trustpilot 26, Reddit 14. Zapier: LinkedIn 20, Trustpilot 9, Reddit 25. Typeform: LinkedIn 20, Trustpilot 19, Reddit 22. Each account cost $0.0045.](https://everyinfra.com/articles/hubspot-mcp-pricing/fig-02-items-bar.en.light.svg?utm_medium=ai_doc&utm_campaign=page_md)

The first round had one request with a wrong value on purpose. At 12:44 Singapore time, we sent `date=last14days` to Trustpilot. The API returned 422 in 0.74 seconds. The error listed the 5 allowed values, and `did_you_mean` suggested `last7days` and `last30days`. The first line of `next_steps` said to change only `date` and that nothing was charged.

In the second round we hit the rate limit. This test key allows 10 calls per minute, and other tests used it at the same time. Between 12:45 and 12:50, 8 requests got a 429 in 0.12 to 0.17 seconds. Each had a `retry-after` header, and none was charged. The script waited 60 seconds and sent them again, and all of them succeeded.

### How many new items appear per account per week

The speed of new content sets the write-back schedule. Calendly's 20 LinkedIn posts span August 28 to November 18, and only 1 is from the last 7 days. Zapier's 20 posts all fall between November 17 and November 21, so a weekly pull of 20 misses posts. On Trustpilot, 11 of Calendly's 26 reviews in 30 days are from the last 7 days. For Zapier, 4 of 9 are.

So do not use one `limit` for all accounts. Set it from last week's count. If the new count equals the limit, raise the limit next time or pull every three days. `linkedin/company_posts` costs the same per call for 10 or 50 posts: $0.002319. For a busy poster like Zapier, ask for 50. The catalog notes that some requests return at most 20, so treat a count of 20 as "may have missed posts".

| Account | LinkedIn, last 7 days | LinkedIn, last 30 days | Trustpilot, last 7 days | Suggested LinkedIn `limit` |
| --- | --- | --- | --- | --- |
| Calendly | 1 of 20 | 7 of 20 | 11 of 26 | 20 |
| Zapier | 20 of 20 | 20 of 20 | 4 of 9 | 50 |
| Typeform | 7 of 20 | 16 of 20 | 6 of 19 | 20 |

LinkedIn company feeds need one more filter. For Calendly, 7 of 20 posts had another author. For Zapier, 12 of 20 did. These are posts by employees or partner companies that the company page reshares. Their `author_username` does not match the company slug, and `author_type` is often `profile`.

In the CRM, keep them apart. Put company posts under company news. Drop employee posts or store only the link, so an employee's view does not look like a company statement. Employee names are personal data, so the note says only "employee post" with the link.

### Trustpilot: no replies to low ratings

Calendly had 26 reviews in the last 30 days: 19 five-star and 5 one-star. 18 of the 26 were invited reviews (`verification_level: invited`). All 5 one-star reviews were organic. They describe a support case that took months and a hard-to-use upgrade. Others describe broken bookings after a time zone change in British Columbia, a core feature that was down with no answer, and a hard cancellation.

Zapier had only 9 reviews in 30 days, all 1 or 2 stars. They describe cancellation, no refund for unused months, and partner quality. Across 35 reviews for the two companies, the company replied to 0. Typeform is different: it replied to 10 of 19.

All replies are on reviews from November 13 or earlier, and the 6 reviews from the last 7 days have no reply yet. Two of those 6 are 1-star. A customer success team can use this before a renewal call: which issues the customer's users raise in public reviews, and whether the company has answered.

The Typeform data shows one more thing: company replies can come one or two weeks later. A review with no reply this week can have a reply next week. If you store the review ID in the script's local store, next week's pull updates the same row, and the next summary shows the reply. If you only look at new items, the record will always say "no reply". So key single items on platform plus item ID, not on account plus week.

### Reddit: one post under two accounts

`reddit/search` finds posts from the last month. A post matches when the title or community name has the keyword, or when the body has all the words. For Calendly, only 1 of 14 titles had "Calendly". It was a thread about open-source scheduling tools. For Zapier, 10 of 25 titles had "Zapier".

Both result sets had the same group of posts. A freelancer posted "[FOR HIRE] AI Workflow Automation (Zapier and Make.com)" in 7 job communities, and the body lists both Calendly and Zapier as skills. By item ID, the Calendly and Zapier results share 7 rows. By a hash of the title plus the first 400 characters of the body, Calendly's 14 rows have 8 distinct texts, and Zapier's 25 rows have 19.

![Bar chart of Reddit rows versus distinct texts: Calendly 14 rows and 8 distinct texts; Zapier 25 rows and 19 distinct texts; Typeform 22 rows and 19 distinct texts, and 16 rows only contain a typeform.com form link. Calendly and Zapier share 7 rows from one group of posts.](https://everyinfra.com/articles/hubspot-mcp-pricing/fig-04-dedupe-share.en.light.svg?utm_medium=ai_doc&utm_campaign=page_md)

If you dedupe by account plus post ID, each company record gets 7 entries, so 14 with the same text. If you dedupe by platform plus post ID across all accounts, the script keeps 7 items, each tagged with both accounts. The 7 are the same text in different communities. If you also merge by text hash, you get 1 item with 7 links.

Choose the level by purpose. For share-of-voice counts, 7 communities are 7 exposures. For an account record, 1 note is enough. You also need to decide if a job post has anything to do with the customer company. In most cases it does not, so drop it.

Typeform's Reddit results show a different kind of noise. Of 22 rows, 0 have "Typeform" in the title. 16 rows only contain a typeform.com link to a survey or sign-up form, such as a community survey, a job application or a beta sign-up. Only 6 rows mention the company by name.

Three are copies of one third-party list of companies that includes Typeform. One is a list of new connectors for an AI assistant. One compares form builders, and one says that the user replaced Typeform with another tool.

So add one more filter rule: drop posts where the brand name appears only inside a URL. Send third-party lists with no checkable source to the account owner, and do not record them as fact.

| Typeform Reddit rows | Count | What to do |
| --- | --- | --- |
| Only a typeform.com form link in the body | 16 | Drop |
| Third-party list of companies | 3 (one text) | Merge, send to the account owner, do not record as fact |
| New connector list of an AI assistant | 1 | Keep as a product note |
| Form builder comparison | 1 | Keep |
| User says they replaced Typeform | 1 | Keep, mark as churn signal |

### LinkedIn slugs: a company name can match another company

The first Typeform call went wrong. At 13:03 Singapore time, we sent `company: typeform` to `linkedin/company_posts`. The API returned 0 rows with `reason: empty_result_refunded`, and nothing was charged. At 13:05 we checked the slug with [`linkedin/company_profile`](/en/linkedin-api/company_profile) for $0.000556.

The slug belongs to a graphic design company in Dublin. It was founded in 1983, has 25 employees and 1,800 followers, and its website is typeform.ie. It has no link to the form builder.

A web search showed that the form builder uses the slug `typeform-`, with a hyphen at the end. At 13:07 we pulled again with that slug and got 20 posts.

This time the result was empty, and nothing was charged. If the other company had posts, the script would write its news into your customer record with no error. To prevent this, store the LinkedIn page URL as a company property, such as `ei_linkedin_slug`. Do not derive it from the company name.

Before the first pull, call `linkedin/company_profile` once and compare the returned `website` with the HubSpot `domain`. If they do not match, do not write, and flag the record for a person to check. At $0.000556 per call, this check costs $0.11 for 200 accounts. You do it once, and after that only for new accounts.

| Slug | Name on LinkedIn | Website | Employees | Posts returned | Cost |
| --- | --- | --- | --- | --- | --- |
| `typeform` | Typeform Design, Dublin | typeform.ie | 25 | 0 (empty, refunded) | $0 |
| `typeform-` | Typeform, the form builder | typeform.com | — | 20 | $0.002319 |

### Bytes per account before the write-back

Each account returned 81,122 to 101,389 bytes over three calls. At about 4 bytes per token, that is about 20,000 to 25,000 tokens. For 200 accounts, the raw data is more than 4 million tokens. One conversation cannot hold that, and it does not need to. The CRM needs only a short summary and a few links per account.

Do the pulling and filtering in a script: dedupe by ID, drop other authors, keep the last 7 days. Then give Claude only the filtered items for each account. That brings the context down to a few thousand tokens per account.

![Stacked bar chart of bytes per account for three calls. Calendly: LinkedIn 26,613, Trustpilot 23,288, Reddit 31,221, total 81,122. Zapier: 35,688, 13,429 and 41,724, total 90,841. Typeform: 31,376, 22,731 and 47,282, total 101,389. At about 4 bytes per token, each account is about 20,000 tokens.](https://everyinfra.com/articles/hubspot-mcp-pricing/fig-03-bytes-bar.en.light.svg?utm_medium=ai_doc&utm_campaign=page_md)

We also made one call through the remote MCP to confirm that the Claude route gets the same data. At 13:05:24 Singapore time, we sent a JSON-RPC `tools/call` request to `everyinfra_call_api` for Zapier's Trustpilot reviews from the last 7 days. It returned 4 reviews, all 1-star, and charged $0.001389. The price and the fields are the same as on REST.

This call took 74.6 seconds. The three REST calls to the same capability took 8.6 to 13.0 seconds. One sample does not prove that MCP is slower. But it is longer than the default 60-second first-byte timer in Claude Code, and this response came back as one JSON body. In Claude Code, set `MCP_TIMEOUT` to 120000 milliseconds. Or add `"mode":"async"` for review and post capabilities, and read the result with `everyinfra_get_job`.

| Path | Capability | Calls | Time per call | Charged per call |
| --- | --- | --- | --- | --- |
| REST `/api/v1/social` | `trustpilot/reviews` | 3 | 8.6 to 13.0 s | $0.001389 |
| Remote MCP `everyinfra_call_api` | `trustpilot/reviews` | 1 | 74.6 s | $0.001389 |
| Claude Code default first-byte timer | — | — | 60 s | — |

![Terminal screenshot: at 13:05:24 on November 22, 2026, a JSON-RPC tools/call request runs everyinfra_call_api with trustpilot reviews, zapier.com and last7days. At 13:06:39 the server returns HTTP 200 after 74.6 seconds, with count 4 and charged_usd 0.001389. Below are 4 one-star reviews with masked reviewer names. Teal boxes mark the time and billing lines.](https://everyinfra.com/articles/hubspot-mcp-pricing/img-mcp-roundtrip.webp?utm_medium=ai_doc&utm_campaign=page_md)

One real round trip through the EveryInfra remote MCP. Personal names are masked. | source: live test https://api.everyinfra.com/mcp

## Which route to use

Choose by volume. Do you watch 10 to 20 key accounts and read each item first? Then use the Claude connector. That is about 10 to 20 approvals per week, and the seat covers it. Do you write 200 accounts every week and need safe reruns? Then use a script on the API with a named service key. That is 6 requests per week, with no added HubSpot cost. If your account has sensitive data turned on, the MCP server blocks notes, so only the API route works.

When the managed environment launches, check three things before you move. First, how many Credits does each write or each record cost? Second, do those Credits come from the plan's included Credits, or must you buy more? Third, will HubSpot move some agent use that now counts as API use into the managed environment? The pricing post does not answer these questions yet.

| Your situation | Route | HubSpot writes per week | HubSpot cost |
| --- | --- | --- | --- |
| 10 to 20 key accounts, each item checked by hand | Claude connector | 10 to 20 approvals | Included with the seat |
| 200 accounts, reruns must be safe | Script on the API with a named service key | About 6 requests | Part of the daily API limit |
| Sensitive data turned on in HubSpot | Script on the API only | About 6 requests | Part of the daily API limit |
| Managed environment, after launch | Not available yet | Unknown | Credits, rate not published |

## What a weekly note looks like

A note body can hold 65,536 characters, which is enough for a full week. But an account owner reads short notes faster. For this job, we use one format. The first line gives the week and a one-sentence summary.

Then there is one block per platform, with at most 3 items each. Each item has a date, a short point and a link. The last line gives the request id of the pull, so you can match it to the bill. Here is an example with this week's real Zapier data, without reviewer names:

```text
2026-W47 · Zapier · Public activity: 4 new Trustpilot reviews, all 1-star, about cancellation and refunds; no company reply.
LinkedIn (8 company posts): Nov 17 and Nov 18, two AutomationBench model rankings; Nov 19, sign-up for New York events; 5 light posts, links only.
Trustpilot: Nov 22, 1-star, workflow errors and no refund for unused months; Nov 20, 1-star, hard to cancel; Nov 18, 1-star, wants another tool; Nov 17, 1-star, bad experience.
Reddit: 10 titles name Zapier; 7 are one freelancer's job post (merged into 1, not linked to the account).
Source request: req_b2ebb0fd3327401a (2026-11-22 13:05 SGT)
```

Two company properties are filterable numbers. `ei_low_reviews` holds this week's count of 1-star and 2-star reviews. `ei_digest_week` holds the week of the last write. A third, `ei_digest_note_id`, is only for the script's duplicate check. Sort by `ei_low_reviews` in HubSpot to see which accounts got the most low public ratings this week.

## The weekly script, step by step

The full weekly write-back has six steps.

1. Use the service key to search for the companies to process. Get the record ID, domain, `ei_linkedin_slug`, `ei_digest_week` and `ei_digest_note_id`.
1. For new companies with an unchecked LinkedIn slug, call `linkedin/company_profile` once. If the website does not match the HubSpot domain, flag the company and skip it this week.
1. Make an `Idempotency-Key` from week, account and capability, and call the three capabilities. On a 429, wait for `retry-after`. On a 422, fix the parameter from `did_you_mean`, and use a new key.
1. Deduplicate and filter in the script. Use platform plus item ID across all accounts. Drop LinkedIn posts by other authors and Reddit posts that only link to a form. Keep the last 7 days.
1. Give Claude only the filtered items for each account and let it write the summary. A person reads the combined result.
1. For companies with no summary this week, batch-create notes with the company link. Batch-update the existing ones by note ID. Then batch-write the note ID, week and low-review count back to the companies.

If any step fails, run the whole script again. In step 3, the same key replays the first response with no new charge. In step 6, the note ID on the company makes the rerun edit the same note and add none. If the script stopped between creating a note and writing back to the company, the search in the previous section fills the gap.

HubSpot asks you to keep errors below 5% of requests. To stay below that line, write one record first in step 6. Check that the property names and association type IDs are correct, and then send the full batch.

## No double charge on retry: the EveryInfra side

A weekly write-back script will retry. Causes include a 429, a dropped connection, the Claude Code first-byte timer, or a HubSpot write error that makes you run the batch again. EveryInfra handles this in three layers.

Layer one: failures and empty results are free. At 12:50 Singapore time, we searched Reddit for a made-up phrase. The response had 0 rows, `charged_usd` was 0, and `reason` was `empty_result_refunded`. The hold of 57 units went back at once. The 429, 422 and 409 responses were also free ([EveryInfra OpenAPI](https://api.everyinfra.com/openapi.json); [refund reconciliation](/en/build/failure-refund-reconciliation)).

Layer two is the `Idempotency-Key` header. The OpenAPI text says to use one new key per logical request, with 1 to 255 visible ASCII characters. For a synchronous call, the same key with the same platform, action and parameters within 24 hours replays the first successful response. The response has `replayed: true` and the header `Idempotent-Replayed: true`. Nothing runs again and nothing is charged again.

Different parameters get `409 idempotency_conflict`. If the first request is still running, you get `409 idempotency_in_progress` with `Retry-After`. A first request that did not succeed releases the key. We tested three steps at 12:49:

```bash
K="hs-weekly-2026w47-zapier-profile"   # week + account + capability; reuse it for reruns in the same week
curl -s https://api.everyinfra.com/api/v1/social \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" -H "Content-Type: application/json" \
  -H "Idempotency-Key: $K" \
  -d '{"platform":"linkedin","action":"company_profile","params":{"company":"zapier"}}'
# 12:49:16 first call: 200, 9.32 s, id req_253a4b3503e5441a, charged_usd 0.000556
# 12:49:34 same key, same body: 200, 0.58 s, same id, replayed: true, header idempotent-replayed: true
# 12:49:43 same key, company changed to calendly: 409 idempotency_conflict, 0.13 s, next_steps says nothing was charged
```

![Terminal screenshot of three real requests with one Idempotency-Key. First: 200, 9.32 s, charged_usd 0.000556. Second: 200, 0.58 s, the same request id, replayed true, and the header idempotent-replayed: true. Third, with a changed parameter: 409 idempotency_conflict, and the error says nothing was charged. Teal boxes mark the replay and the 409.](https://everyinfra.com/articles/hubspot-mcp-pricing/img-idem-replay.webp?utm_medium=ai_doc&utm_campaign=page_md)

The same key returns the first response; a changed request is refused. Real responses at 12:49 Singapore time, November 22, 2026. | source: live test https://api.everyinfra.com/api/v1/social

The replayed body still shows `billing.charged_usd` of 0.000556. That is a copy of the first response, with the same `id`, and the bill has only one charge. Your key format defines what counts as the same request. With week plus account plus capability, reruns in the same week cost once, and the next week starts a new key. With a random UUID per run, every rerun is a new request, so the key does nothing.

| Case | EveryInfra response | Charged? | What your script does |
| --- | --- | --- | --- |
| Same key, same body, within 24 hours | 200 with `replayed: true` | No | Use the response as it is |
| Same key, other parameters | `409 idempotency_conflict` | No | Make a new key |
| Same key, first request still running | `409 idempotency_in_progress` with `Retry-After` | No | Wait and send again |
| First request failed | Error; the key is released | No | Send again with the same key |
| No key | New request | Yes, again | Always add the key |

The IETF HTTP API working group is turning this header into a standard. Draft 09 came out on November 21, 2026 ([IETF: draft-ietf-httpapi-idempotency-key-header-09](https://datatracker.ietf.org/doc/draft-ietf-httpapi-idempotency-key-header/)). Its definition matches our use: the client makes the key, and the server uses it to recognize retries. HTTP semantics list POST as not idempotent, so without a key, a resent POST is a new request ([RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html)).

Layer three is on the remote MCP. The `everyinfra_call_api` tool has no idempotency key parameter. If Claude retries a synchronous call in chat, each retry is a new request. Async submissions (`mode: async`) with identical parameters within 5 minutes merge into the first job, with no new charge. So put the weekly bulk pull in a script with REST and `Idempotency-Key`. Let Claude read the filtered data, write the summaries and send the HubSpot writes.

## Preventing duplicate HubSpot writes: a documented design, not run

The HubSpot CRM API has no request-level idempotency key. A user who ran HubSpot from Claude Code for three weeks lists this in a post on r/hubspot ([Reddit r/hubspot](https://www.reddit.com/r/hubspot/comments/1ss3ma7/3_weeks_running_hubspot_from_claude_code_cli/)). If a custom property already exists, its creation returns 409, and you must handle the 409 yourself. The same post says that a `PATCH` with one field cleared two related fields, and that notes need `hs_timestamp` in UTC with a Z suffix. That is one user's report. We did not find the last two points in HubSpot's docs, so test them in a sandbox first.

HubSpot's docs give three tools you can use against duplicates. The first is the record ID. Every record gets an `hs_object_id`, and an update by ID does not create a new record. Companies also have a domain, and the companies guide says to always include it, because it is the main unique identifier that prevents duplicate companies ([HubSpot: Companies API](https://developers.hubspot.com/docs/api-reference/latest/crm/objects/companies/guide)).

The second is the unique-value property. The properties guide says you can have up to ten unique ID properties per object. Set `hasUniqueValue` to `true` when you create the property, and then use `idProperty` to read records by it ([HubSpot developer docs: Properties API](https://developers.hubspot.com/docs/api-reference/latest/crm/properties/guide)). The Knowledge Base adds that you can turn this on only when you create the property, and that feedback submissions, marketing events and products do not support it yet ([HubSpot Knowledge Base: Set validation rules for a property](https://knowledge.hubspot.com/properties/set-validation-rules-for-properties)).

The third is search. Notes are searchable activities, and the search endpoint can filter records linked to a company with the `associations.company` pseudo-property. The docs also warn that new or updated records can take a few moments to appear in search results, and search is limited to five requests per second per account ([HubSpot: Search the CRM](https://developers.hubspot.com/docs/api-reference/latest/crm/search-the-crm)).

The docs do not say if notes accept a custom unique-value property. Notes have an endpoint to upsert by unique property values ([HubSpot: Upsert notes](https://developers.hubspot.com/docs/api-reference/latest/crm/activities/notes/batch/upsert-notes)), and notes are not on the Knowledge Base exclusion list. But no page states that you can create a `hasUniqueValue` property on notes. We have no HubSpot account, so we did not try. The main design below uses only documented methods. The script dedupes single items locally, and each company gets one summary note per week. The note ID and the week go into custom company properties, and a rerun edits the same note by ID.

| What you write | Dedup key | How | Result of a rerun |
| --- | --- | --- | --- |
| One public item | Platform + item ID, for example `reddit:t3_1y2fct9`, in the script's local store | Not written to HubSpot alone; goes into the weekly summary | Only its status changes, for example "company replied" |
| Note: weekly summary | Company record ID + week; note ID stored in company property `ei_digest_note_id` | Not yet this week: `notes/batch/create` with the company link; already there: `notes/batch/update` by note ID | Edits the same note, adds none |
| Company: `ei_low_reviews`, `ei_digest_week`, `ei_digest_note_id` | Company record ID (`hs_object_id`) | [`companies/batch/update`](https://developers.hubspot.com/docs/api-reference/latest/crm/objects/companies/batch/update-companies) | Same value, no side effect |
| Note-to-company link | Sent in the create request | Type ID 190 (note to company), only on create | Editing a note adds no link |

```text
# 1) In step 1's company search, also read this week's state and the note ID
POST https://api.hubapi.com/crm/objects/2026-09/companies/search
{ "filterGroups": [ { "filters": [ { "propertyName": "ei_linkedin_slug", "operator": "HAS_PROPERTY" } ] } ],
  "properties": [ "domain", "ei_linkedin_slug", "ei_digest_week", "ei_digest_note_id" ], "limit": 100 }

# 2a) ei_digest_week is not this week: create the summary note and link it to the company
POST https://api.hubapi.com/crm/objects/2026-09/notes/batch/create
{ "inputs": [ { "properties": { "hs_timestamp": "2026-11-22T04:45:00Z",
      "hs_note_body": "2026-W47 · Zapier · Public activity: ..." },
    "associations": [ { "to": { "id": "8812345" },
      "types": [ { "associationCategory": "HUBSPOT_DEFINED", "associationTypeId": 190 } ] } ] } ] }

# 2b) ei_digest_week is this week: edit the same note by ei_digest_note_id
POST https://api.hubapi.com/crm/objects/2026-09/notes/batch/update
{ "inputs": [ { "id": "<ei_digest_note_id>", "properties": { "hs_note_body": "2026-W47 · Zapier · ..." } } ] }

# 3) Write the note ID, week and low-review count back to the company
POST https://api.hubapi.com/crm/objects/2026-09/companies/batch/update
{ "inputs": [ { "id": "8812345", "properties": {
    "ei_digest_week": "2026-W47", "ei_digest_note_id": "<new note ID>", "ei_low_reviews": "4" } } ] }
```

This is a configuration example, and we did not run it on a HubSpot account. The design has one gap. If the script stops after 2a creates the note but before step 3, the company has no note ID, and a rerun creates a second note. To close the gap, the rerun first searches notes for each company whose `ei_digest_week` is not this week. Filter by `associations.company` and this week's `hs_timestamp` range. If a note body starts with "2026-W47 ·", write its ID back to the company and use 2b. Search results lag, so wait a few minutes after a stop before you rerun.

If your test account lets you create a `hasUniqueValue` property on notes, you can use `notes/batch/upsert` with `idProperty` instead. That writes in one step and has no gap, but confirm it in a test account first. A note body can hold 65,536 characters, and `hs_timestamp` is required. To link a note to a company, use type ID 190 in the HUBSPOT_DEFINED category. For a deal, use 214 ([HubSpot developer docs: Notes API](https://developers.hubspot.com/docs/api-reference/latest/crm/activities/notes/guide)).

To check this design in a test account, look at three things. If any check fails, do not connect a production account.

| Check | How | Pass |
| --- | --- | --- |
| Rerun in the same week | Run the script twice in one week | The second run sends only `notes/batch/update`, no `notes/batch/create`; the company timeline still shows one summary for the week |
| Stop in the gap | Stop the script between 2a and step 3, wait a few minutes, run again | The search restores the note ID; no second note |
| Next week | Run with next week's week value | A new summary is created; last week's note is unchanged |

Developer test accounts are free, include a 90-day trial of many Enterprise features, and one developer account can create up to 10 of them ([HubSpot developer docs: Account types](https://developers.hubspot.com/docs/getting-started/account-types)).

The same keys work in the Claude connector, as prompt rules. Tell Claude to read the company's `ei_digest_week` and `ei_digest_note_id` first. If this week's summary exists, edit that note; create one only when there is none, and then write the note ID back to the company. Keep each batch at 10 records or fewer, and list the records for approval before each write. HubSpot recommends that you update one record before bulk changes. The audit log also records each create or update from Claude under the user and the Claude connector. So you can trace a write to a chat.

![Flow chart of a weekly rerun. Left, EveryInfra pulls with an Idempotency-Key. A success replays within 24 hours with no new charge. Empty or failed results are refunded, and the key is released. A 429 waits for retry-after with no charge. Right, the HubSpot writes, a configuration example: the company stores the ID of this week's summary note, so a rerun edits the same note and adds none. Company fields are overwritten by record ID. New notes carry association type 190.](https://everyinfra.com/articles/hubspot-mcp-pricing/fig-06-retry-timeline.en.light.svg?utm_medium=ai_doc&utm_campaign=page_md)

## 200 accounts per week: what each side costs

On EveryInfra, use the catalog prices. Each account needs one `linkedin/company_posts` call ($0.002319), one `trustpilot/reviews` call ($0.001389) and one `reddit/search` call ($0.000792) per week. That is $0.0045 per account. For 200 accounts, that is 600 calls and at most $0.90 per week. Over 52 weeks, that is at most $3.90 per month and $46.80 per year.

It is a maximum because empty results are free. If an account has no Trustpilot page, that call costs nothing. Our three accounts each cost $0.0045, with no empty results.

| Item | Per week | Per month (x52/12) | Source |
| --- | --- | --- | --- |
| EveryInfra fees, 200 accounts x 3 calls | At most $0.90 | At most $3.90 | Catalog `price_usd`; $0.0045 per account in tests |
| HubSpot API requests, batch endpoints | About 6 | About 26 | This design; Starter allows 250,000 per day |
| HubSpot Claude connector write rounds | 40 rounds of up to 10 records | About 173 | Claude connector help page |
| HubSpot Credits | 0 | 0 | Only used in the managed environment |
| One Claude Pro seat | — | $20 ($17 on annual billing) | Claude pricing page, read November 22, 2026 |
| HubSpot API limit pack | Not needed | $500 per pack | Catalog Technical Limits |

![Horizontal bar chart, monthly USD, log scale: EveryInfra fees for 200 accounts at most $3.90; one Claude Pro seat $20; one HubSpot API pack $500, not needed here; HubSpot Credits 0 without the managed environment.](https://everyinfra.com/articles/hubspot-mcp-pricing/fig-05-weekly-cost-bar.en.light.svg?utm_medium=ai_doc&utm_campaign=page_md)

The connector route needs 40 approvals per week. The script route puts the writes into 6 API requests, and a person reads one summary. If some companies already have this week's note and others do not, step 6 sends a create batch and an update batch. For 200 companies that is at most 3 batches, so at most 7 requests per week, still a tiny share of the limit.

HubSpot has not said how much "everyday" use a seat includes. Assume that one person asks Claude to update 200 companies and create 200 notes every week. We do not know if that is still everyday use. We also do not know how many Credits the excess will cost. Until HubSpot publishes the rates, plan large write-backs against the API limits, which are public numbers.

## What the videos show that the docs do not

We searched YouTube for "hubspot mcp" with `youtube/search` at 13:03 Singapore time on November 22, 2026. We took English transcripts of 5 videos with `youtube/transcript`, at $0.000556 and 3.9 to 6.1 seconds each: the top three results, plus two Claude-with-HubSpot videos outside the top 10, a beginner guide and a review. The beginner guide repeated the top three, so we did not use it. The first result was a 10-minute demo by a RevOps consultant from June 2025, with 19,601 views. The second was a 15-minute test by a GTM engineer from August 2026, with 85,382 views, the most in the top 10. The third was a 6-minute developer MCP tutorial from the HubSpot Developers channel from October 2025, with 2,920 views.

The first video teaches the old setup. It creates a private app in HubSpot settings and says to "select all of the scopes". It then pastes the token into the Claude desktop file `claude_desktop_config.json`, which runs a local npm package. This setup no longer works for new apps. HubSpot's docs say that you cannot create legacy private apps after October 26, 2026, and existing apps still work ([HubSpot developer docs: Legacy private apps](https://developers.hubspot.com/docs/apps/legacy-apps/private-apps/overview)). Even with an old app, do not give Claude a token with all scopes. The same video asks Claude to research 8 executives of a company on the web and create them as contacts, with no approval step. If you run the same prompt again, the CRM gets 8 duplicate contacts.

The second video adds three points that the docs do not fully cover. First, the write tool "manage CRM objects" arrived with no changelog entry that the creator could find, so he built a small tool that reads the tool list every hour and shows changes. Do not hard-code tool names; read `get_user_details` first. Second, service keys have names. Records that a key creates or changes show this name in the activity panel and the audit log, so give your write-back script its own named key. Third, personal access keys can only read CRM objects; to write, use a service key or an app.

In the demo, he sets Claude's tool permission to "always allow" to skip approvals. HubSpot recommends "Needs Approval", so do not copy this in production. He also guesses that a local redirect URL for the MCP connector can fail over time. The Claude Code docs use a local callback in their example. He did not test this, and neither did we.

The third video covers the developer MCP server. You join the beta under "Product updates > In beta" and run `hs mcp setup` to pick your IDE. It helps you build projects and fix build errors, but it does not touch CRM data, so a person who searches for "hubspot mcp" can install the wrong server. The extra review says that the MCP server could not read notes at the time. The current integration guide says that notes and other activities are blocked only in accounts with sensitive data turned on. After you connect, call `get_user_details` and check the object list for your account.

## Limits and caveats

We did not run the HubSpot side on a real account. All HubSpot steps are configuration examples. HubSpot numbers come from public pages that we read on November 22, 2026. The duplicate-write design comes from HubSpot's docs, and the docs do not say if notes accept a unique-value property, so run it in a test account first. The HubSpot request counts, 6 to 7 per week, and the 40 connector rounds are derived from the documented batch sizes of 100 and 10; we did not send them.

The tool list of the HubSpot MCP server depends on the subscription, permissions and account settings. The docs say to call `get_user_details` first to see your tools and objects. We had no authorized account, so we cannot list the tool names.

On the EveryInfra side, we pulled each account once, so the sample is small. The weekly rate estimates cover only late November 2026. `reddit/search` covers only the last month and searches posts, not comments. A brand name that is also a common word will match more unrelated posts. In LinkedIn company feeds, the author fields are sometimes empty.

Trustpilot returns English reviews by default; add `lang` for other languages. We made only one remote MCP call, so 74.6 seconds is not a typical value. It only shows that the timer needs a margin.

We used four videos. They show creator demos, not a method that HubSpot documents. The data comes from public web pages. Before you store it in a CRM, check the rules for your region. This article is not legal advice.

Do not file a public review as the opinion of your contact at that company. A Trustpilot review comes from one user of the company, who is usually not the person in your CRM. In each note, give the platform, date and link. Do not store reviewer names in the CRM.

## Industry updates

- November 12, 2026: The HubSpot developer blog published a guide to custom MCP connectors. It uses MCPJam and read-only grants ([HubSpot developer blog](https://developers.hubspot.com/blog/connect-hubspots-mcp-server-with-any-ai-tool-securely)). For you: AI tools without a built-in connector can now connect with this guide.
- November 17, 2026: HubSpot published its headless pricing ([HubSpot](https://www.hubspot.com/company-news/pricing-headless)). For you: connector use is part of the seat, your own agents use API capacity, so check API capacity first for large jobs.
- November 21, 2026: The IETF HTTP API working group published draft 09 of the `Idempotency-Key` header ([IETF](https://datatracker.ietf.org/doc/draft-ietf-httpapi-idempotency-key-header/)). For you: your own write-back service can accept idempotency keys in the same way, so a Claude retry does not write twice.

## FAQ

**What is the HubSpot MCP server URL?**

It is `https://mcp.hubspot.com`. The transport is Streamable HTTP, and auth is OAuth 2.1 with PKCE (S256). You need the client ID and secret of a connector that you create under "Development > MCP Connectors" ([HubSpot integration guide](https://developers.hubspot.com/docs/apps/developer-platform/build-apps/integrate-with-the-remote-hubspot-mcp-server)).

**Does the HubSpot MCP server cost extra?**

Under the pricing of November 17, 2026, everyday use in connectors such as Claude and ChatGPT comes with the HubSpot seat. Your own agents on the APIs use API capacity, not Credits. Only the managed environment that HubSpot is building will use Credits, at $0.010 each ([HubSpot](https://www.hubspot.com/company-news/pricing-headless)). The AI tool itself is a separate cost, for example $20 per month for Claude Pro.

**How do I set up hubspot mcp in claude code?**

HubSpot does not support dynamic client registration. Use `claude mcp add --transport http --client-id <ID> --client-secret --callback-port 8080 hubspot https://mcp.hubspot.com/`. Use the same redirect URL as the HubSpot connector. Then type `/mcp` in Claude Code to sign in ([Claude Code docs](https://code.claude.com/docs/en/mcp)).

**Which tools does the HubSpot MCP server have?**

The list depends on your subscription, user permissions and account settings. After you connect, call `get_user_details`. It returns your user, your account, and the objects and tools you can use ([HubSpot integration guide](https://developers.hubspot.com/docs/apps/developer-platform/build-apps/integrate-with-the-remote-hubspot-mcp-server)).

**Is the HubSpot MCP server on GitHub the same as mcp.hubspot.com?**

No. `mcp.hubspot.com` is the hosted remote server that reads and writes CRM data. The HubSpot developer MCP server runs locally with the HubSpot CLI and helps you build apps and CMS content. It does not read or write CRM records ([HubSpot developer MCP docs](https://developers.hubspot.com/docs/developer-tooling/local-development/mcp-server); [HubSpot CLI repository](https://github.com/HubSpot/hubspot-cli)).

**Can I still create a private app in HubSpot?**

Not a new one. HubSpot's docs say that, as of October 26, 2026, you cannot create legacy private apps, and existing ones still work. For new integrations, use a service key or an app on the developer platform. Service keys share the limits of privately distributed apps ([HubSpot developer docs: Legacy private apps](https://developers.hubspot.com/docs/apps/legacy-apps/private-apps/overview)). Some 2025 tutorials still teach the private app setup with all scopes, and you will not find the button.

**Can the HubSpot MCP server see public LinkedIn, Trustpilot or Reddit content about my customers?**

No. Its social features cover only the social accounts that you connect to HubSpot and your own posts ([HubSpot integration guide](https://developers.hubspot.com/docs/apps/developer-platform/build-apps/integrate-with-the-remote-hubspot-mcp-server)). Public posts and reviews about customer companies must come from outside, for example from [`linkedin/company_posts`](/en/linkedin-api/company_posts) and [`trustpilot/reviews`](/en/trustpilot-api/reviews).

## Get started

1. Sign up in the [EveryInfra quickstart](/en/docs#quickstart) and put your key in the `EVERYINFRA_API_KEY` environment variable. Add `https://api.everyinfra.com/mcp` in Claude or Claude Code as shown on the [MCP page](/en/mcp-server).
1. Create an MCP connector in HubSpot. Skip this step if you use HubSpot's own connector in Claude on the web. Set write tools to "Needs Approval".
1. In a HubSpot test account, create three custom company properties: `ei_digest_week`, `ei_digest_note_id` and `ei_low_reviews`.
1. Run one account first. Pull [LinkedIn company posts](/en/linkedin-api), [Trustpilot reviews](/en/trustpilot-api) and [Reddit posts](/en/reddit-api), and send an `Idempotency-Key` (week + account + capability) with each request. Dedupe, let Claude write the summary, approve it, and write this week's summary note for that company.
1. Run the same requests again. Check that EveryInfra shows no new charge and that HubSpot has no extra note. Then scale to 200 accounts and check the bill against the [pricing page](/en/pricing) and the catalog.

Related guides: [Atlassian MCP server competitor tickets](/en/blog/atlassian-mcp-server), [Outreach MCP follow-ups](/en/blog/outreach-mcp), [ActiveCampaign with social reviews](/en/blog/activecampaign-mcp-active-intelligence-social-review-data), [error self-healing](/en/build/api-errors-self-healing).

## References

1. HubSpot is headless. Here's how we'll price it. HubSpot, November 17, 2026. https://www.hubspot.com/company-news/pricing-headless
1. Integrate AI tools with the HubSpot MCP server. HubSpot developer docs, updated November 20, 2026. https://developers.hubspot.com/docs/apps/developer-platform/build-apps/integrate-with-the-remote-hubspot-mcp-server
1. Using the HubSpot MCP server. HubSpot developer docs, September 18, 2026. https://developers.hubspot.com/docs/build-with-ai/remote-mcp-server
1. Remote HubSpot MCP server is now generally available. HubSpot developer changelog, April 13, 2026. https://developers.hubspot.com/changelog/remote-hubspot-mcp-server-is-now-generally-available
1. Connect HubSpot's MCP Server With Any AI Tool Securely. HubSpot developer blog, November 12, 2026. https://developers.hubspot.com/blog/connect-hubspots-mcp-server-with-any-ai-tool-securely
1. API usage guidelines and limits. HubSpot developer docs, read November 22, 2026. https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines
1. Technical Limits. HubSpot Product & Services Catalog, read November 22, 2026. https://legal.hubspot.com/hubspot-product-and-services-catalog/technical-limits
1. HubSpot Product & Services Catalog. HubSpot, read November 22, 2026. https://legal.hubspot.com/hubspot-product-and-services-catalog
1. HubSpot Credits. HubSpot, read November 22, 2026. https://www.hubspot.com/products/artificial-intelligence/credits
1. Sales Software Pricing. HubSpot, read November 22, 2026. https://www.hubspot.com/pricing/sales
1. Set up and use the HubSpot connector for Claude. HubSpot Knowledge Base, read November 22, 2026. https://knowledge.hubspot.com/integrations/set-up-and-use-the-hubspot-connector-for-claude
1. Manage access to apps. HubSpot Knowledge Base. https://knowledge.hubspot.com/integrations/manage-access-to-apps
1. Properties API. HubSpot developer docs. https://developers.hubspot.com/docs/api-reference/latest/crm/properties/guide
1. Set validation rules for a property. HubSpot Knowledge Base, read November 22, 2026. https://knowledge.hubspot.com/properties/set-validation-rules-for-properties
1. Companies API. HubSpot developer docs, updated November 16, 2026. https://developers.hubspot.com/docs/api-reference/latest/crm/objects/companies/guide
1. Create or update a batch of companies by unique property values. HubSpot developer docs, updated November 16, 2026. https://developers.hubspot.com/docs/api-reference/latest/crm/objects/companies/batch/upsert-companies
1. Create or update a batch of notes by unique property values. HubSpot developer docs. https://developers.hubspot.com/docs/api-reference/latest/crm/activities/notes/batch/upsert-notes
1. Notes API. HubSpot developer docs, updated November 16, 2026. https://developers.hubspot.com/docs/api-reference/latest/crm/activities/notes/guide
1. Update a batch of companies. HubSpot developer docs. https://developers.hubspot.com/docs/api-reference/latest/crm/objects/companies/batch/update-companies
1. Developer MCP server. HubSpot developer docs. https://developers.hubspot.com/docs/developer-tooling/local-development/mcp-server
1. HubSpot CLI. GitHub. https://github.com/HubSpot/hubspot-cli
1. HubSpot won't charge extra when Claude or ChatGPT works its CRM. PPC Land, November 19, 2026. https://ppc.land/hubspot-wont-charge-extra-when-claude-or-chatgpt-works-its-crm/
1. HubSpot Just Announced New Headless Pricing. IMPACT, Nov 2026. https://www.impactplus.com/learn/hubspot-just-announced-new-headless-pricing-what-this-means-in-plain-english
1. MCP. Claude Code docs, read November 22, 2026. https://code.claude.com/docs/en/mcp
1. Permissions. Claude Code docs. https://code.claude.com/docs/en/permissions
1. Getting started with custom connectors using remote MCP. Claude Help Center. https://support.claude.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp
1. Plans & pricing. Claude, read November 22, 2026. https://claude.com/pricing
1. Authorization. MCP specification 2026-07-28. https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization
1. RFC 7636: Proof Key for Code Exchange. IETF. https://datatracker.ietf.org/doc/html/rfc7636
1. The Idempotency-Key HTTP Header Field, draft 09. IETF, November 21, 2026. https://datatracker.ietf.org/doc/draft-ietf-httpapi-idempotency-key-header/
1. RFC 9110: HTTP Semantics. IETF. https://www.rfc-editor.org/rfc/rfc9110.html
1. EveryInfra capability catalog, read 12:42 Singapore time, November 22, 2026. https://api.everyinfra.com/api/v1/social/catalog
1. EveryInfra OpenAPI, read November 22, 2026. https://api.everyinfra.com/openapi.json
1. 3 weeks running HubSpot from Claude Code CLI instead of MCP. Reddit r/hubspot. https://www.reddit.com/r/hubspot/comments/1ss3ma7/3_weeks_running_hubspot_from_claude_code_cli/
1. Anyone using HubSpot MCP? Reddit r/hubspot. https://www.reddit.com/r/hubspot/comments/1r1d23e/anyone_using_hubspot_mcp/
1. MCP Inspector. GitHub. https://github.com/modelcontextprotocol/inspector
1. Authentication overview. HubSpot developer docs. https://developers.hubspot.com/docs/apps/developer-platform/build-apps/authentication/overview
1. Make API requests using a service key. HubSpot developer docs, October 28, 2026. https://developers.hubspot.com/docs/apps/developer-platform/build-apps/authentication/account-service-keys
1. HubSpot Account Types. HubSpot developer docs. https://developers.hubspot.com/docs/getting-started/account-types
1. Legacy private apps. HubSpot developer docs, updated October 30, 2026. https://developers.hubspot.com/docs/apps/legacy-apps/private-apps/overview
1. Search the CRM. HubSpot developer docs. https://developers.hubspot.com/docs/api-reference/latest/crm/search-the-crm
1. Public Beta: Self-Service MCP Auth Apps for the HubSpot Remote MCP Server. HubSpot developer changelog, January 20, 2026. https://developers.hubspot.com/changelog/public-beta-self-service-mcp-auth-apps-for-the-hubspot-remote-mcp-server
1. HubSpot connector for Claude: Additional Object Access and Admin Controls. HubSpot developer changelog, August 28, 2025. https://developers.hubspot.com/changelog/claude-connector-additional-objects-and-admin-controls
