Skip to main content
Glama

Related Servers

Alternatives to Mantis MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Integrates MantisBT bug tracker into Claude and other MCP clients via the REST API. Read and manage issues, notes, file attachments, tags, relationships, and monitors — with optional offline semantic search across all issues.
      34
      77
      7
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides issue tracking tools for Jira, Redmine, GitHub, and GitLab via the Model Context Protocol, enabling agents to search, fetch, sync, and manage issues through natural language.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables natural language interaction with MantisBT issues and notes via CRUD operations and semantic search.
      318
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Provides AI assistants with direct access to MantisBT issue trackers via the REST API, enabling reading, updating, resolving, and semantically searching issues.
      20
      16
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that enables Language Learning Models to interact with FogBugz, allowing operations like creating and updating issues, assigning cases, listing open cases, and searching through natural language.
      11
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server that integrates with Atlassian Jira to search issues, retrieve details, access comments, create new issues, and update issues.
      408
      MIT

    TDQS

    B3.2/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is some overlap between get_user, get_users, and get_users_by_project_id that could cause confusion. The descriptions help differentiate them, but an agent might struggle to choose between get_users and get_users_by_project_id when querying all users.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with 'get_' prefix, using snake_case throughout. This predictability makes it easy for agents to understand and navigate the tool set without naming conflicts.

    Tool Count5/5

    With 8 tools, the server is well-scoped for interacting with Mantis issue tracking systems. Each tool serves a clear purpose in querying issues, projects, users, and statistics, avoiding bloat while covering essential operations.

    Completeness3/5

    The tool set focuses heavily on read operations (get_*), with no tools for creating, updating, or deleting issues, projects, or users. This limits agents to querying data only, which is a notable gap for full lifecycle management in an issue tracking domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues