Skip to main content
Glama
mcp-erp-server

mcp-erp-server

by aldemarluz

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ERP_PROFILEYesAccess profile that determines which departments' tools are registered and at what level (none / read / write). Known profiles: `director` (read on sales, procurement, finance, inventory), `sales_manager` (write on sales, read on finance and inventory), `sales_rep` (read on sales and inventory), `buyer` (read on procurement and inventory). Passed to the server via the ERP_PROFILE environment variable.

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
sales_find_customerB

Search customers by name, id or tax id. Returns tier and city.

sales_list_ordersB

List sales orders, optionally filtered by status and customer. Totals are computed from the lines.

sales_get_priceC

Price of a product for a customer's tier, and whether it is above the floor price.

sales_update_order_statusA

Move a sales order to a new status. Without confirm=true this only returns a preview (dry run). Only valid transitions are accepted.

finance_receivablesC

Open and overdue invoices, with totals.

inventory_stockC

On-hand, reserved and available quantity per product and location.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a distinct resource and action: customer lookup, order listing, price lookup, order status transition, receivables, and stock levels. No two tools could plausibly be confused for one another, and the domain prefixes further separate sales, finance, and inventory concerns.

Naming Consistency4/5

The pattern is namespace_verb_noun (sales_find_customer, sales_list_orders, sales_update_order_status), applied consistently within the sales namespace. The finance_receivables and inventory_stock tools drop the verb and read as nouns, a minor but noticeable deviation from the rest of the set.

Tool Count4/5

Six tools is a lean, well-scoped surface where each tool maps to a clear question an ERP assistant would ask. It is on the thin side for a system as broad as an ERP, but nothing feels padded or redundant.

Completeness3/5

The set covers read paths for customers, orders, pricing, receivables, and stock, plus one guarded write (order status). However, there is no order creation, no customer or inventory write operations, and no invoice or line-item detail retrieval, leaving notable gaps for a full ERP lifecycle.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues