Skip to main content
Glama

Related Servers

Alternatives to advocatehub-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      The first full-featured MCP server for Adobe Experience Platform: 29 tools across schemas, datasets, profiles, segments, query service, and GDPR/CCPA privacy operations. Extends Adobe's read-only beta with production-grade write operations.
      65 npm
      Apache 2.0
    • 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.
      10 npm
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Custom MCP server for HubSpot CRM providing ICP segmentation, scoring, duplicate detection, Data Quality Score, and lifecycle stage automation. Exposes 39 tools to enhance HubSpot's native capabilities.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP gateway adding per-tool RBAC, tenant isolation, audit export, and PII redaction to any server.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      A governed MCP server with OAuth 2.1 + PKCE, declarative tool scoping, row-level data filters, per-identity rate limits, and a tamper-evident audit trail.
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables non-technical operations users to resolve common commerce-ops tickets, such as orders charged but failed, through an investigate, recommend, approve, and execute workflow with read-only and write tools.
      -

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation4/5

    The tools are mostly distinct: list_advocatehub_tools for discovery, configure_tenant for setup, get_active_identity_context for session context. The only potential confusion is between audit_tail and audit_search, but they are differentiated by recency vs. filtered search, and the descriptions clarify the distinction.

    Naming Consistency4/5

    All tool names use snake_case and are readable. Most follow a verb_first pattern (list_, configure_, get_), but audit_tail and audit_search place the resource (audit) before the verb, a minor deviation from the otherwise consistent convention.

    Tool Count4/5

    With five tools, the count falls within the typical 3-15 range and feels reasonable for a utility/admin-focused server. It is slightly on the smaller side given the apparent domain, but not inappropriately sparse.

    Completeness1/5

    The server name and list_advocatehub_tools description reference domain objects like members, rewards, and challenges, yet none of the actual tools perform any domain operations. The set is limited to configuration, identity, and audit utilities, leaving the core AdvocateHub functionality completely absent. Even within the meta-purpose, there is no way to modify configuration or manage audit logs beyond reading them.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing