If you’ve spent any time reading about HubSpot AI in the last 6 months, the vocabulary has exploded. This post is the plain-English reference.

For the full pillar context: What Is HubSpot MCP? and the 5-minute executive guide.

AI Workflow Actions (BYOK)

Custom HubSpot workflow actions powered by AI. In Daeda AI’s implementation, you bring an OpenRouter API key (see BYOK below), drop an AI Workflow Action into any HubSpot workflow, and the AI’s output is automatically formatted to match the property type you’re writing to. Lets you add AI intelligence (classification, summarisation, extraction, scoring) to native HubSpot workflows without leaving the workflow builder.

Autofill CRM Card

A CRM card inside Daeda AI that analyses a record’s recent emails for property updates that may have been missed - then returns recommendations the rep can review and commit in seconds without leaving the record. Sales reps hate updating the CRM; this is the “second pair of eyes” version.

Breeze AI

HubSpot’s first-party suite of AI features inside the HubSpot UI. Covers content generation, insights, and in-record copilots. Bundled into paid HubSpot tiers. Distinct from MCP-based tooling (which lives outside the HubSpot UI). Most teams run both. See HubSpot MCP vs Breeze AI for the comparison.

BYOK (Bring Your Own Key)

An AI pricing and ownership model where you provide the model API key yourself instead of paying a marked-up per-seat fee to the vendor. In practice this usually means bringing an OpenRouter key. Benefits: you pick the model (Claude Opus, GPT-4o, Llama 3, whatever you want), pay model costs at cost, and swap models when something better ships. No lock-in.

Capability Catalogue

The browsable index at daeda.tech/daeda-ai - a live catalogue of real things teams build with Daeda AI, each with a short demo and a full walkthrough. Intended as the first landing place for new Daeda AI users.

Consultant Plan / Agency Plan

Daeda AI’s two pricing tiers. Consultant: $125/month, 1 user, 5 connected portals. Agency: $375/month, unlimited users, 5 portals. Both include a 7-day free trial, Write Plans, Workflow Actions, Autofill, and Bring Your Own Key. Add-on portals available.

daeda-mcp

An open-source npm package (not a HubSpot product) that syncs a narrow slice of your portal - contacts, companies, and deals only - to an encrypted SQLite database on your own machine at ~/.daeda-mcp/data/. Authenticates via a HubSpot private-app token with exactly four scopes (crm.export, crm.objects.contacts.read, crm.objects.companies.read, crm.objects.deals.read). Strictly read-only via its get_raw_sql tool - SELECT/WITH only, INSERT/UPDATE/DELETE/DROP blocked. Runs as npx -y daeda-mcp. Nothing leaves your machine. Purpose-built for sub-second local queries on those three objects without network round-trips. Different product, different architecture from Daeda AI. Install guide: How to install HubSpot MCP.

Daeda AI

The full Daeda app on the HubSpot Marketplace. An AI-powered HubSpot operations platform with three pillars: AI-Powered Workflow Actions (the Ask AI workflow step), the Autofill CRM Card, and the Automation Suite. The Automation Suite connects your AI assistant (Claude Desktop, Cursor, or similar) to Daeda’s managed database service - so it is not local-first; the synced portal mirror lives in Daeda-hosted infrastructure, not on your laptop. Authenticates via HubSpot OAuth with deep optional scopes, supports existing custom objects, multi-portal switching from inside your AI assistant, and builds writes as human-approved Write Plans you review and confirm in one step. Pricing on the product page.

Deep Optional Scopes

Daeda AI’s permission model. Instead of all-or-nothing app access, you explicitly grant read or write access object-by-object - Contacts, Companies, Deals, Tickets, and any custom objects. Every feature (Workflow Actions, Autofill, Write Plans) respects the same scope model.

HubSpot MCP

Shorthand for “an MCP server that talks to HubSpot”. In practice since 2026-04-13 it almost always means the first-party HubSpot Remote MCP Server (see below). Some people still use the term for third-party servers that talk to HubSpot - the free daeda-mcp npm package, Daeda AI’s Automation Suite, and a small number of others. See the pillar page for the full explainer.

HubSpot Remote MCP Server

