There is a thread on r/hubspot called “Anyone using HubSpot MCP?” that keeps getting bumped. There is another one called “HubSpot MCP as a RevOps operator. Looking for blunt feedback.” The blunt feedback used to be that the official MCP was read-only and too thin to change how you work.

That changed on 2026-04-13. HubSpot shipped the GA release of their Remote MCP Server with real write capabilities, and it deserves a fresh, honest look.

What the official HubSpot MCP ships today

HubSpot’s Remote MCP Server connects Claude, ChatGPT, Cursor, or any MCP-compatible AI client to a HubSpot portal over OAuth 2.1 with PKCE. It is free across all hubs and tiers, and it now does considerably more than the beta.

12 tools, read and write. The GA release covers contacts, companies, deals, tickets, products, line items, invoices, quotes, orders, carts, subscriptions, and segments. It also reads and writes engagements - calls, emails, meetings, notes, and tasks. That is a real working surface.

Search with filters. search_crm_objects returns up to 200 results per page with filter groups. You can express “all open deals in stage X owned by this rep” as one query, not a manual scavenger hunt.

Org context. The server exposes users, teams, reporting structures, owners, roles, and seats as read-only context - useful for AI that needs to understand who owns what.

Marketing reads. Campaign metrics, revenue attribution, landing pages, website pages, and blog posts are readable.

Permission-respecting. Every action respects the connected user’s existing HubSpot permissions. It is not a backdoor.

Credit where it is due: this is a genuine product, not a demo. If you need to read and update standard CRM records through an AI assistant, the official MCP now handles that.

Where it still falls short for ops teams

The gaps are not about what the official MCP does badly - they are about what it does not do at all.

No custom objects. The Remote MCP Server exposes the standard CRM object types listed above. Custom object schemas are not currently surfaced. If your portal relies on custom objects for renewals, partnerships, or product usage tracking, the official MCP cannot see or touch them.

No reviewable plans. The official MCP executes writes immediately via manage_crm_objects. There is no concept of drafting a multi-step change, reviewing it as a whole, and then executing. If the AI proposes creating twelve properties and three workflows, each step fires independently. There is no undo-as-a-batch.

One portal per connection. OAuth 2.1 authenticates one user to one portal. If you are an agency or consultant managing five portals, you need five separate connections. There is no workspace model.

No system design. You can update individual records, but you cannot design a portal configuration in conversation - pipelines, lifecycle stages, workflow logic, list criteria - and hand it off to execute as a plan. The toolset is record-level, not system-level.

Every query hits the API live. There is no local data layer. Each tool call round-trips to HubSpot’s servers. For a quick lookup that is fine. For analysis that touches thousands of records across objects, the latency and pagination add up.

Sensitive-data constraint. If your HubSpot account has “Sensitive Data” enabled, engagement objects (calls, emails, meetings, notes, tasks) are blocked from the MCP server entirely. CRM objects remain accessible, but the engagement gap can be a problem for ops teams that need email and call context.

None of these are bugs. They are product scope decisions. HubSpot shipped a solid, safe starting point - and for many teams, it is enough.

But if you are trying to run ops through a conversation, not just query records, the gap is real.

What Daeda AI adds

We built Daeda AI for the operators sitting in that gap. It is a HubSpot Marketplace app with an Automation Suite that connects your AI assistant to your portal data.

Managed data layer. Your portal data syncs to Daeda’s managed database. The AI queries that layer directly - no per-question API calls, no pagination mid-thought, no rate-limit interruptions. Cross-object queries run in seconds against the full dataset.

Write Plans with human review. When the AI proposes a change - create properties, build a pipeline, set up workflows - it drafts a structured Write Plan. That plan appears inside Daeda AI in HubSpot, where a human reviews and approves it before anything executes. No silent mutations. I wrote about how that flow works.

Custom object support. The Automation Suite syncs, queries, and updates existing custom objects in your portal.

Multi-portal from one workspace. One Daeda AI workspace can connect multiple HubSpot portals. Your AI client switches between them on demand - no reconnecting, no juggling OAuth sessions.

System-level design. Pipelines, lifecycle stages, workflows, lists, property groups, custom object schemas - all designable through conversation, all routed through the Write Plan review surface.

When to use which

Need	Use
Quick record lookups and updates across standard CRM objects	HubSpot’s official Remote MCP - free, native, solid
Cross-object analysis across thousands of records	Daeda AI - managed data layer avoids API round-trips
Human-reviewed, multi-step CRM changes	Daeda AI - Write Plans
Custom object support	Daeda AI
Multi-portal ops (agencies, consultants)	Daeda AI
System design (pipelines, workflows, lifecycle stages)	Daeda AI

They are not competitors. The official MCP is a good first-party tool for record-level work. Daeda AI is the layer you add when ops work needs planning, review, and scale.

The short version

HubSpot’s Remote MCP Server is now a real product - 12 tools, read-write across the standard CRM, free on every tier. Use it for what it is good at.

Where it stops - custom objects, reviewable Write Plans, multi-portal, system design, offline analysis - that is what we built Daeda AI for. It is on the HubSpot Marketplace. Take a look.