mcp-local-erp
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_fileC | Lê o conteúdo de um arquivo do projeto. |
| list_dirC | Lista arquivos e pastas dentro do projeto. |
| propose_changeA | Primeiro passo, obrigatório antes de qualquer write_file. Declare a feature/alteração, uma descrição objetiva do propósito, e a lista de paths (relativos à raiz do projeto) que serão criados ou modificados. Retorna um plano pendente de aprovação do usuário. |
| approve_changeA | Aprova um plano previamente proposto, liberando write_file para os arquivos declarados nele. Só chame isso depois de aprovação explícita do usuário na conversa. |
| reject_changeC | Rejeita/cancela um plano pendente. |
| list_pending_changesC | Lista planos por status: 'pending', 'approved' ou 'rejected'. |
| write_fileA | Escreve/sobrescreve um arquivo do projeto. Requer um plan_id já aprovado (via propose_change + approve_change) cujo escopo inclua rel_path. O conteúdo salvo recebe automaticamente um comentário de rastreabilidade no topo (feature, plano, data/hora). |
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 7 tools
All 7 tools have clearly distinct purposes: read/list for browsing, write for modifying, and propose/approve/reject/list_pending for managing the change-plan workflow. There is no ambiguity between them, and the propose/approve workflow is clearly chained.
Tools follow a consistent verb-based pattern: read_file, list_dir, write_file, propose_change, approve_change, reject_change, list_pending_changes. All use snake_case with verb-first naming. The only minor deviation is that 'list_pending_changes' mixes the noun 'changes' with 'list_dir' using 'dir', but this is negligible.
7 tools is well-scoped for a local ERP project server. Each tool earns its place: two for file browsing, one for writing, and four for the governance workflow around changes. No redundancy and no missing obvious categories.
The surface covers file read/write plus a complete change-approval workflow: propose, approve, reject, and list status. A minor gap is that there is no tool to retrieve or inspect a specific plan's details or diff before approving, which agents might need, but the core lifecycle is complete.