Every portal you connect, in one list.
Each client's portal with its Hub ID and the name you give it. Every answer says which portal it came from, and if one portal needs reconnecting, the others keep working.
Connect HubSpot to the AI you already use. Ask which campaigns turned into deals, which paid leads nobody has followed up, and what each client's pipeline did this week. One connector covers every portal you connect.
HubSpot's own sign-in, one consent per portal. AdPlug keeps no copy of your CRM records, and every change is previewed before it runs. Included from Pro.
Most ad reports stop at the form fill, and the deals sit in HubSpot where nobody lines them up with the spend. Nine tools give your AI the records, pipelines and reports in every portal you connect, and a preview before anything changes.
Each client's portal with its Hub ID and the name you give it. Every answer says which portal it came from, and if one portal needs reconnecting, the others keep working.
Contacts, companies, deals, leads, tickets and custom objects, filtered and sorted on any property, including the records linked to a company or deal. One search can run across every portal.
Up to 100 records of one type at a time, with the properties you ask for and a link that opens each one in HubSpot.
Record types, pipelines and stages, properties and dropdown values, owners and portal settings. The AI checks the names before it filters or writes, so it isn't guessing at your custom fields.
SQL over your CRM data, with grouping and date buckets, in one portal or each portal you name. Amounts stay in each portal's currency.
Campaign attribution and revenue, campaign results, marketing email performance, page and blog analytics, AI search visibility and buyer intent. Some need a HubSpot plan or permission the portal may not have, and AdPlug's Connections page shows which are missing.
Create and update contacts, companies, deals, leads, notes and tasks. The preview shows each record's current and new values, HubSpot takes at most 10 records per change, and records are never deleted or merged.
Build segments, set up campaigns, edit marketing emails and their A/B tests, and add custom properties and pipelines. Each change is previewed first and counts as one AI edit, and team owners can keep a teammate on View only.
Where there's no ready-made tool for the job, the AI can reach the rest of HubSpot's MCP tools through AdPlug, and any change made that way comes back as a preview first.
HubSpot asks for consent once per portal, so you connect each client's portal from AdPlug's Connections page. After that, the one HubSpot connector in your AI reaches all of them. Add AdPlug's ad connectors to the same Claude or ChatGPT and one question can line up what the ads cost with what they turned into.
Ask about one client's portal, or search every portal at once. Each answer names the portal it came from, and a change always targets one portal.
With Google Ads, LinkedIn Ads or Microsoft Ads in the same chat, the AI reads the source and campaign data on your HubSpot records and sets it against the spend.
HubSpot has its own address, https://api.adplug.app/mcp/hubspot. The all-platforms address is for the ad platforms, so add HubSpot next to it, or next to one ad platform's connector.
Client portals often report in different currencies, so AdPlug has the AI fetch the currency with every amount and keep them apart.
On Claude's Free plan
Claude Free allows one custom connector, so HubSpot and an ad connector in the same Claude chat need a paid Claude plan.
Short on purpose: the AI looks up your portals, properties and campaigns itself, and asks for the period when it needs one. The prompts that mention ads need an AdPlug ad connector in the same chat.
Generate a report using HubSpot and Google Ads on the lifecycle stages the leads from Google Ads reached.
Drop into your AIShow me the keywords that created deals and pipeline in HubSpot.
Drop into your AICompare what I spent on each ad campaign with the pipeline and revenue it created in HubSpot.
Drop into your AIWhich ad platform brings us the leads that turn into deals in HubSpot?
Drop into your AIWrite my weekly report: ad spend by platform next to the leads, deals and pipeline in HubSpot.
Drop into your AIFind the leads from paid ads that nobody has followed up yet.
Drop into your AICheck that my HubSpot leads carry the source and campaign data I need to tie them to ads.
Drop into your AIGive me a weekly summary for every client portal I've connected, with each client's ad spend next to it.
Drop into your AIConnect HubSpot and run any of these from Claude or ChatGPT.
Connect HubSpotStart with Claude or ChatGPT, then bring the same workflow into Cursor, VS Code, or whatever your team adopts next.
HubSpot runs its own connectors for Claude and ChatGPT, built on its MCP server, and they work one portal at a time: HubSpot's help articles say you connect one HubSpot account to a Claude or ChatGPT account, and switch by disconnecting and reconnecting. AdPlug puts every portal you connect behind one connector, brings your ad spend into the same chat, and shows you every change before it runs.
| HubSpot's own connector | AdPlug | |
|---|---|---|
| Portals per AI account | One at a time; disconnect and reconnect to switch | Every portal you connect, on one connector |
| Ad platform data | Not part of the connector | Google Ads, LinkedIn Ads and Microsoft Ads connectors in the same chat |
| Before a change runs | The AI may show the proposed changes and ask first; HubSpot suggests making ChatGPT ask before every write | A preview with current and new values every time; nothing runs until you say yes |
| Permissions | Follows your HubSpot user permissions | Follows your HubSpot user permissions, plus View only per teammate and a usage log |
| AI clients | Claude on a paid plan, and ChatGPT | Claude, ChatGPT with Developer mode, Cursor, VS Code, Codex and other MCP clients |
Sources: HubSpot's knowledge base articles Set up and use the HubSpot connector for Claude (updated September 17, 2026) and Set up and use the HubSpot connector for ChatGPT (updated September 28, 2026), checked October 17, 2026.
A HubSpot MCP is a connector that lets an AI tool like Claude or ChatGPT read and change your HubSpot data through the Model Context Protocol: contacts, companies, deals, pipelines, campaigns and reports. AdPlug's is hosted, so there's nothing to install. One connector reaches every portal you connect, and it works next to AdPlug's ad connectors, so the AI can put your ad spend against the leads and deals it created.
Yes. HubSpot runs its own connectors for Claude and ChatGPT on its MCP server. As of October 2026, HubSpot's help articles say you can connect one HubSpot account at a time to a Claude or ChatGPT account and switch by disconnecting and reconnecting, and its Claude connector needs a paid Claude plan. Neither brings in data from your ad accounts. AdPlug puts every portal you connect behind one connector, brings your ad spend into the same chat, and shows you every change before it runs.
Sign in to AdPlug, open Connections and click Connect HubSpot. Pick the portal on HubSpot's account picker and confirm the permissions, then do the same for each portal you want the AI to reach. In Claude, open Customize, then Connectors, click + Add, then Add custom connector, name it AdPlug - HubSpot and paste https://api.adplug.app/mcp/hubspot. Approve AdPlug's sign-in and the connector is ready.
Yes, ChatGPT adds custom MCP servers through Developer mode, which OpenAI lists for Plus, Pro, Business, Enterprise, and Education accounts on the web. Connect your portals in AdPlug first. Then in ChatGPT turn Developer mode on under Settings, Apps, Advanced settings, click Create app, paste https://api.adplug.app/mcp/hubspot as the MCP Server URL, and approve AdPlug's sign-in.
Yes, and that's the main reason agencies and consultants use it. HubSpot asks for consent once per portal, so you connect each client's portal from AdPlug's Connections page, and the one HubSpot connector in your AI reaches all of them. The AI can work in one portal or search every portal at once, it names the portal behind each result, and a change always targets one portal. Pro includes 3 portals, and Max and Agency include 10.
No. HubSpot has its own connector, https://api.adplug.app/mcp/hubspot. AdPlug's all-platforms URL, https://api.adplug.app/mcp, is for the ad platforms, so add HubSpot next to it, or next to one ad platform's connector, in the same Claude or ChatGPT. Both run on the same AdPlug account.
Yes, when the HubSpot connector and an AdPlug ad connector are in the same Claude or ChatGPT. Then one question can set Google Ads, LinkedIn Ads or Microsoft Ads spend against the leads, deals and revenue in HubSpot, by campaign, or by keyword where your HubSpot records carry the source and campaign data. Claude's Free plan allows one custom connector, so HubSpot and an ad connector together in Claude need a paid Claude plan.
Four are required: read access to contacts, companies and deals, plus the basic permission every HubSpot app needs to sign in. The other 60 are optional, and you can untick any of them on HubSpot's permissions screen. Unticking one only switches off the features that need it: SQL reports need HubSpot's SQL permission, attribution reports need reporting access and a campaign revenue permission (Marketing Hub Professional or Enterprise), and changes to contacts, companies and deals need their write permissions. AdPlug's Connections page shows how many of the 64 each portal granted and what's missing. A portal that connected AdPlug earlier keeps what it granted then: newer permissions stay locked until that portal's Super Admin allows them, and then you reconnect.
Someone with Super Admin rights or the App Marketplace Access permission in that portal. Anyone else can request it on HubSpot's own screen, and a Super Admin allows AdPlug for the portal once. On AdPlug's side, HubSpot is included from the Pro plan.
Yes, after you approve a preview. The preview names the portal and shows each record's current and new values, and nothing changes until you say so. HubSpot takes at most 10 records per change, and each change counts as one AI edit. Changes cover contacts, companies, deals, leads, notes, tasks, segments, campaigns, marketing emails, custom properties and pipelines. Records can't be deleted or merged, because HubSpot's MCP server has no tool for either. A segment can be deleted, which removes the list but not the records in it, and HubSpot can restore it. Team owners on Max and Agency can set a teammate to View only for HubSpot, which hides and blocks the change tools.
No copy of your CRM records: records and reports go straight to your AI assistant. For each portal, AdPlug stores the Hub ID, the portal's name and the name you give it, its domain and region, the HubSpot user ID and email that connected it, the permissions granted, and the login tokens, encrypted. Change previews keep the change you asked for and, once it runs, HubSpot's answer, until the daily clean-up after about a day. The usage log records the tool name and the Hub ID, no record data. Deleting your AdPlug account revokes every HubSpot login and deletes the rows.
HubSpot is included from Pro. Pro ($29 a month) connects 3 portals, Max ($89 a month) connects 10, and Agency connects 10 per person. It isn't on the Free plan: upgrade from the HubSpot card in AdPlug and you can connect your first portal straight away.
In AdPlug, open Connections, click Remove next to the portal on the HubSpot card, then Confirm remove. AdPlug deletes that portal's stored login and any previews that never ran, and asks HubSpot to revoke the login. Your HubSpot records stay exactly as they are. To uninstall AdPlug from the portal itself, open HubSpot's settings, go to Integrations, then Connected Apps, and choose Uninstall from AdPlug's Actions menu. To take the connector out of your AI, remove it in Claude's or ChatGPT's connector settings.
Nine tools, every portal you connect, and changes that only run after you approve a preview. Portals: every connected portal with its Hub ID and your name for it, and a status check that names any portal needing a reconnect. Records: contacts, companies, deals, leads, tickets, activities, products, quotes and custom objects, searched with filters, sorting and paging in one portal or all of them, or fetched by ID, up to 100 at a time. Schema: record types, pipelines and stages, properties and dropdown values, owners and portal settings. Reports: SQL over CRM data, plus HubSpot's attribution, campaign, marketing email, content, AI search and buyer intent reports, where the portal's plan and permissions allow. Changes: create and update contacts, companies, deals, leads, notes and tasks, segments, campaigns, marketing emails and their A/B tests, custom properties, pipelines, and AI search prompts and recommendations, at most 10 records per change. No record is deleted or merged. Everything else: any other tool HubSpot offers the portal, with changes turned into previews. Ads next to the CRM: Google Ads, LinkedIn Ads and Microsoft Ads through AdPlug's ad connectors in the same chat. Out of reach: forms and form submissions, workflow edits, files, and the ads data inside HubSpot. Safety: team owners can set View only for HubSpot, and every tool call is logged with the tool and the portal.
Still weighing your options? Read the best MCP servers for marketing in 2026, including HubSpot's own connector and how they compare.
Ask about leads, deals and pipeline in every client portal from the AI you already use, with your ad spend in the same chat. Every change is previewed first.