Skip to main content
Glama
bugfender

bugfender-mcp

Official
by bugfender
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to bugfender-mcp

No user-submitted related servers found.

    Related Servers

    • BountyProof MCP

      skyxtools
      A
      license
      B
      quality
      C
      maintenance
      An MCP server for authorized bug bounty work that enforces an evidence-driven workflow with session management, preflight checks, surface discovery, and verified scanning.
      12
      MIT
    • Auralogs MCP Server by auralogs-ai

      Auralogs MCP Serverofficial

      auralogs-ai
      A
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server for the Auralogs logging platform, enabling AI agents to query production logs, search errors, and retrieve AI analyses without write access. It allows you to ask your coding assistant 'what's broken in production right now?' by connecting to your logs via a simple bearer auth key.
      MIT

    • mcp-airq-cloud

      CorantGmbH
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for the air-Q Cloud API, enabling remote retrieval of air quality sensor data and historical analysis through read-only tools like listing devices, fetching readings, and exporting charts or data.
      Apache 2.0

    • bugsink-mcp

      Nshuti7
      A
      license
      Not graded
      quality
      B
      maintenance
      Hosted MCP server that exposes your self-hosted Bugsink error tracker as tools for LLMs, enabling issue management, release tracking, and stacktrace retrieval via chat prompts.
      637 npm
      MIT

    • tokenless-zendesk-mcp

      yutamago
      A
      license
      A
      quality
      D
      maintenance
      MCP server that authenticates via browser session cookies to access Zendesk's REST API without API tokens, supporting reads and writes with agent permissions.
      19
      9 npm
      1
      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

    D1.7/5.0

    Scored across 25 tools

    Disambiguation2/5

    Many tools have similar names (e.g., get_crashes, get_crash_details, get_crash_stats) and most lack descriptions, making it hard to distinguish their exact purposes. An agent would likely misselect between crash-related tools.

    Naming Consistency4/5

    The naming generally follows a verb_noun snake_case pattern (e.g., list_apps, get_crashes, search_logs). However, 'who_am_i' is an outlier that breaks the pattern, and the mix of 'list', 'get', 'search', 'count' is acceptable but slightly inconsistent.

    Tool Count3/5

    With 25 tools, the server is on the heavy side for a monitoring/tracking API. While each tool may serve a specific need, the count is borderline and could be reduced by combining related tools (e.g., crash stats into one tool with parameters).

    Completeness3/5

    The tool surface covers reading and listing for most resources (crashes, issues, feedback, logs, devices, network). However, it lacks create, update (except for issue status), and delete operations, which limits the agent's ability to manage resources fully.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources