Skip to main content
Glama
TNE736

LQABR MCP HubSpot Server

by TNE736
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to LQABR MCP HubSpot Server

No user-submitted related servers found.

    Related Servers

    • HubSpot MCP Server

      djmoore-projects
      A
      license
      A
      quality
      C
      maintenance
      Exposes HubSpot CRM data and actions as tools for AI agents, enabling contact lookup, company search, contact creation, and activity logging via natural language.
      4
      245 npm
      MIT

    • LQABR HubSpot MCP Server

      bsmahi
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with HubSpot CRM through two tools (upsert_lead_profile and get_lead_profile) for managing lead profiles, using FastMCP with Secret Manager-based authentication and supporting both stdio and HTTP transports.
      -

    • HubSpot MCP Server

      blackhole2100
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with HubSpot CRM data, providing tools for managing contacts and companies, retrieving activity and conversations, and performing semantic search with vector storage and caching for improved performance.
      MIT

    • BackCrew HubSpot MCP Server

      jayson-svg
      A
      license
      B
      quality
      B
      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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 4 tools

    Disambiguation2/5

    The tools clearly separate lead and blog summary domains, but within each domain the upsert and get tools have high semantic overlap in purpose, though descriptions help distinguish read vs. write.

    Naming Consistency4/5

    All tool names follow a consistent verb_noun pattern (upsert/get + lead_profile/blog_summary) with snake_case, very predictable. Minor point: 'upsert' is a valid term but less common than 'create_or_update'.

    Tool Count4/5

    4 tools is a reasonable count for a focused HubSpot integration covering two entities (lead and blog summary) with basic CRUD. It's slightly thin but appropriate for a narrow scope.

    Completeness3/5

    Coverage is incomplete: lead profiles have upsert+get but no ability to delete or list/filter leads. Blog summaries similarly lack delete and listing. The domain surface has notable missing operations that could hinder workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources