Skip to main content
Glama
hubspot-pipeline-mcp

hubspot-pipeline-mcp

by RynoJor

Related Servers

Alternatives to hubspot-pipeline-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Exposes CRM tools from HubSpot to Claude and other agents, enabling pipeline analysis, deal risk detection, and automated follow-up drafting.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables Claude to search, create, and update contacts, deals, and support tickets in HubSpot, and to generate cross-object account summaries.
      10
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to interact with a HubSpot CRM account via natural language, starting with read-only lookups and optionally enabling write operations like creating contacts, deals, and notes.
      11
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to build and operate HubSpot revenue operations work — workflows, lists, campaigns, sequence enrollments, owner reassignments, and record deletion — with read, build (switched off), and commit actions gated by preview-then-approve. Every write is read back from the live system and reported as verified only when the change is actually present.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables Claude and Cursor to search HubSpot contacts and deals, read recent notes, and write notes onto deals through a write tool that stays disabled until explicitly enabled. Every tool call is appended to a JSON audit log with its arguments, status, and duration.
      4
      MIT

    TDQS

    A3.6/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool targets a distinct diagnostic question (stalled deals, duplicates, stage funnel, missing fields, rep conversion, single-deal detail), so an agent can pick correctly in most cases. There is mild overlap: stalled deals appear both in find_stalled_deals and inside pipeline_summary, and get_deal re-surfaces every check, but the descriptions frame one as aggregate and the other as drill-down.

    Naming Consistency3/5

    Names mix verb-first (find_stalled_deals, find_duplicate_contacts, get_deal) with noun-first (pipeline_summary, deals_missing_fields, rep_conversion). All are snake_case and readable, but there is no single predictable verb_noun convention an agent can rely on.

    Tool Count5/5

    Six tools is well-scoped for a pipeline health/diagnostics server — one per distinct audit dimension plus a per-deal drill-down. No tool looks redundant or filler.

    Completeness3/5

    The read/diagnostic surface is strong and covers most health checks, but every workflow dead-ends: there are tools to find duplicate contacts or stalled deals yet none to merge, update, reassign, or log activity. An agent can report at-risk value but cannot remediate it.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues