auravms-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AVMS_API_KEY | Yes | Your AuraVMS API key, created at app.auravms.com under Settings > API Keys |
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 |
|---|---|
| list_suppliersA | Search or list suppliers in the AuraVMS account. Use before add_supplier (supplier emails are unique) and to collect supplier UUIDs for create_rfq. |
| add_supplierA | Add a new supplier to the AuraVMS account. Searches for the email first (supplier emails are unique — re-adding an existing vendor fails). Returns the supplier UUID to use in create_rfq. |
| create_rfqA | Create an RFQ in AuraVMS. SAFETY: by default this saves a DRAFT and emails nobody. Pass send:true ONLY after the user has explicitly confirmed — sending emails a zero-signup quote link to every invited supplier. Supplier IDs come from list_suppliers / add_supplier. |
| list_rfqsA | List RFQs (filter by status open/closed, search, paginate). Pass rfq_id to get one RFQ's items and per-supplier response status (has_responded / is_declined — answers 'who hasn't responded?'). Item ids feed get_quotes. |
| get_quotesA | Pull all supplier quotes for one RFQ line item, with AuraVMS's native L1/L2/L3 price ranking (L1 = lowest quoted price). Returns per-supplier price, lead time, remarks, response_id (needed by place_order) and rank_label. L1 is price-only — still weigh lead time, payment terms and deviations before recommending an award. |
| place_orderA | Place the purchase order on a winning quote. SAFETY: this is a purchase commitment and emails a PO to the supplier — it refuses unless confirm:true is passed after the user has explicitly approved this exact order. bought_quantity/bought_price default to the quoted values; only override deliberately (negotiated price, split award). |
| send_remindersA | Email a reminder to suppliers who haven't responded to an RFQ. Omit supplier_ids to remind all non-responders. SAFETY: throttled to once per RFQ per 24 hours — chasing more often weakens the buyer's position. |
| close_rfqA | Close an RFQ once awards are placed (or the sourcing round is abandoned). Suppliers can no longer submit quotes after closing. |
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 8 tools
Each tool has a distinct purpose: adding suppliers, creating/closing RFQs, viewing quotes, listing RFQs and suppliers, placing orders, and sending reminders. No two tools overlap in function.
All tool names follow a consistent verb_noun pattern in snake_case: add_supplier, close_rfq, create_rfq, get_quotes, list_rfqs, list_suppliers, place_order, send_reminders. No mixing of conventions.
8 tools cover the core RFQ workflow well. Not too few to be trivial, not too many to be overwhelming. The count is appropriate for the domain.
The tool set covers the complete RFQ lifecycle: supplier management, RFQ creation/closing, quote retrieval, order placement, and reminders. Minor gaps like updating suppliers or RFQ items are present but do not hinder the primary workflow.