AuraVMS
Manage suppliers, send RFQs, compare supplier quotes and place purchase orders in AuraVMS.
View in the Claude registry- Brand
- Unknown
- Category
- Pending
- Primary Subcategory
- Pending
Integration details
Description
AuraVMS is procurement software for manufacturers and trading companies. This connector lets Claude work in your AuraVMS workspace: search and add suppliers, draft requests for quotation (RFQs) with line items, send them to suppliers, compare the quotes that come back with AuraVMS's L1/L2/L3 price ranking, remind suppliers who haven't responded, place purchase orders and close RFQs. Reading suppliers, RFQs and quotes never changes anything. Actions that email suppliers (sending an RFQ, reminders, purchase orders) or close an RFQ are marked so Claude asks before running them. The connector uses a key scoped to your workspace and cannot change billing, team members or organization settings. Revoke it any time under Settings > API Keys in AuraVMS.
- Integration type
- Connector
- Verification status
Community connector- Platform
- Claude
- Category
- Pending
- Primary Subcategory
- Pending
- Secondary Subcategories
- None listed
- Brand
- Unknown
- Access
- Account required
- First tracked
- 2026-09-29
- Tool count
- 10
- Geography
- US
The broad Category that contains the Primary Subcategory.
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Agent DiscoverabilityClaude Discoverability ScoreClaude Connector discovery is coming soon
Community Connectors only appear in Claude’s registry.Once verified, organic discovery begins and we can calculate your score.Read more about Community Connector verification.
No spam. Unsubscribe any time.
No spam. Unsubscribe any time.
What discovery looks like
Claude can surface verified Connectors when they match a user’s Prompt.
How Claude Connector discovery works
Your Connector will compete to appear for users’ Prompts once Claude verifies it
Competitive lineup
10 tools agents can invoke
How do I improve a Community connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.