Skip to main content
Glama
M-Pineapple

hubspot-auditor

by M-Pineapple
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to hubspot-auditor

No user-submitted related servers found.

    Related Servers

    • hubspot-mcp

      MCPForgeHQ
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for the HubSpot CRM API with tools for managing contacts, companies, deals, tickets, and CRM workflows. Generated with MCPForge. Sensitive operations can be protected with permissions, audit logs, and approval workflows.
      12 npm
      MIT

    • mcp-hubspot

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      HubSpot MCP server that enables browsing and searching contacts, companies, and deals in your HubSpot workspace.
      405 npm
      MIT

    • hubspot-mcp

      MBAD753
      A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server that exposes HubSpot CRM data (contacts, deals, companies, quotes) to AI agents, enabling natural language queries.
      9
      MIT

    • mcp-hubspot

      kaael1
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that uses a browser extension to interact with HubSpot through the logged-in browser, enabling reading, searching, creating, and updating HubSpot records without API tokens.
      8 npm
      -

    • HubSpot MCP Server

      fagun04
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that exposes HubSpot CRM operations as tools over stdio, enabling any MCP client to query and modify HubSpot data.
      642 npm
      MIT

    This server cannot be deployed

    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.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: list_checks enumerates available versioned audit checks, while run_audit executes an audit. An agent cannot reasonably confuse discovery of checks with execution of the audit.

    Naming Consistency5/5

    Both names follow a consistent verb_noun pattern (list_checks, run_audit) with matching snake_case convention. There is no deviation or mixed style.

    Tool Count4/5

    Two tools is on the thin side, but the server's stated scope is a narrow read-only audit, so discovery plus execution is a reasonable minimal surface. It could justify one or two more tools (e.g. retrieving past results) but nothing feels missing for the core purpose.

    Completeness4/5

    For a read-only auditor, listing checks and running them covers the essential lifecycle with no CRUD expectations. Minor gaps exist around inspecting individual check definitions or retrieving historical results, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources