We value your privacy
We use cookies to improve your experience, analyze site traffic, and show relevant content.
Strictly Necessary
Required for the website to function. Cannot be disabled.
Analytics
Help us understand how visitors use the site so we can improve it.
Marketing
Used to deliver relevant ads and track their effectiveness.
MetaHub MCP · for HubSpot
Your AI — the one you already pay for — handles your HubSpot so you can fully focus on sales. Data entry, follow-ups, prioritisation, cleanup, quotes: it does the admin, you do the selling. Smarter than Breeze, on a model you actually picked.
🏆 Built by metawork.studio. HubSpot Solutions Partner — running HubSpot for clients since 2016.
Built for two people
Most «AI for HubSpot» tools assume you'll learn a new interface. MetaHub assumes you're busy and need shit to be done. The AI is already on your screen, and the CRM should just do what you ask in plain convo.
For reps + founder-sellers
For sales directors + founders managing a team
Try saying this to your AI
Plain English. No property names, no internal IDs, no clicking around. Your AI handles the HubSpot end, you keep selling.
"What's on my plate today?"
6 things. 2 deals advanced overnight, 3 tickets need a reply, 1 quote stuck in negotiation since Friday. Want me to draft the ticket responses?
"What stalling deals need my immediate attention?"
Acme ($72k, untouched 16 days), Nordwind ($28k, demo never followed up), Globex ($140k, decision-maker dropped off two weeks ago). Pulling the last engagement on each.
"Pull all the contacts I need to reach out to today, then draft a personalised first-touch email for each one."
14 contacts on today's list, including 4 from the re-engagement workflow. Wrote each email against the contact's lifecycle stage and the last touchpoint. Review before I queue them?
"Write a quote for Acme: 50 Pro seats, annual, 15% discount."
Done. €54,000 list, €45,900 after 15%. Filed as a line-item-backed deal under Acme, attached to the open thread with their procurement lead. Ready to send when you say go.
Everything it handles
There's no feature menu to learn — just things you can ask for, in plain words. Here's the range of what MetaHub takes off your plate.
Full, hands-off configuration so you can onboard yourself — pipelines, properties, custom objects, automations, built to spec the moment you ask.
Pull exactly what you need out of HubSpot and push exactly what you want back in — in plain language, no exports, no view-building.
Hand it a messy spreadsheet and it maps the columns, cleans the values, and files every record where it belongs.
Keep the portal tidy as you work — fix properties, fill gaps, reshape records — all on request, never by hand.
Ask for something and MetaHub does the technical part the way we would do it for you. Right the first time.
A 30-second morning briefing from your real portal: which deals moved, who is waiting, what to send today.
Funnels, forecasts, win/loss, leaderboards, campaign metrics — answered in chat, never built by hand in HubSpot.
Pull lookalike contacts from Apollo, craft sharp first-touch emails, and update the portal — without ever opening it.
The progress you make in conversation lands back in HubSpot as tasks, activities and tickets automatically.
Roll out a sales campaign across your pipeline right where you are already typing.
A dedicated workspace that finds and merges duplicate contacts and companies fast. Fully GDPR compliant: your data never leaves your browser or reaches AI.
We constantly update the functionality and playbooks. Any update to HubSpot, any change in their API, anything we add that simplifies and boosts productivity is included in free updates to your license.
The number that matters
~5h → 30min
per sales rep, per week, on CRM admin
The average rep loses about five hours a week updating HubSpot. Logging activities, copying notes, chasing overlooked leads, figuring out the UI, cleaning up overdues, trying to find most important things. MetaHub gives most of that time back, because the AI you already use can do it in seconds when asked.
For a team of five, that's roughly a full extra selling day per rep, every week. That's the headline. Everything else on this page is just how.
Smarter than Breeze
HubSpot's Breeze is a single, locked-down model with locked-down prompts. You can't choose the model, you can't bring your own context, you can't compose it with the other AI work you already do. That's a design choice that ages quickly — every new generation of Claude or GPT leaves Breeze further behind.
MetaHub is the inverse. It plugs into the AI you chose — Claude, ChatGPT, Gemini, Copilot, or any MCP-compatible client. The same chat you already use for email drafts, research, planning, code — now it also runs your CRM. When your AI upgrades to the next model, your CRM gets smarter the same day. No vendor lock-in, no waiting for HubSpot's roadmap.
HubSpot Breeze
MetaHub
Works with the AI you already use
Claude
ChatGPT
Gemini
Microsoft Copilot
GitHub CopilotUnder the hood, every common HubSpot action is covered — custom objects, vocabulary-aware properties, reporting, dedup, the lot. You don't need to learn any of it. You just talk.
Setup
No code. No agency call. No consultant on retainer.
Pick a plan below and check out. 30 days free, cancel anytime.
In Claude, ChatGPT, or Gemini, add MetaHub as a connector. We'll show you exactly where to click — under a minute.
Type connect to my hubspot, authorize connection, you're done.
Detailed setup
Step-by-step for Claude, ChatGPT, and Gemini — plus Microsoft Copilot and GitHub Copilot.
Works in claude.ai (no install), Claude Desktop, and Cursor — same address, same login.
↓ Download Claude Desktop (optional)Claude.ai requires Pro, Team, or Max for custom connectors. On the free plan? Use Claude Code, Cursor, ChatGPT (Developer Mode), or Gemini CLI instead — same MetaHub app, no subscription gate.
Pick a plan — see pricing below — and complete checkout.
Open claude.ai → click your profile picture → Settings → Connectors → Add custom connector.
Paste this address into the URL field: https://metahub.metawork.studio/mcp/
Click Add. A sign-in screen opens — choose Google, Microsoft, or email, using the same address you used at checkout. MetaHub recognises your license and connects automatically.
First time only: ask MetaHub to connect your HubSpot. Type connect my hubspot and paste your HubSpot Private App token when prompted.
Important: this requires the ChatGPT desktop app, not the website. The browser version of ChatGPT doesn’t support tool connections.
↓ Download ChatGPT Desktop (macOS / Windows)Pick a plan — see pricing below — and complete checkout.
Open the ChatGPT desktop app → Settings → scroll to the bottom → enable Developer Mode.
In Settings → Connectors → Add connector. Leave authentication set to OAuth.
Paste this address into the URL field: https://metahub.metawork.studio/mcp/
Click Connect. A sign-in screen opens — choose Google, Microsoft, or email, using the same address you used at checkout. MetaHub recognises your license and connects automatically.
First time only: type connect_hubspot and paste your HubSpot Private App token when prompted.
Gemini CLI is Google’s free AI assistant that runs in your computer’s terminal (command line). To use it, you need Node.js installed — it’s free and takes 2 minutes.
Pick a plan — see pricing below. Copy your license key from the confirmation email or your license account page.
Open your terminal (Mac: search «Terminal» in Spotlight · Windows: search «Command Prompt») and run: npm install -g @google/gemini-cli
Open the file ~/.gemini/settings.json in any text editor (create it if it doesn’t exist) and add the following — replacing YOUR_LICENSE_KEY with the key from step 1:
{
"mcpServers": {
"metahub": {
"httpUrl": "https://metahub.metawork.studio/mcp/",
"headers": {
"Authorization": "Bearer YOUR_LICENSE_KEY"
}
}
}
} Back in your terminal, type gemini and press Enter. MetaHub’s tools will be available immediately.
First time only: type connect_hubspot and paste your HubSpot Private App token when prompted.
MetaHub is a remote MCP server (Streamable HTTP + OAuth 2.1), so it plugs in with just its address and a browser sign-in. Add it in Microsoft Copilot Studio and use it inside your Microsoft 365 Copilot agents.
Heads-up: the consumer Copilot (Windows / copilot.microsoft.com) doesn’t support custom MCP servers — you connect through Copilot Studio.
Pick a plan — see pricing below — and complete checkout.
In Copilot Studio, add a tool, choose Model Context Protocol, and point it at https://metahub.metawork.studio/mcp/. Sign in with the address you used at checkout, then add the agent to Microsoft 365 Copilot.
First time only: type connect_hubspot and paste your HubSpot Private App token when prompted.
MetaHub is a remote MCP server (Streamable HTTP + OAuth 2.1), so it connects with just its address and a browser sign-in. Use it in GitHub Copilot agent mode inside VS Code or Visual Studio.
Pick a plan — see pricing below — and complete checkout.
In VS Code, open Copilot → Agent mode → Add MCP server and point it at https://metahub.metawork.studio/mcp/. Sign in with the address you used at checkout.
First time only: type connect_hubspot and paste your HubSpot Private App token when prompted.
Why pay for this
HubSpot’s own MCP is free, first-party, and genuinely fine for basic lookups — we’ll be the first to say so, and it reaches further than at launch, into campaigns, conversations and marketing email. On the CRM itself it’s still a dozen-odd generic tools: no custom objects, no schema building, no CRM reports, no duplicate cleanup, no workflows, no deletes of any kind, one portal. MetaHub is the operator layer that starts where the free one ends:
| Capability | MetaHub | HubSpot’s own MCP | Free community MCPs |
|---|---|---|---|
| Hosted + one-click sign-in (OAuth) | ✓ Yes | ✓ Yes | – Partial mostly token in config |
| Read & write core CRM — contacts, companies, deals, tickets | ✓ Yes | ✓ Yes | – Partial |
| Custom objects + build schema, properties, pipelines, stages | ✓ Yes | ✕ No can’t touch custom objects | – Partial read-only |
| Builds workflows — triggers, actions, custom-code steps, on/off | ✓ Yes | ✕ No no automation tools | ✕ No |
| CRM reports — funnels, forecasts, win/loss, leaderboards | ✓ Yes | ✕ No marketing-campaign metrics only | ✕ No |
| Finds and merges duplicates | ✓ Yes | ✕ No | ✕ No |
| Safe deletes — archive vs permanent/GDPR, the right recipe | ✓ Yes | ✕ No no delete or archive tools at all | ✕ No |
| Our HubSpot method baked in — no loose tasks, won’t wipe enum options | ✓ Yes | ✕ No | ✕ No |
| Email → CRM filing, daily briefing, summaries | ✓ Yes | ✕ No | ✕ No |
| Works marketing email + inbox conversations | ✕ No we stay on the CRM | ✓ Yes | ✕ No |
| Runs multiple portals / clients from one seat | ✓ Yes | ✕ No one portal per connection | ✕ No |
| First-party, maintained by the CRM vendor | – Partial we maintain the adapter | ✓ Yes | ✕ No mostly stale |
| Price | from $29/seat/mo | free | free |
Credit where it’s due: HubSpot’s own MCP is free, first-party, and genuinely fine for basic lookups and edits on one portal. If what you mostly want is marketing email and the inbox, it covers ground we deliberately don’t — take it, and we’ll tell you so. MetaHub earns its price the moment the work gets real: modelling custom objects, building workflows, reporting, cleaning duplicates, deleting safely, and running more than one portal — none of which the free option does.
GDPR & your data
MetaHub is built data-minimal by design. We don't keep a copy of your portal, and the heavy lifting that touches real records runs in your own browser — so GDPR compliance is a side-effect of the architecture, not a checkbox.
Every request runs live against your HubSpot and returns. We don't cache, copy, or warehouse your deals, contacts, or emails — there's no MetaHub database holding your CRM.
The deduplication workspace analyses your records locally, on your machine. When you merge, only the record IDs travel to us to action the merge — never the record content — and those jobs auto-delete within 24 hours.
MetaHub runs on servers in Germany. The only thing we persist is your connection credential — encrypted at rest — plus the email tied to your license.
The CRM data your AI reads to do its work goes only to the assistant you already chose — Claude, ChatGPT, Gemini — under your own provider agreement. MetaHub adds no extra AI in the middle.
Pricing
A couple of hours with a HubSpot specialist costs more than a year of MetaHub — and MetaHub runs your portal every day, not just the hour you booked. 30-day free trial on both plans. No setup fees. Cancel anytime.
Single user
$€3929/mo
billed monthly billed annually — save 26%
Team
$€2922/seat/mo
billed monthly billed annually — save 24%
Changelog
Every license includes future additions — no tier upgrade, no extra invoice. Recent-first.
One chat can be pointed at several Pipedrive accounts, and each answer carries a small block of metadata telling your AI which one is active. Until now that block said nothing at all when no account had been picked — it left the field empty. But empty did not mean the call went nowhere: it went to the default account. So a chat that had been pointed at a client's Pipedrive and then lost that pointer (a server restart is enough) looked like it had no account selected, while it was quietly reading and writing somewhere else. The field is never empty now. If no account was picked, it says so and names the one being used instead, marked as the default so it can never be confused with an account you chose. Same for MetaHub, where no account selected means the call would fail rather than fall back — it now says that too, instead of leaving your AI to infer it.
hs_use_account lets you point one chat at a specific client's HubSpot, and metawork_context lets you name that pointer so several chats can deliberately share it. Both work by handing your AI a signed token to carry on every following call — the token, not the connection itself, is what keeps the chat locked to that account, because the connection your AI client happens to be using can change without warning: a reconnect, a network hiccup, or us deploying an update all hand out a fresh one. Until now, naming a pointer with metawork_context (or pointing hs_use_account at one by name) skipped that token, so it relied on the connection staying the same after all. When it didn't, the chat lost its HubSpot context silently — no error, just the wrong portal or none at all. Every named pointer now gets a token too, so reconnects no longer reset it.
MetaHub asks you to confirm before anything irreversible — deleting a workflow, creating or updating records in bulk, sending an inbox reply. Until now those prompts named the record and stopped there, which reads exactly the same whether it is about to happen in your own portal or in a client's — and one chat can be pointed at several portals. Every confirmation now says which HubSpot account it would act in, and hands your AI that account as a separate field so it can show it to you before you answer; the send-reply preview carries it too, which matters because HubSpot has no unsend. The receipt after the write names the same account, matching what the audit log recorded. If the account cannot be worked out, the prompt says so loudly instead of quietly leaving it out. One related fix: a dry-run workflow delete no longer reports itself as a success — nothing was deleted, and the audit log now agrees.
`whoami` — the check your AI runs first to confirm it's connected to the right account — used to answer about both HubSpot and Pipedrive, whichever product you bought. On MetaHub that meant every answer carried a Pipedrive connection you never asked for (ours, not yours — MetaHub has no Pipedrive tools to use it with), and a live call to Pipedrive behind it every time. It now describes the CRM this product actually drives: your HubSpot connection, which portal this chat is pointed at, and who on your team has connected. The same fix repairs something that mattered more if you run several HubSpot portals on one license: after switching a chat to another portal, the short confirmation MetaHub attaches to each answer — the one naming the active account and carrying the token that keeps the chat locked to it — was looking at the Pipedrive slot, found nothing, and stayed silent. It now names your HubSpot portal, so a chat can't drift onto another one unnoticed.
Every connection now reports which version of the tool set it is serving, and your AI can see it. That matters because of a quiet failure the protocol allows: your AI client caches the list of MetaHub tools when it connects, and nothing ever tells it that list went out of date. When we rename or merge a tool, a client still holding the old list keeps offering the old name — and the call fails at the moment you need it, with an unhelpful "unknown tool". From now on: the version and a short fingerprint of the tool set ride along with every connection, `whoami` reports them, and a call made under a retired name either runs anyway (we forward it) or tells you exactly which tool replaced it and that reconnecting will refresh your list. Nothing about your CRM data changes; this is about MetaHub never breaking silently underneath you.
Ask which email underperformed and you get an answer, not a table. MetaHub pulls every send in a window and scores each one against your account's own median — because "22% open rate" means nothing on its own, and "22% against your usual 31%, with unsubscribes up threefold" is the thing you actually needed to know. Deliverability problems (bounces, unsubscribes, spam complaints) are flagged separately from dull copy, because a list quietly dying is the bigger problem. The campaign report was also rebuilt. It had been returning campaigns with every field blank — name, status, dates, budget, metrics, assets, all null — because it was asking HubSpot the wrong questions. It now returns real attribution (sessions, new and influenced contacts) and a per-asset breakdown with each asset's own numbers: emails with their sends and opens, landing pages with views and submissions, forms with conversion rates. One honest limitation: HubSpot retired the API that listed exactly who opened a given email back in October 2025. You get exact counts, plus the contacts the campaign is credited with — and MetaHub tells you which is which rather than passing one off as the other. These tools need Marketing Hub Professional; HubSpot won't allow access below that plan whatever your permissions say. On a lower plan they say so in one line instead of failing with an error code.
MetaHub can now see the conversations inbox: ask what's unanswered, read a thread, summarise it, file it against a deal, and reply to it. The useful part isn't the reading — it's "who's waiting on us". HubSpot has no way to ask that; MetaHub works it out by comparing when the customer last wrote to when you last answered, sorts by how long they've been waiting, and puts the people with an open deal behind them at the top. Ask "what's unanswered in the inbox" and you get a worklist, not a list. Replying is deliberately two steps. MetaHub drafts, shows you the exact wording, who it's going to and whose name it goes out under — and sends nothing until you say yes. If you change a word after that, it asks again, because what gets sent should be what you read. HubSpot has no unsend, so this isn't negotiable. Internal notes never reach the customer, and WhatsApp threads can be read but not replied to (HubSpot doesn't allow it through the API on any plan). Summaries include inbox conversations now too, so a deal recap stops missing the exchange that actually moved it. Ask hs_playbook('conversations') for the method. One thing to do: this needs new HubSpot permissions, and HubSpot only applies permission changes to new connections. Reconnect HubSpot once from your account page — everything else keeps working in the meantime.
Connecting HubSpot used to fail unless the HubSpot user approving it was the license's billing email or a listed team member — everyone else landed on "isn't on this license" with nothing they could do about it. That check is gone. Whoever you happen to be signed in to HubSpot as can approve the connection, and the account that approved it is recorded so you can see who connected what. If your HubSpot login differs from the address you pay with, or you manage a client's HubSpot, connecting works now.
Agency licenses no longer need a Service Key pasted for each extra HubSpot account. Ask your AI to connect and it hands back an authorization link — approve it in HubSpot and that account joins your authorized set. Disconnecting works per account too, so removing one client's HubSpot leaves the rest in place. Before it answers, each chat verifies which account it's actually pointed at, so a question about one client can't be answered out of another client's CRM.
Solo licenses cover one HubSpot account at a time, and moving to another one was always allowed — but once you had connected an account the page offered no way to do it, so the only route was reinstalling MetaHub from the marketplace. There's now a "Connect a different HubSpot" button on your account page. Sign in to the account you want before you press it: it replaces the one you had, and MetaHub stops reaching the old one.
Connecting a Solo license by pasting your license key into a config file no longer works — you sign in through your browser instead, the same way Claude and ChatGPT already connect. A license key identifies the license, not the person holding it: one Solo key pasted into five configs looks exactly like one person working from five machines. Signing in fixes that at the root. If you connect MetaHub through Claude, ChatGPT, Microsoft Copilot or GitHub Copilot you were already signing in and there's nothing to do; Gemini CLI now signs in too. Team plans keep license-key access; they're seat-counted and tied to their CRM account already.
Setting up Gemini CLI used to mean pasting your license key into ~/.gemini/settings.json. It signs in through your browser now, like every other client: add the server, run /mcp auth metahub, and approve it in the window that opens. Nothing secret sits in a config file on disk anymore.
When our HubSpot token service answered slowly (cold start plus a token refresh), the error shown was the onboarding message — telling an already-connected customer to reinstall the app. A slow broker now says exactly that («temporary, retry in a few seconds»), and the timeout budget was raised to cover the slow path.
Every entry in the activity log now records WHICH portal/account the write dispatched against — relevant when a team operator switches between clients, and for dedup merges, which carry the account they ran on. Filter with account= to see one account's history.
Deals join contacts and companies as a dedup entity — same review-and-merge flow, same audit trail. Recurring deals are handled: two deals in the same series (retainers, renewals) are recognized as siblings, not flagged as duplicates.
The paste-a-token mode of the dedup page is now gated behind a client invite link or Google/Microsoft/email sign-in, and every merge is attributed to the person who clicked it in the audit log.
Audit entries older than two years are pruned automatically.
Last week's activity log didn't catch merges made through the dedup tool — they run on a separate path and slipped past it. They're logged now too, one line per merge naming the record that was merged away and the one that survived, so «why is this duplicate gone» has an answer there as well.
Every write your AI makes — updates, archives, merges, pipeline changes — now lands in an activity log you can ask about directly: «why did we change that» or «why is this deal missing» gets a real answer instead of a guess. Tell your AI why you're making a change and it notes the reason down too, so it survives past the conversation it happened in. Available on every plan.
Filtered HubSpot searches could silently come back unfiltered if the filter conditions arrived in a slightly different shape than expected. That's fixed — a filtered search now filters, and if something about the filter still doesn't parse, you get a clear error instead of a full, unfiltered result set.
The dedup tool now works on your custom objects, not just contacts and companies. Pick a custom object — your Aufträge, Ausgaben, or whatever your portal uses — and MetaHub finds likely duplicates by name and your searchable fields, shows them side by side, and merges the ones you confirm. Available on HubSpot Enterprise portals, where custom objects live. As always, merges can't be undone, so review before you confirm.
MetaHub can now build HubSpot workflows that trigger on line-item changes — a product added to a deal, a quantity or price updated — which HubSpot doesn't offer as a native trigger. Ask your AI to automate something that should happen 'whenever a line item on the deal changes' — re-run pricing, flag the deal for review, notify the owner — and MetaHub sets up a flow that reliably picks those changes up. Line-item-driven automation that just works, no special add-ons required.
When MetaHub links two records in HubSpot — tagging a contact as the 'Billing Contact' on a company, or the 'Decision Maker' on a deal — the label you ask for now actually sticks. Custom association labels your team defined in HubSpot were sometimes rejected or applied with no label at all; MetaHub now reads your portal's exact label definitions and applies the right one every time. Ask your AI to link a contact to a deal 'as the billing contact' and the labelled relationship shows up correctly in HubSpot.
MetaHub can now assemble HubSpot workflows that include custom-code steps — it knows the exact step format, the Node runtime, and that the workflow secret must exist in your portal before the workflow is created (a missing secret used to fail with an unhelpful server error). It also knows line items can't trigger a workflow on their own, so it builds deal-triggered flows that walk the deal's line items instead. And creating a deal property now lands in HubSpot's correct built-in group on the first try; for custom objects it asks which group to file into rather than guessing wrong.
MetaHub can now put a negative-value line on a deal — a credit, rebate, or give-back — even though HubSpot won't accept a negative unit price. Ask for a line at a negative amount and it records the value as a line discount so the deal total comes out right. When a quantity is involved and it's unclear whether you mean the whole line or each unit, it asks first instead of guessing.
MetaHub can now create, edit, turn on or off, and delete HubSpot workflows for you — set up an automation just by describing it. Ask it to enroll contacts when they submit a form, wait a day, then send an email or create a follow-up task, and it assembles the whole workflow and hands you a link to review it in HubSpot. New workflows are created switched off, so nothing runs on your records until you've checked it and flipped it on. To stop a workflow it disables it rather than deleting, since a deleted workflow can't be restored without HubSpot Support.
When you ask MetaHub to link two records — or to create them already linked — without spelling out the relationship type, it now uses HubSpot's default association for that pair instead of erroring out. So 'link this contact to that company' works on its own, no need to know the association type.
You can now upload a file and attach it to a deal, contact, company, or ticket straight from your AI. The file is added through a note on the record — HubSpot's standard way of surfacing attachments. Attach by link (a Google Drive or Dropbox 'anyone with the link', or any public/signed URL) for instant, no-wait uploads, or drop a small file straight into chat. Ask 'how should I upload files?' for the best path.
Big imports into HubSpot now start with a clean-up pass. Drop your contacts, companies, or deals sheet into the dedup tool and it tidies and de-duplicates the rows for you — matching exact first, then fuzzy, and ignoring legal suffixes and industry boilerplate when it compares — then hands back an import-ready CSV with your original columns intact: the winning record kept, absorbed duplicates removed. The method is built into the playbook too — ask your AI to plan an import and it steers large files through clean-then-import, counting rows in vs. out so nothing is silently lost.
Ask your AI to design a pipeline, create properties, model a custom object, plan an import, or run any task the Metawork method covers, and it now follows a documented playbook instead of improvising. hs_playbook() lists the topics (import · pipelines · properties · tasks · data_safety · crm_choice · tools); hs_playbook(topic) returns the full method. Property-group hygiene is baked in — it checks existing groups and asks where to file before creating properties.
New hs_create_pipeline, hs_update_pipeline, hs_create_stage, and hs_update_stage tools — build or reshape a deal or ticket pipeline from the chat, with the method's data-safety guards applied so stages and their records stay intact.
Creating a task now requires associating it to the contact, company, or deal it belongs to — HubSpot won't accept a loose, unlinked task through MetaHub. Keeps your activity timeline attached to something you can actually find again.
The dedup queue is for long work — matching takes minutes, triage can take days, and the tab tends to stay open across breaks. Sessions are now a 5-day sliding window (any activity extends them) instead of a 15-minute hard cap. On top of that, the page transparently re-mints the session token if the server returns 401 — so a deploy restart or a long break no longer ends with "Session token expired" the moment you click merge.
When you connect by pasting your HubSpot Private App token directly into the dedup page (instead of going through hs_dedup), the SPA now mints a server-side session token automatically. Practical impact: merges no longer fail with "Missing session token", and the new settings UI (visible fields, match rules, audit log, export/import) shows up. Settings persist per-token, so reconnecting with the same token brings your configuration back.
When a cluster has more records (or more visible fields) than fit on screen, the comparison table now scrolls horizontally instead of squeezing columns. The field-label column on the left stays sticky as you scroll so you don't lose context.
Save a snapshot of your dedup configuration to JSON and roll back at any time — Export downloads the full license doc (team defaults + everyone's personal overrides), Import replaces it atomically with the same validation a normal save uses. The new Audit log tab records the last 50 changes (who, when, which scope, which fields) so it's easy to spot when a teammate changed something that affects everyone's queue. Import is recorded in the log too.
Each discriminator / identifier / soft signal can carry an optional condition that gates when it fires: minimum value length, non-empty, or a regex pattern (case-insensitive full match). Useful for rules like «treat customer_number as a discriminator only when it's at least 5 chars» or «promote to definite if both tax IDs match DE.+». Backward compatible — existing rules without conditions keep working unchanged.
Team-license members can now keep their own visible-field choices and match rules separate from the team defaults without forking the whole config. The settings modal grows a Team / Personal toggle: edit team defaults in the Team scope (everyone sees the change), or build a personal layer in the Personal scope that overrides the team field-by-field per entity. A Reset to team default button cleans up overrides you no longer want. Solo licenses don't see the toggle — there's no team to override.
Every team works the dedup queue differently — some live by tax ID, some by customer number, some only ever look at title and country. The new ⚙ Fields & rules modal (top of the page, also reachable from any expanded cluster) lets each license decide which fields show in the comparison view per entity, and define three buckets of match rules: discriminators (values differ → not a duplicate, cluster hidden), identifiers (values match → promoted to Definite), and soft signals (contributes to Likely/Possible). Settings are shared across the whole Team license so the queue looks the same for everyone; last-edited-by stamped so you can see who changed what.
«Brief me on Acme», «what happened with the Smith deal», «catch me up on this ticket» — hs_summarize gathers everything your AI needs to compose a coherent recap in a single tool call: entity context, activities (open + done), notes, emails, files, and (in broad scope) the history attached to the linked contact and company via HubSpot's Engagements + Associations APIs. Asks you up-front whether you want narrow (just the entity) or broad (linked records too), and recent (past 6 months) or all-history — the AI can't silently pick for you.
Large dedup runs no longer require the browser tab to stay open. Clicking «Merge this group» or «Merge selected» now hands the work off to the server — only the IDs travel, never the record content. You can close your laptop, the lid will keep merging. The dedup tab shows live progress and reattaches automatically when you come back. Job files hold only the merge plan (entity type + survivor + loser IDs) and your already-resolved API token; they auto-delete 24 hours after the job finishes so credentials don't linger on disk. Works on both MetaPipe (Pipedrive) and MetaHub (HubSpot).
New tool to create custom property groups on any object type, so onboarding a complex data model (40+ fields across products, deals, line items) no longer needs UI clickwork before properties can be filed cleanly. Also fixed hs_associate_schema_to which rejected friendly names, IDs, and FQNs — the body now sends the correct objectTypeId format and the default association name is sanitized to HubSpot's ^[a-zA-Z][a-zA-Z0-9_]*$ rule.
Same hosted browser tool as MetaPipe's pd_dedup, now for HubSpot contacts and companies. Fuzzy name matching with Levenshtein gating, E.164 phone normalization, marketplace + social-host blocklists, address gate (different city/country = sister offices not duplicates), persistent decisions across re-analyses, Flag-and-skip via Note writes, shift-click range select. Data never leaves your browser — merges call HubSpot directly via the v3 /crm/v3/objects/{type}/merge endpoints.
Ask your AI to summarize a contact, company, deal, or ticket — it pulls notes, calls, meetings, emails, tasks (and for broad scope on deals/tickets, the engagement history of associated contacts + company) and composes a recap covering what happened, what was discussed, outstanding next steps, and accomplishments. The tool asks first: narrow vs broad (engagements often live on the contact, not the deal), and recent (6 months) vs all-history.
hs_search_owners (optional open-deal-count enrichment), hs_search_properties (text search + sensitive-field gate), hs_get_portal_info, hs_campaign_report (Marketing Hub list + metrics + assets in one call).
Properties flagged with HubSpot’s dataSensitivity=sensitive are hidden from property listings by default. Pass include_sensitive=True to opt in explicitly. Matches HubSpot’s own MCP posture.
Added hs_pipeline_funnel, hs_pipeline_forecast, hs_activity_report, hs_conversion_report, hs_won_deals_report, hs_lost_deals_report, hs_new_contacts_report, hs_stale_deals, hs_user_leaderboard. Ask your AI for any common HubSpot report by name.
Same codebase, two deployments. HubSpot tools live at metahub.metawork.studio, Pipedrive at metapipe.metawork.studio. Buy what you need, no bundle pressure. Internal split via METAPIPE_SCOPE.
Drop MetaHub into ~/.gemini/settings.json with a Bearer token. Same tool surface as the Claude + ChatGPT paths.
hs_use_account / hs_list_accounts. Pipedrive and HubSpot active-account state is now decoupled per team caller — operate as client A in PD while operating as client B in HS in the same session. connect_hubspot accepts HubSpot’s newer Service Keys alongside Private App tokens.
OAuth flow in ChatGPT Settings → Connectors. Email match against your checkout account; no separate token.
hs_create_custom_object_schema, hs_associate_schema_to, hs_list_associations, hs_list_association_types, hs_disassociate. Service contracts, products, partners, projects — whatever you model, your AI can operate it.
MetaHub resolves portal-specific list names, pipeline names, and property labels server-side. Your AI doesn’t have to guess what «the re-engagement list» means in your portal.
Phase-1 launch with 31 tools covering objects (contacts, companies, deals, tickets, custom), properties, search, associations, batch reads/updates.
The AI you already pay for, doing the CRM work you'd rather not. 30 days free, then less than two hours of a specialist's time for the whole year, cancel any time.
Start 30-day free trialRunning an agency or consultancy? MetaHub also handles multi-portal dispatch, per-client credentials, and tenant-isolated team mode — the way we built it for our own client work. Contact us →