Skip to main content
Glama
aydin-omer

Feedback Hub MCP

by aydin-omer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Feedback Hub MCP

No user-submitted related servers found.

    Related Servers

    • Customer Support Analyst MCP

      ZivSapir
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables natural-language Q&A over customer support ticket data. Provides tools for schema inspection, SQL-based ticket counts and grouping, and full-text search for customer wording without requiring API keys.
      -

    • chatwoot-mcp

      minholi
      A
      license
      B
      quality
      C
      maintenance
      Provides AI assistants with read-only access to Chatwoot analytics and operational data, including conversations, agents, inboxes, teams, CSAT, and real-time metrics.
      30
      1
      MIT

    • AxonHub MCP Server

      yunwuneo
      F
      license
      A
      quality
      C
      maintenance
      Enables AI clients to query AxonHub admin data through natural language, including instance status, projects, channels, models, requests, and usage statistics, with read-only safeguards and sensitive-field redaction.
      8
      -

    • Zendesk MCP Server

      fitcloud
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with Zendesk ticket data for customer support analysis and insights. It supports searching tickets by tags or keywords, retrieving ticket details, and analyzing agent performance and service trends.
      -

    • CRM MCP Server

      Cerennly
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables querying and managing a CRM database through natural language conversations with Claude Desktop.
      -
    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 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: get_feedback_stats returns aggregate counts and breakdowns, while list_feedback returns individual entries. An agent can easily choose between summary statistics and detailed records.

    Naming Consistency5/5

    Both names use a consistent snake_case verb_noun pattern: get_feedback_stats and list_feedback. The shared 'feedback' noun and clear verb prefixes make the naming predictable.

    Tool Count3/5

    Two tools is thin for a feedback hub server, even if the intended scope is read-only. The set feels borderline minimal rather than well-scoped for broader feedback workflows.

    Completeness2/5

    The surface only supports reading aggregate stats and listing entries. Core lifecycle operations such as submitting feedback, retrieving a single entry, updating classification/status, or resolving feedback are absent, creating significant gaps for a feedback hub.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources