Connect Grok to AIMS360 with an MCP server. Grok reads live orders, invoices, styles, inventory, customers, sales and margin from your ERP and answers in plain English, as a table, a chart or an Excel export. Creating and updating orders, customers and styles from the chat works today, within the No access, Read or Write access each person has by area; allocation and invoicing from the chat are coming soon. Contact AIMS360 to have the connection provisioned for your tenant.
AIMS360 provides a Model Context Protocol server for Grok. Once it is connected, Grok can read your live orders, invoices, styles, inventory and customers and answer questions about sales, backlog, margin and receivables in plain English, without anyone exporting a report first. The AI connection launched in the June 2026 release.
Request the MCP connection Book a demoYes. AIMS360 provides an MCP (Model Context Protocol) server that connects Grok to your live AIMS360 orders, invoices, styles, inventory and customers. Once your connection is installed, you ask Grok a question in plain English, such as what did we ship last quarter by division, which customers are past due, or margin by style for spring, and Grok answers from your real ERP data as text, a table, a chart or an Excel export. It creates and updates orders, customers and styles from the chat, within the No access, Read or Write access an admin sets for each person by area, and allocation and invoicing from the chat are coming soon. To get the connection set up, request it from AIMS360.
The practical difference is who gets to ask. Reporting in most ERPs is a skill: you have to know which report, which filters, which date field. With a connector, anyone who can type a sentence can get the number, and the number comes out of the system of record rather than out of a model's guess.
The Grok connection and the Claude connection are the same AIMS360 MCP server. That is the whole point of building on an open standard: AIMS360 writes the connection once and it works wherever MCP is supported. A team split between Grok and Claude sees the same orders, the same invoices and the same numbers, in whichever window they happen to be working.
Understanding plain-English business wording. Resolving last quarter, my top accounts, the fall line. Chaining steps without you restating the context. Turning the result into a summary, a table or a chart.
Live orders, invoices, styles, inventory and customers from your own tenant, at style, color and size grain. Booked versus shipped kept separate so sales means the right thing. Margin percent, average unit retail, units back-ordered. Every channel: DTC, wholesale, retail and EDI dropship.
Model Context Protocol is an open standard for connecting AI assistants to outside systems. Before MCP, every assistant needed a bespoke integration for every tool. With MCP, AIMS360 builds the connection once and it works wherever MCP is supported. For an ERP that means the assistant is reading your actual records instead of working from whatever you remembered to paste in.
MCP support in ERP is still early. Microsoft has shipped MCP servers for Dynamics 365 finance and operations and for Business Central, and other vendors have followed, including some that sell to apparel and consumer brands, so ask each vendor what its AI connection can read and do. AIMS360 runs its own MCP server, so Grok, Claude, ChatGPT and Gemini all connect to live AIMS360 data.
There is no public marketplace install. AIMS360 provisions the connection for your tenant, which is what keeps it scoped to your company's data.
Ask for the AIMS360 MCP server connection through the contact form. Support confirms your tenant and your plan.
The server is scoped to your company's AIMS360 data. Nobody else's records are reachable.
Paste the connection details into Grok's connector settings and authenticate. The same details work in Claude.
No query language and no field names. Grok reads live AIMS360 data and answers in the chat.
These are not canned reports. They are examples of wording that works, because AIMS360 resolves business language to the right fields behind the scenes.
“What did we ship last quarter, by division?” “Margin by style for the spring line.” “Which customers are past due, and by how much?” “Open backlog by season, oldest first.” “Compare this month to the same month last year.” “Units shipped by size for our top ten styles.”Prefer ChatGPT? The same ERP data is available through the AIMS360 app for ChatGPT, and every connection is listed on the AI assistants hub.
The MCP server exposes tools over your live AIMS360 data. Today they read orders, invoices, styles, inventory, customers, cut tickets, pick tickets and RMAs, and create and update orders, customers and styles. Creating and updating orders and customers from the chat arrived in the November 2026 release, and style setup, style lookups, cut tickets, pick tickets and RMAs were added later that month. Tools for allocation and invoicing are coming soon. Orders cover the booked side of the business; invoices cover what actually shipped and sold.
New in November 2026.
Still coming. Easier sign-in, planned for version 26.12.02 (December 2026), connects ChatGPT and Claude without typing in client credentials. Allocation and invoicing from the chat are coming soon. See what's coming on What's New.
| Area | Break it down by | Measure it in |
|---|---|---|
| Orders Booked and open backlog |
Customer, style, color, size, style/color/size, season, division, sales rep, ship-to state, order source, payment terms, carrier, buyer, vendor, cancellation reason, entered / start / complete date | Ordered amount, open amount, shipped amount, cancelled amount, order count, units booked, units cancelled |
| Invoices Shipped, sold and billed |
Customer, style, color, size, style/color/size, season, division, sales rep, bill-to and ship-to state, order source, Shopify store, payment terms, carrier, invoice date, due date | Total amount, merchandise, balance, invoice count, units shipped, units back-ordered, margin %, average unit retail |
| Record lookup One order or invoice |
Order number or invoice number, with line-item and per-size expansion | Full header and line detail, allocations, back-order position |
Built-in shortcuts cover what operators ask most: overdue orders, orders with no allocation, overdue invoices, and outstanding balance. Period-over-period comparison is built in as well, up to twelve periods, so this month against last, or the same month across three years, does not need a new report.
| Pasting an export into a chat | AIMS360 MCP server | |
|---|---|---|
| Source | Whatever you exported this morning | Live AIMS360 orders, invoices, styles, inventory and customers |
| How current | As of the last export | As of right now |
| Apparel grain | Whatever fit in the spreadsheet | Style, color, size, season, division |
| Follow-up question | New export | Just ask |
| Data leaving your control | A full file, every time | Only the rows the question needs |
| Write access | N/A | Creates and updates orders, customers and styles, only where the user has Write access; allocation and invoicing coming soon |
The row about data leaving your control is the one most teams underweight. Pasting a full export into a chat window sends far more than the question required. A scoped connection sends only the rows the question actually needs.
Model Context Protocol. An open standard for connecting AI assistants to external systems, created by Anthropic and now governed by the Agentic AI Foundation under the Linux Foundation.
The service that exposes a defined set of tools an assistant can call. AIMS360 runs one against your ERP data, serving Grok, Claude and Gemini.
Each person authenticates as themselves, so the connection can see and do only what that person's AIMS360 role allows.
Booked is what was ordered. Shipped is what left and was invoiced. Apparel needs both, and they are not the same number.
Stock or work-in-progress committed to an order. Open orders with none are backlog at risk.
Average unit retail. Total dollars divided by units sold, at whatever grain you asked for.
Yes. AIMS360 provides a Model Context Protocol server that connects Grok to your live AIMS360 orders, invoices, styles, inventory and customers. It is not a public download. AIMS360 provisions the connection for your tenant. Request it through the AIMS360 contact form and support will set it up.
It is the same MCP server. Model Context Protocol is an open standard, so AIMS360 builds the connection once and it works wherever MCP is supported. Grok, Claude and Gemini read the same live orders, invoices, styles, inventory and customers, at the same grain, with the same No access, Read or Write limits for each person by area. The only difference is which assistant you are typing into.
Model Context Protocol is an open standard for connecting AI assistants to outside systems. Before MCP, every assistant needed a bespoke integration for every tool. With MCP, AIMS360 builds the connection once and it works wherever MCP is supported. For an ERP that means the assistant is reading your actual records instead of working from whatever you remembered to paste in.
Yes. Grok supports custom MCP connectors. You add one at grok.com/connectors by choosing New Connector, then Custom, and entering the server URL, and the server has to be reachable over the internet. The AIMS360 MCP server is hosted by AIMS360, so there is nothing to run yourself. On Grok Business and Enterprise, a team admin provisions the connector first.
Yes, for orders, customers and styles. Grok looks up and analyzes orders, invoices, styles, inventory, customers, cut tickets, pick tickets and RMAs, and it can create and update orders, customers and styles from the chat, with a preview before anything saves. Allocation and invoicing from the chat are coming soon. Each person can only change the areas their admin set to Write in AIMS360 User Setup, part of AIMS360 role based access, so Grok cannot do anything that person could not do by signing in directly.
Yes. An admin sets each person to No access, Read or Write for each area, such as orders, customers, styles, inventory and purchase orders, in AIMS360 User Setup. Grok only sees the tools for the areas that person can reach and can only change areas set to Write, and every change still shows a preview and waits for a yes. API access has to be on for that person in User Setup before Grok can connect at all.
Sign-in for ChatGPT and Claude without typing client credentials is planned for version 26.12.02 in December 2026, and allocation and invoicing from the chat are coming soon. Style setup from the chat, style lookups, cut tickets, pick tickets and RMAs arrived in November 2026.
Orders, invoices, styles, inventory and customers, at the grain apparel needs. Booked, open, shipped and cancelled amounts. Units booked, shipped and back-ordered. Margin percent and average unit retail. Grouped by customer, style, color, size, season, division, sales rep, channel, Shopify store, carrier, payment terms or ship-to state. Plus built-in patterns for overdue orders, unallocated backlog, overdue invoices and outstanding balance.
Request the AIMS360 MCP server connection through the AIMS360 contact form. Support provisions it against your tenant and sends you the connection details to add in Grok. There is no self-serve marketplace install today, which is deliberate. The connection is scoped to your company's data.
xAI lists connectors as available to all Grok users. On Grok Business and Enterprise, a team admin has to provision a connector in the console before members can use it. AIMS360 will confirm the setup that fits your environment before provisioning, so nobody spends a week discovering a plan limit.
Data handling is governed by your own workspace settings with the assistant provider and by your agreement with AIMS360. Business and enterprise workspaces are generally not used to train models by default. Confirm the specifics for your plan with the provider and with AIMS360 before rolling it out company-wide. See also how AIMS360 handles data security.
Every channel. The data behind it is your AIMS360 ERP, which already runs DTC, wholesale, retail and EDI dropship to major retailers in one system, so the answers span all of them rather than one storefront.
Tell us about your setup and we will provision the connection for your tenant, then walk it through on your own orders, invoices, styles, inventory and customers.
Request the MCP connection Book a demo