What we build
A first Aras Innovator tool list, written as the manifest your IT team signs
Built on what Aras Corporation documents: any ItemType (Part, Document, CAD), relationships such as Part BOM, files and vault files, server methods, lifecycle and permissions, classification and extended properties. Backends named below are documented resources; "confirmed in blueprint" means the vendor documentation sits behind a login and the resource is checked against your release first.
# aras-innovator-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
describe_itemtypes: # -> available ItemTypes and properties in this installation
backend: GET /server/odata/$metadata
mode: read
search_parts: # number, name, state -> parts
backend: GET /server/odata/Part with $filter and $select
mode: read
get_bom: # part id -> child parts with quantities
backend: GET /server/odata/Part('id')/Part BOM with $expand=related_id (relationship name confirmed in blueprint)
mode: read
get_change_items: # part or state -> change items with workflow status
backend: OData query on your change ItemType, confirmed in blueprint
mode: read
get_documents: # part id -> related documents and files
backend: OData relationship expand, confirmed in blueprint
mode: read
propose_change_request: # part, description -> draft change item held for a person to submit
backend: POST /server/odata/<change ItemType> after confirmation
mode: propose
audit: every call logged with user, tool, arguments and the Aras Innovator response
The manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.