MetaHub · HubSpot MCP

Give your AI the keys to your HubSpot.

Connect MetaHub MCP in Claude — or Cursor, or any MCP-compatible client. Your AI gets 31 tools (Phase 1, growing), including custom objects and vocabulary-aware property handling. Not a chat wrapper. The MCP is the interface your AI uses to call HubSpot\'s API directly.

Built by a HubSpot Solutions Partner.

Claude.ai session with MetaHub MCP connected — hs_search_objects returning a deal table
Real Claude session. Real HubSpot data. No chat wrapper in between.

Why this is different

Not a chatbot. A direct connection.

Most "AI for HubSpot" tools are chat wrappers — your prompt goes to an LLM, the LLM emits an instruction in English, a script tries to parse it back into a HubSpot API call. Custom objects break. Pipelines get hallucinated. Vocabulary like "the re-engagement list" or "the EU pipeline" gets lost in translation.

MetaHub is different. We expose HubSpot as a typed MCP tool surface — 31 tools today, each with strict schemas matching the real CRM API. Custom objects are first-class. Your portal\'s vocabulary — list names, pipeline names, property labels — gets resolved server-side, so your AI doesn\'t have to guess what "send to my onboarding sequence" means.

Chat wrapper

  • Prompt → LLM → English instruction → script tries to parse
  • Custom objects ignored or hallucinated
  • List names + pipeline names lost in translation
  • Read-mostly

MetaHub MCP

  • Typed tools your AI calls directly
  • Strict schemas — no hallucinated fields
  • Custom objects + schemas + associations as first-class tools
  • Vocabulary-aware: portal names resolve to IDs server-side

Phase 1. 31 tools today, covering objects, custom schemas, properties, search, associations, and batch ops. New tools ship continuously — every license includes the full future tool surface.

What it actually does

Three real prompts. Three real tool calls.

These are the kinds of asks your team already makes — except now your AI handles them end-to-end. Including the custom-object work that other "AI for HubSpot" tools quietly skip.

  • "Pull every deal closing this quarter where the amount is over $50k."

    hs_search_objects

    Filtered query against the deals object — returns a table with deal name, amount, close date, stage, owner.

  • "Create a custom object "Service Contract" with renewal date and ARR properties, then associate it with company 1942."

    hs_create_custom_object_schema + hs_create_object + hs_associate

    Schema defined, instance created, association written — three calls, one prompt.

  • "Find contacts at acme.com who haven't opened an email in 30 days and add them to the re-engagement list."

    hs_search_objects + hs_batch_update

    Vocabulary-aware: knows your "re-engagement" list maps to listId 42 without you telling it.

Setup

Six steps. Five minutes.

  1. 1

    Buy a license at license.metawork.studio (single or team plan).

  2. 2

    Copy your license token from the dashboard.

  3. 3

    In Claude.ai → Settings → Connectors → Add custom connector.

  4. 4

    URL: https://metahub.metawork.studio/mcp/

  5. 5

    Authorization: Bearer <your-license-token>

  6. 6

    Start chatting — your AI now has MetaHub's full tool surface.

Works in any MCP-compatible client — Claude.ai, Claude Desktop, Cursor, Continue, plus anything else that speaks the protocol. Tested in all of the above.

Pricing

One studio. Two plans.

7-day free trial on both. No bundles, no per-seat creep, no setup fees. Cancel from your license dashboard any time.

Single user

$249/mo

  • 1 license token
  • Full Phase-1 tool surface (31 tools)
  • All future tools included
  • 7-day free trial
  • Cancel anytime
Start free trial

Stop describing your CRM to your AI.

Hand it the keys. MetaHub is the same MCP we run inside our studio every day, packaged so your team can run it too.

Start 7-day free trial