A
licenseB
qualityD
maintenanceA Model Context Protocol (MCP) service that enables integration with Mantis Bug Tracker, allowing users to query and analyze bug tracking data through natural language commands.
8
14 npm
12
MIT
MantisBT MCP Server
by dpesch
Related Servers
Alternatives to MantisBT MCP Server
- FlicenseNot gradedqualityDmaintenanceEnables interaction with MantisBT bug tracking systems through the REST API. Supports issue management, project access, user information, and note creation with type-safe operations.1-
Related Servers
- AlicenseAqualityDmaintenanceProvides AI assistants with direct access to MantisBT issue trackers via the REST API, enabling reading, updating, resolving, and semantically searching issues.2013 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables natural language interaction with MantisBT issues and notes via CRUD operations and semantic search.61 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Desktop and other MCP clients to browse projects and issues, create and update issues, log time, edit wiki pages, and read or save attachments on a self-hosted issue tracker through plain-language requests. It acts only with the user's own API permissions and asks for confirmation before destructive or bulk changes.MIT
- AlicenseAqualityDmaintenanceConnect Claude to your Redmine instance to search, browse, create and update issues, manage time entries, and upload/download attachments.51Mozilla Public 2.0
- FlicenseNot gradedqualityDmaintenanceEnables query and management of Zentao bugs, tasks, projects, and iterations directly from MCP-compatible IDEs like Cursor or Claude Desktop.-
- AlicenseNot gradedqualityCmaintenanceMCP server that lets clients drive a ZenTao instance through its REST API v2, exposing 119 OpenAPI-defined operations plus plan, story, and assignment query helpers for common lookups. Enables reading and writing ZenTao data — including stories, bugs, tasks, plans, users, and status transitions — directly from Codex, Claude Desktop, and other MCP clients.20 npmMIT
TDQS
A3.7/5.0
Scored across 41 tools
Disambiguation2/5
A large fraction of the surface is deprecated aliases whose functionality is already covered by newer tools: get_issues vs get_issue, list_notes/list_issue_files vs get_issue select, add_monitor/remove_monitor vs update_issue, get_project_users/versions/categories/find_project_member vs get_project, get_issue_enums/get_issue_fields vs get_issue_schema, and get_mcp_version/get_mantis_version vs get_version. The deprecation notes prevent outright confusion, but an agent must still choose between multiple tools that do the same thing, which is exactly the overlap this dimension penalizes.
Naming Consistency4/5
Nearly all tools follow a predictable snake_case verb_noun pattern (get_issue, create_issue, list_projects, add_note, delete_version). Minor deviations exist in the version tools (get_version alongside get_mcp_version/get_mantis_version) and a few noun-first resource names like list_issue_files, but the convention remains readable throughout.
Tool Count2/5
41 tools is well above the 25-tool threshold for a heavy surface, and a significant portion (roughly a dozen) are deprecated shims that duplicate newer tools. The effective useful surface is much smaller than 41, making the count poorly scoped for the server's purpose.
Completeness4/5
Core issue lifecycle is well covered: list/get/create/update/delete issues, notes, attachments, monitors, relationships, tags, versions CRUD, projects, schema, config, and metadata. Remaining gaps are minor—no attachment deletion, no project/category/tag create-update-delete tools—but agents can work around these, and the deprecated aliases still provide coverage for older clients.
Maintenance
ActivityMaintained
ResponsivenessNo issues