engineering-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ENGINEERING_MCP_DB | No | Optional override for the SQLite database file path. Defaults to ~/.engineering-mcp/engineering.db. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| work_upsert_projectB | WORK: cria ou atualiza um projeto de engenharia (ex: app, backend, QA lab). Use antes de abrir tickets. |
| work_list_projectsC | WORK: lista projetos locais do Engineering MCP. |
| work_upsert_ticketB | WORK: cria/atualiza ticket (story, bug, task, spike, epic). IDs no formato KEY-N (ex: ENG-3). Passe id para atualizar status. |
| work_upsert_taskC | WORK: cria/atualiza uma task filha de um ticket. |
| work_listC | WORK: lista tickets com filtro por projeto, status, tipo ou texto. |
| work_boardC | WORK: visão kanban (backlog/todo/doing/review/done) de um projeto. |
| work_getA | WORK: detalhe de um ticket com tasks. Para pacote completo (QA+tempo+investigação) use report_ticket. |
| qa_record_runA | QA: grava um run de teste (pass/fail/flaky/blocked) ligado a um ticket. Não executa testes — para rodar, use o MCP qa-lab-agent. |
| qa_record_bugA | QA: grava um bug local (severity + classificação). Para histórico Jira corporativo use o MCP qa-oracle (search_bug_history). |
| qa_attach_evidenceC | QA: anexa log, screenshot, report ou URL a um ticket, bug ou run. |
| qa_listA | QA: lista runs, bugs e evidências. Filtra por ticket_id se informado. |
| time_estimateC | TIME: grava ou atualiza a estimativa em horas de um ticket. |
| time_logD | TIME: lança tempo trabalhado em um ticket ou task. |
| time_metricsC | TIME: estimado vs real vs restante, por ticket, projeto ou global. |
| investigate_openB | INVESTIGATION: abre uma investigação (RCA) ligada a ticket e/ou bug. Cruza WORK + QA. Para logs CI/Jira use também qa-oracle. |
| investigate_add_findingC | INVESTIGATION: adiciona observação, evidência, hipótese ou decisão a uma investigação aberta. |
| investigate_concludeB | INVESTIGATION: fecha com causa raiz e classificação (bug/flaky/infra/regression). Depois grave knowledge. |
| investigate_listC | INVESTIGATION: lista investigações, opcionalmente por ticket ou status. |
| knowledge_saveB | KNOWLEDGE: grava playbook, lição ou padrão a partir de uma investigação. Memória local (FTS). |
| knowledge_searchB | KNOWLEDGE: busca playbooks/lições por texto. Use antes de reabrir bug parecido. |
| report_ticketB | REPORTING: junta WORK + QA + TIME + INVESTIGATION + KNOWLEDGE de um ticket. Use para status, handoff ou evidência. |
| report_statusB | REPORTING: snapshot do projeto — board counts, tempo, falhas recentes, bugs e investigações abertas. |
| eng_routeA | Encaminha uma tarefa em linguagem natural para o domínio certo: work, qa, time, investigation, knowledge ou reporting. |
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 23 tools
Each tool targets a distinct resource and action (e.g., work_upsert_project vs work_upsert_ticket vs work_upsert_task). Lifecycle tools like investigate_open/add_finding/conclude and qa_record_run/record_bug are clearly separate, and the reporting and knowledge tools have unique roles. No two tools appear to do the same thing.
The naming pattern is generally domain_prefix + verb_noun (e.g., work_upsert_ticket, qa_record_run). Minor deviations include 'work_list' lacking an explicit object, 'work_board' and 'time_metrics' using nouns as commands, and 'eng_route' not following the domain-prefix structure. Overall, it's predictable and readable.
With 23 tools, the server is on the heavier side, but the count is justified by the breadth of domains covered (work, time, investigation, knowledge, QA, reporting, routing). Each tool serves a specific purpose, and the volume aligns with the comprehensive engineering management scope.
The tool surface covers the full lifecycle for tickets, tasks, projects, investigations, time tracking, and QA evidence, including reporting and knowledge handoff. Minor gaps include the absence of explicit delete or archive operations on tickets/projects, and no bulk actions, but these are not critical for typical workflows.