HubSpot’s first-party hosted MCP endpoint at https://mcp.hubspot.com. Generally available since 2026-04-13, free across all hubs and tiers. Authenticates via OAuth 2.1 + PKCE (you create an MCP Auth App in HubSpot at Development > MCP Auth Apps). Exposes 12 tools and supports read and write on 12 standard CRM object types (contacts, companies, deals, tickets, carts, products, orders, line items, invoices, quotes, subscriptions, segments) and all 5 engagement types (calls, emails, meetings, notes, tasks), plus read-only access to organizational context (users, teams, roles, seats) and marketing content (campaigns, landing pages, website pages, blog posts). Respects existing HubSpot user permissions. Does not currently expose custom object schemas - that’s the clearest capability gap at GA. If Sensitive Data is enabled on the account, engagement objects are blocked from MCP access. Covered in the HubSpot MCP pillar guide and Official MCP vs daeda-mcp.

HubSpot Developer MCP Server

A separate HubSpot MCP product, not to be confused with the Remote MCP Server. Installed locally via the HubSpot CLI (hs mcp setup), generally available since 2026-02-19. Aimed at developers building HubSpot apps and CMS content inside Claude Code, Cursor, VS Code, OpenAI Codex, or Gemini CLI. Different endpoint, different setup, different audience - developers, not RevOps.

HubSpot Connector for ChatGPT

A managed install path for using HubSpot from inside ChatGPT. Uses HubSpot’s MCP machinery under the hood but is installed and managed from inside ChatGPT’s own UI (the ChatGPT workspace admin approves the connector, users re-authenticate inside ChatGPT). Supports read and write via HubSpot’s audit log, with a 10-record bulk cap per request on create/update actions. Same Sensitive Data caveat as the direct Remote MCP. Details in HubSpot’s February 2026 announcement.

Human in the Loop

An operating model where the AI drafts changes but a person reviews and approves them before they run in production. The default for any write-capable HubSpot AI tool. Daeda AI implements this as Human-Approved Write Plans (see below).

Human-Approved Write Plan

A code-executed sequence of HubSpot changes the AI drafts after you describe what you need. You read the full plan, edit in conversation, and confirm in a single step. Once approved, the changes execute against your portal - properties created, workflows updated, lists added, associations linked. The plan document itself becomes the audit record of what was built and why. The canonical alternative to “autonomous AI agents.”

MCP (Model Context Protocol)

An open standard released by Anthropic in late 2024 for connecting AI assistants to external tools and data. Think of it as the USB-C of AI tooling - one plug, any compatible device. Now supported across Claude, ChatGPT, Cursor, VS Code, and most modern AI development environments.

Multi-Portal Operations

Running the same ops workflows (audits, list building, system design, Write Plans) across multiple HubSpot portals simultaneously. Daeda AI’s plans include 5 connected portals by default, with add-on portals available. Built for agencies and consultants managing 5+ portals.

OpenRouter

A model-agnostic API gateway that lets you call any major AI model (Claude, GPT, Gemini, Llama, and many more) with a single API key. Daeda AI’s BYOK model uses OpenRouter as the provider layer so you can pick and swap models without changing tools.

Portal Audit

A point-in-time assessment of a HubSpot portal’s health - workflows, data quality, property hygiene, association gaps, ICP fit. Previously a two-hour manual walkthrough. With MCP-based tooling, it’s about ten minutes of conversation with the AI.

Private App Token

A HubSpot-generated access token from the Settings → Integrations → Private Apps flow. Used by daeda-mcp and other third-party tools to authenticate to your portal. Stored in your OS keychain, never in plaintext.

Write Operations

Changes the AI makes to your portal - creating records, updating properties, logging activities, building workflows. As of 2026-04-13, HubSpot’s first-party Remote MCP Server supports writes on standard CRM objects and engagements via its manage_crm_objects tool, respecting existing HubSpot user permissions and auditing through HubSpot’s standard audit log. daeda-mcp is still strictly read-only by design. Daeda AI’s Automation Suite goes further, building writes as human-approved Write Plans reviewed inside Daeda AI before they execute.

Missing a term?

If you hit a HubSpot AI term we haven’t covered, email us or drop it in a LinkedIn comment - we’ll add it. The HubSpot MCP pillar is the long-form companion; this glossary is the quick reference.