Mantis MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MANTIS_API_KEY | Yes | Your Mantis API key/token | |
| MANTIS_API_URL | Yes | Your Mantis instance API URL |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_issuesB | 獲取 Mantis 問題列表，可根據多個條件進行過濾，建議查詢時select選擇id,summary,description就好，資訊過多可能導致程式異常 |
| get_issue_by_idC | 根據 ID 獲取 Mantis 問題詳情 |
| get_userB | 根據用戶名稱查詢 Mantis 用戶 |
| get_projectsC | 獲取 Mantis 專案列表 |
| get_issue_statisticsC | 獲取 Mantis 問題統計數據，根據不同維度進行分析 |
| get_assignment_statisticsC | 獲取 Mantis 問題分派統計數據，分析不同用戶的問題分派情況 |
| get_users_by_project_idC | 獲取指定專案的所有用戶 |
| get_usersC | 用暴力法強制取得所有用戶 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
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.
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.
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.
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.