EngiMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| engi_project_statusC | Return a concise EngiMCP project status. |
| engi_project_mapC | Return a tree/map of managed Markdown documents. |
| engi_doc_readB | Read a managed Markdown document by ID or path. |
| engi_doc_createC | Create a Markdown document from a template. |
| engi_frontmatter_patchC | Patch YAML frontmatter for a managed document. |
| engi_doc_patch_sectionC | Patch a Markdown section by heading path. |
| engi_validate_projectB | Validate IDs, frontmatter, and basic document relationships. |
| engi_graph_queryB | Return graph neighbors for a document or entity. |
| engi_impact_analyzeC | Analyze transitive document impact for changed IDs. |
| engi_requirement_createC | Create a requirement document with the next typed requirement ID. |
| engi_decision_createC | Create an Engineering Decision Record. |
| engi_task_createC | Create a project task document. |
| engi_context_packC | Build compact task-specific context from project documents. |
| engi_git_statusC | Return Git dirty status and changed files. |
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 14 tools
All tools have clearly distinct purposes: context packing, decision creation, document CRUD, git status, graph queries, impact analysis, project mapping, status, requirement and task creation, and validation. No overlapping responsibilities.
Most tools follow a noun_verb pattern (e.g., engi_decision_create, engi_doc_read) with a consistent 'engi_' prefix. However, 'engi_validate_project' breaks the pattern by using verb_noun order, and 'engi_git_status', 'engi_project_map', 'engi_project_status' are noun_noun. Overall, inconsistency is minor.
14 tools is well-scoped for an engineering documentation and project management server. Each tool covers a distinct operation without excess, and the count aligns with the domain's typical needs.
The toolset covers document CRUD (except delete) and creation of decisions, requirements, and tasks, but lacks update/delete for the latter three. Impact analysis and graph queries are advanced, but missing lifecycle operations for core entities are notable gaps.