Mantis MCP Extension
AILABS-GmbH/mantis-mcp-extension
Endpoint MCP nativo para MantisBT 1.2.x com autenticação integrada
Ver no GitHubServidor MCP que roda dentro de uma instalação MantisBT 1.2.x em PHP 8, usando autenticação HTTP Basic Auth com a base de dados de contas do próprio Mantis. Fornece acesso via JSON-RPC aos recursos de gestão de issues sem necessidade de REST ou SOAP.
Instalação
npx convez-ai AILABS-GmbH/mantis-mcp-extension1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Integrar MantisBT 1.2.x com Claude e outros clientes MCP
- Gerenciar issues e bugs programaticamente com permissões de usuário
- Ler, criar e atualizar issues mantendo auditoria de autoria
Veredito

Solução técnica e bem-pensada para uma lacuna real: expor MantisBT 1.2.x via MCP quando SOAP está quebrado e REST não existe. Requer conhecimento em PHP e infraestrutura Mantis; documentação é clara mas público-alvo é restrito (legacies em 1.2.x).
README
A tradução para o português deste README ainda está na fila.
Mantis MCP Extension
A Model Context Protocol (MCP) endpoint that runs inside an existing
MantisBT installation — designed for MantisBT 1.2.x under PHP 8, where
the bundled SOAP API (nusoap) is broken and no REST API exists. It bootstraps
Mantis' own core.php, so it uses the database connection from
config_inc.php and the core business logic (bug_api, bugnote_api,
filters, access control) directly. No REST, no SOAP, no separate service.
https://your-mantis.example.com/api/mcp/
Running MantisBT 2.x? Use the standalone REST-based server instead: AILABS-GmbH/mantis-mcp-server. Both projects expose identical tool names and schemas, so MCP clients can switch between them transparently.
Key properties
- User-based authentication via HTTP Basic Auth. Every request carries a
Mantis username + password, verified per request through Mantis' own
auth_attempt_script_login(). All actions run as that user with their normal Mantis permissions; reporter/note author are attributed correctly. No API tokens, no cookies, no server-side sessions (stateless MCP). - PHP-8-safe around a PHP-5-era core. Error output is fully disabled and
buffered before
core.phploads (the 1.2.x core is noisy under PHP 8), and Mantis' HTML error handler is replaced by a PHP-8-correct one after loading — the same takeover the SOAP API attempted, minus itsArgumentCountError. Mantistrigger_error()business failures become clean MCP tool errors. - No cookies, guaranteed. Mantis 1.2.x starts a PHP session while loading
core.php; the extension setssession.use_cookies=0beforehand so noSet-Cookieheader ever leaves the server. - Core-level access checks. Listing uses Mantis' filter engine (only
issues the user may see); create/update/note check the configured
thresholds (
report_bug_threshold,update_bug_threshold,add_bugnote_threshold). - JSON Lines file logging with secret redaction (passwords never appear in logs).
Installation
-
Place this repository in your Mantis installation as
api/mcp/:cd <mantis-root>/api git clone https://github.com/AILABS-GmbH/mantis-mcp-extension.git mcp(or upload the files manually so that
<mantis-root>/api/mcp/index.phpexists; the extension locatescore.phptwo directories up.) -
Make
api/mcp/logs/writable by the web server user:chmod 750 api/mcp/logs -
Optional: copy
config.example.phptoconfig.phpto change the log directory or log level. -
Verify the endpoint:
curl -s -u your_user:your_password -X POST https://your-mantis/api/mcp/ \ -H 'Content-Type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
The shipped .htaccess routes requests to index.php, forwards the
Authorization header under CGI/FastCGI (common on managed hosting), and
denies direct web access to lib/, logs/ and tests/.
Connecting an MCP client
claude mcp add --transport http mantis https://your-mantis/api/mcp/ \
--header "Authorization: Basic $(printf 'your_user:your_password' | base64)"
The server is stateless: it intentionally returns no Mcp-Session-Id header,
and clients authenticate every request via Basic Auth.
Tools
| Tool | Backed by (Mantis 1.2.8 core) |
|---|---|
mantis_list_projects | current_user_get_accessible_projects() |
mantis_list_issues | filter_get_bug_rows() (permission-aware, paginated) |
mantis_get_issue | bug_get() + bugnote_get_all_visible_bugnotes() |
mantis_create_issue | BugData->create() + email_new_bug() |
mantis_update_issue | BugData->update() (history + notification mails) |
mantis_add_note | bugnote_add() |
Security notes
- TLS is mandatory in practice — Basic Auth sends credentials with every request. Never expose this endpoint over plain HTTP.
- The endpoint enforces Mantis' own per-user permissions, but anyone with a valid Mantis account can use it. Consider additional network-level restrictions if your Mantis instance is internet-facing.
logs/andtests/are denied via.htaccess; keep it that way and rotate/clean logs as needed.
Compatibility
- Target: MantisBT 1.2.8 (all core calls verified against the 1.2.8 source); should work on other 1.2.x releases with the same API surface.
- PHP: 8.x (developed against 8.5). The extension shields itself from the old core's PHP 8 warnings; it does not patch Mantis itself.
- Web server: Apache (
.htaccessshipped). For nginx, route the location toindex.phpand pass theAuthorizationheader.
Testing without a Mantis installation
tests/mock-mantis-core.php mocks the 1.2.8
core API surface including the old core's quirks (load-time warnings, HTML
error handler, session_start(), trigger_error() failures):
MANTIS_MCP_CORE_PATH="$PWD/tests/mock-mantis-core.php" php -S 127.0.0.1:8095 -t .
curl -s -u jdoe:secret -X POST http://127.0.0.1:8095/index.php \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Mock users: jdoe:secret (full access), viewer:viewpw (read-only).
Contributing
Contributions are welcome — please read CONTRIBUTING.md. If you use an AI coding assistant, see AGENTS.md.
License
Released under the MIT License.