mcp-mantis
Related Servers
Alternatives to mcp-mantis
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceIntegrates 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.34146 npm8MIT
- AlicenseNot gradedqualityAmaintenanceEnables natural language interaction with MantisBT issues and notes via CRUD operations and semantic search.50 npm1MIT
- FlicenseNot gradedqualityCmaintenanceEnables interaction with MantisBT bug tracking systems through the REST API. Supports issue management, project access, user information, and note creation with type-safe operations.2-
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to find and manage Redmine tickets via the Redmine REST API, supporting issue listing, details, updates, and comments.7 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Redmine instances to manage issues, projects, and users. It provides comprehensive tools for issue tracking, project oversight, and user management through the Redmine REST API.13 npmMIT
- AlicenseCqualityDmaintenanceEnables AI assistants to interact with Redmine instances, managing issues, projects, and metadata through natural language commands.123 npmMIT
TDQS
Scored across 20 tools
Each tool has a clearly distinct purpose. Even similar tools like `get_issue` vs `get_issues` and `update_issue` vs `resolve_issue` have well-defined differences explained in descriptions, so an agent can reliably choose the correct one.
All tools start with 'mantis_' and follow a verb_noun pattern (e.g., mantis_add_note, mantis_list_issues). The only slight deviation is mantis_whoami, but that's a common convention. Overall, naming is highly consistent and predictable.
20 tools cover a wide range of operations for a bug tracker: reading, updating, searching, relationships, attachments, enumerations, etc. The count is appropriate for the domain without being overwhelming.
The tool set lacks fundamental CRUD operations. There is no create_issue or delete_issue, and no tools to create/update/delete projects or filters. This creates significant gaps that will cause agent failures when these operations are needed.