Connect Claude AI to AIMS360 with an MCP server. Claude reads live orders, invoices, inventory, styles, and vendor POs from your ERP and answers in plain English as a table, a chart, or an Excel export. Read-only today. Contact AIMS360 to have the connection provisioned for your tenant.
AIMS360 provides a Model Context Protocol server for Claude. Once it is connected, Claude can read your live orders, invoices, inventory, styles, and vendor purchase orders, and answer questions about sales, backlog, margin, stock, and receivables in plain English, inside the same chat where you are already writing the plan, the email, or the analysis. AIMS360 is a consumer brands ERP used by brands in fashion and apparel, footwear, jewelry, bags and accessories, cosmetics, beauty and personal care, outdoor and sporting goods, wellness and supplements, home, furniture and lifestyle, household and home care, baby and children's products, and pet products.
Request the MCP connection Book a demoYes. AIMS360 provides an MCP (Model Context Protocol) server that connects Claude AI to your live AIMS360 data. Once your connection is installed, you ask Claude a question in natural language, such as what did we ship last quarter by division, which customers are past due, or which spring styles are low on stock, and Claude answers from your real ERP records as text, a table, a chart, or an Excel export. The connection is read-only today. To get one set up, request it from AIMS360.
The same MCP server also connects Grok. Building on an open standard means the connection is written once and works wherever MCP is supported, so a team split between Claude and Grok gets the same numbers in either window.
Model Context Protocol is an open standard for connecting AI assistants to outside systems. Anthropic created it in November 2024 and donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025, so no single vendor owns it. Before MCP, every assistant needed its own 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 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 and Business Central, and a small number of other vendors have followed. Among ERPs built for apparel and consumer brands, AIMS360 is one of the few offering one, and one of the few where the same server reaches orders, invoices, inventory, styles, and vendor POs rather than sales alone. Because it is an open standard, this is how AIMS360 fits an agentic, AI-native way of running a brand without replacing the ERP underneath it.
Claude is good at working a problem through with you. AIMS360 is the only thing that knows what is true about your orders, your units, your stock, and your money. MCP is the wire between them.
Understanding the question the way a colleague would. Multi-step analysis without a new report at every step. Working the numbers into the memo, deck, or email you are already writing. Following up without you restating the whole context.
Live orders, invoices, stock, and vendor POs 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, units on hand. Every channel: DTC, wholesale, retail, and EDI dropship.
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 Claude's connector settings as a custom connector and authenticate. Works in the Claude web and desktop apps and in Claude Code. The same details work in Grok.
No query language and no field names. Claude 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. Follow-ups chain naturally: pull the top customers, ask which of their orders are unallocated, then export the list.
Prefer ChatGPT? The same ERP data is available through the AIMS360 app for ChatGPT. For a standing dashboard use Power BI, and for the finance file use Live Excel. Every connection is listed on the AI assistants hub.
The MCP server exposes read-only tools over your live AIMS360 data. Orders cover the booked side of the business, invoices cover what shipped and sold, and inventory, styles, and vendor POs cover what you have and what is on the way.
| 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 |
| Inventory and stock What you have now |
Style, color, size, season, division | Units on hand and stock position at style, color, and size grain |
| Styles The style master |
Style number, season, division, color, size range | Style record detail as it stands in AIMS360 |
| Vendor purchase orders What is on the way |
Vendor, style, season, PO number, status | Open vendor PO quantities and status |
| Record lookup One order, invoice, style, or PO |
Order, invoice, style, or PO 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, so this month against last, or the same month across three years, does not need a new report. Exact fields for inventory, styles, and vendor POs depend on your AIMS360 plan and setup, and support confirms them when the connection is provisioned.
Yes, and the design choices are deliberate. The connection is provisioned by AIMS360 for one tenant, authenticated in Claude's connector settings, and read-only. Claude receives only the rows a question needs, never a full export. Nothing about another AIMS360 customer is reachable. AIMS360 runs on Microsoft Azure with the same access controls, backups, and monitoring that protect the rest of the ERP.
Some ERP connectors let the assistant create records on day one. AIMS360 chose to ship read first, so finance and operations could trust the numbers before any assistant could change them. Write actions from Claude are on the roadmap.
| Pasting an export into a chat | AIMS360 MCP server | |
|---|---|---|
| Source | Whatever you exported this morning | Live AIMS360 orders, invoices, inventory, styles, and vendor POs |
| How current | As of the last export | As of right now |
| 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 | None today, write actions on the roadmap |
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 both Claude and Grok.
Claude's name for an MCP server you add yourself, using connection details from the vendor. That is how the AIMS360 server is installed.
The connection can query and analyze, but cannot create, edit, cancel, or delete anything in AIMS360.
Booked is what was ordered. Shipped is what left and was invoiced. Consumer brands need 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.
A purchase order you placed with a factory or supplier. Open vendor POs are what is on the way into stock.
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 Claude AI to your live AIMS360 orders, invoices, inventory, styles, and vendor purchase orders. 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.
Model Context Protocol is an open standard for connecting AI assistants to outside systems. Anthropic created it and donated it to the Agentic AI Foundation under the Linux Foundation in December 2025, so it is vendor neutral. Before MCP, every assistant needed its own integration for every tool. With MCP, AIMS360 builds the connection once and it works wherever MCP is supported, which is why the same server also serves Grok.
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 as a custom connector in Claude. There is no self-serve marketplace install today. That is deliberate: the connection is scoped to your company's data.
Not today. The AIMS360 MCP connection is read-only. Claude can look up and analyze orders, invoices, inventory, styles, and vendor POs, but it cannot create, edit, cancel, or delete records in AIMS360. Write actions from Claude, such as drafting a vendor PO, are on the roadmap and will ship with approval controls. Your approvals, permissions, and audit trail stay in AIMS360.
Orders and invoices at the grain consumer brands need: 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 inventory and stock position, style records, and open vendor purchase orders. See the reporting and inventory management pages for what sits behind each.
All of them. Beyond orders and invoices, the MCP server exposes your stock position, style master records, and open vendor purchase orders, so a question like which spring styles are low on stock and whether a PO is already open for them is answered in one chat. Exact fields depend on your AIMS360 plan and setup, and support confirms them when the connection is provisioned. Details on the vendor PO page.
The connection is provisioned by AIMS360 for one tenant, authenticated in Claude's connector settings, and read-only. Claude receives only the rows a question needs, not a full export, and nothing about another AIMS360 customer is reachable. AIMS360 runs on Microsoft Azure with the same controls that protect the rest of the ERP. See Anywhere Cloud and data backup.
That depends on your Claude plan, not on AIMS360. Anthropic's commercial products, such as Claude for Work, Enterprise, and the API, do not use customer data for model training by default. Consumer plans have a training setting the account holder controls. AIMS360 sends data only in answer to the question you asked, and never to anyone but the assistant you connected. Check your Claude plan's data terms before rollout.
The connection is scoped to your company's tenant. Ask support how it maps to your AIMS360 role-based access control when you request it, so a rep with limited screen access in AIMS360 does not see more through Claude than they would in the ERP.
Availability depends on your AIMS360 plan. Support confirms it when you request the connection. You also need a Claude plan that supports custom MCP connectors. See AIMS360 pricing or ask us.
Same ERP data, different assistant. The AIMS360 app for ChatGPT is enabled from inside ChatGPT. The Claude connector runs over MCP and is provisioned by AIMS360. Teams that draft, analyze, and write in Claude keep the numbers in that same window.
MCP connectors are supported in the Claude web and desktop apps, in Claude Code, and on the Claude Developer Platform. Which plan tiers allow custom connectors is set by Anthropic and changes over time, so AIMS360 confirms the setup that fits your environment when you request the connection.
Yes. Grok connects to AIMS360 through the same MCP server that serves Claude, provisioned by AIMS360 against your own tenant and read-only in the same way. Gemini is not supported today. Tell us which assistant your team uses and we will factor it into the roadmap. All current connections are listed on the AI assistants hub.
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. AIMS360 is a consumer brands ERP used by brands in fashion and apparel, footwear, jewelry, bags and accessories, cosmetics, beauty and personal care, outdoor and sporting goods, wellness and supplements, home, furniture and lifestyle, household and home care, baby and children's products, and pet products.
Tell us about your setup and we will provision the connection for your tenant, then walk it through on your own orders, invoices, and stock.
Request the MCP connection Book a demo
