Create RFQs, compare supplier quotes with L1/L2/L3 ranking, and place purchase orders.
Auravms MCP server exists for a simple reason — assistants are far more useful when they can act on Auravms directly instead of describing what you should do. Create RFQs, compare supplier quotes with L1/L2/L3 ranking, and place purchase orders.
Say "send an RFQ for 2,000 kg of SS304 sheet to my steel suppliers, delivery Mumbai by Aug 15" and the agent does the whole cycle.
Once Auravms is connected, these are the calls the assistant has available:
list_suppliers — Search/list suppliers; collect UUIDs for RFQsadd_supplier — Add a vendor (dedupes by email first)create_rfq — Create an RFQ — draft by default; send: true emails the invited suppliers their quote linkslist_rfqs — List RFQs (open/closed, search); with rfq_id, shows items + who has/hasn't respondedget_quotes — Per-item quotes with native L1/L2/L3 ranking, lead times, remarkssend_reminders — Nudge non-responders — throttled to once per RFQ per 24hplace_order — Place the PO on a winning quote — requires confirm: trueclose_rfq — Close out the sourcing roundauravms-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need one environment variable: AVMS_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Auravms's toolset — list_suppliers, add_supplier, create_rfq and 5 more — is a fair guide to whether it matches your workflow. It is maintained by dann26parr69; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| list_suppliers | Search/list suppliers; collect UUIDs for RFQs |
| add_supplier | Add a vendor (dedupes by email first) |
| create_rfq | Create an RFQ — **draft by default**; send: true emails the invited suppliers their quote links |
| list_rfqs | List RFQs (open/closed, search); with rfq_id, shows items + who has/hasn't responded |
| get_quotes | Per-item quotes with native L1/L2/L3 ranking, lead times, remarks |
| send_reminders | Nudge non-responders — throttled to once per RFQ per 24h |
| place_order | Place the PO on a winning quote — **requires confirm: true** |
| close_rfq | Close out the sourcing round |
{
"mcpServers": {
"auravms": {
"command": "npx",
"args": ["-y", "auravms-mcp"],
"env": {
"AVMS_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| AVMS_API_KEY | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.