mcp-erp-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ERP_BASE_URL | Yes | The base URL of the ERP system, e.g. https://erp.example.com. | |
| ERP_PASSWORD | Yes | Your ERP password. | |
| ERP_USERNAME | Yes | Your ERP login username/email. | |
| ERP_CONFIG_FILE | No | Optional path to a JSON file containing endpoint paths and HTML selectors. If omitted, defaults are used. |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_work_orderA | Look up a single work order by its number. Returns full structured record: status, technician, schedule, NTE, customer, location, parent WO, and the close-out fields. |
| list_pending_workB | List all pending-dispatch and in-progress work orders, optionally filtered to a single manager. |
| add_closeout_noteB | Submit a close-out note with all required fields. Validates every field; raises rather than submitting incomplete. |
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 3 tools
Each tool targets a distinct action and resource: get_work_order retrieves a single record, list_pending_work lists multiple records, and add_closeout_note submits a note. There is no overlap in purpose, making selection unambiguous.
All tool names follow a consistent verb_noun pattern in snake_case: get_work_order, list_pending_work, add_closeout_note. The verbs (get, list, add) clearly indicate the action, and the nouns are descriptive.
Three tools is on the low end for an ERP bridge, but they form a coherent subset for a specific work order closeout workflow. It is slightly under what might be expected for broader ERP work order management, but not unreasonable.
The set covers read (single and list) and one write (closeout note), but lacks create, update, delete, and broader listing operations for work orders. These gaps would cause failures for agents needing to manage the full work order lifecycle.