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
26 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.2015 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables natural language interaction with MantisBT issues and notes via CRUD operations and semantic search.42 npm1MIT
- 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.-
- AlicenseAqualityBmaintenanceEnables AI assistants to manage Redmine issues, projects, time tracking, wiki, and files via the MCP protocol.3353 npm5Apache 2.0
- FlicenseAqualityCmaintenanceExposes Zentao REST API as MCP tools for listing/searching bugs, reading details with screenshots, and resolving bugs after explicit confirmation. Includes a setup wizard to configure Codex, Claude, Cursor and other clients.5-
TDQS
A3.7/5.0
Scored across 38 tools
Disambiguation4/5
Most tools target a distinct resource+action pair (issues, notes, files, relationships, monitors, versions, tags), and descriptions explicitly clarify boundaries like get_issue vs get_issues vs list_issues, or list_notes vs the notes embedded in get_issue. The only real overlap is among the metadata tools (sync_metadata, get_metadata, get_metadata_full) and get_mcp_version vs get_mantis_version, but these are still reasonably separable.
Naming Consistency4/5
The set overwhelmingly follows a predictable verb_noun snake_case pattern (get_issue, create_issue, delete_version, add_monitor, remove_relationship, list_projects). Minor deviations exist such as find_project_member (find vs get), release_version, and the singular/plural mismatch between attach_tags and detach_tag, but these do not impede reading.
Tool Count2/5
At 38 tools this is well above the 25-tool threshold where a surface starts to feel heavy for the apparent scope. While MantisBT is a broad domain, several tools are near-duplicates (get_metadata, get_metadata_full, sync_metadata; get_mcp_version vs get_mantis_version) and could be consolidated, so the count is over-scoped.
Completeness4/5
Coverage is strong: full CRUD for issues, notes, versions, relationships, and monitors, plus files, tags, config, enums, users, and a metadata cache. A few management operations are missing (no create/list-update for projects or categories, no single note fetch/update), but core agent workflows are fully served.
Maintenance
ActivityMaintained
ResponsivenessNo issues