









































Works out-of-box with your favorite AI agents

Bastian Solutions WMS refers to Exacta, the intralogistics software from Bastian Solutions, the Indianapolis systems integrator that Toyota Industries acquired in 2017 and that became part of Toyota Automated Logistics on April 1, 2026. Exacta spans the WMS, WES and WCS layers: inventory by location, order planning, real-time task orchestration for labor and equipment, slotting, and control of conveyors, sorters, pick-to-light and AS/RS. Distribution centers, 3PLs, food and beverage operations and manufacturers run RF-directed floor work on it.
Where a connection exposes the relevant records, the MCP lets an agent answer questions a shift supervisor would otherwise piece together from Exacta screens and reports. It can list outbound orders still waiting on picks before a carrier cutoff, find where an item is stored and how much sits in each location, or check stock against open purchase orders sent down from the host system. An inventory lead can have it pull recent adjustments for one SKU before a cycle count.
Someone with Exacta credentials signs in through Makini Link, and Makini issues an MCP endpoint to paste into Claude, ChatGPT, Cursor or another client; get_connection_details then shows which objects and fields that connection offers. Exacta is modular and configured around each site's automation, so what is exposed can vary between facilities, and on-premises servers may need Makini's IP addresses allowlisted or a VPN. Because Exacta sits between the host ERP and floor equipment, confirm which system owns orders before allowing agent writes.
Have any questions? We’re here to help You
Minutes, not a project. You point your agent at a single Makini MCP endpoint and authenticate once. There's no per-system SDK, data mapping, or integration to build on your side. That same endpoint reaches Bastian Solutions WMS and 2,000+ other EAM/CMMS, ERP, and WMS systems.
No. Makini owns the connectors. When a vendor ships an API change, deprecates an endpoint, or updates its auth, we fix it on our side. Your agent keeps calling the same tools with no rebuild, redeploy, or downtime on your end.
It still connects. Hundreds of providers in EAM, ERP, and WMS have no API or are heavily customized. Makini builds and owns adapters, so your agent reaches those systems through the same MCP endpoint as everything else.
Same platform, two entry points. MCP server lets AI agents (Claude, ChatGPT, Cursor, and others) reach your systems through the Model Context Protocol. Unified API covers traditional app and backend integrations over REST. Unified API exposes normalized data, MCP provides product-specific tools, both cover the same 2,000+ systems listed on Makini.
Yes. Many enterprises choose to connect through Makini specifically because of security. Every user is authenticated with dedicated scoped token. This comes with tool and record level permissions management even if the agent you are connecting doesn't support it on its own.
You connect AI to Bastian Solutions WMS by running Makini's MCP server in front of it. The server works with any MCP-compatible agent, so any AI can read and write Bastian Solutions WMS data without a custom build.
To get started with Bastian Solutions WMS MCP, connect Makini, authenticate Bastian Solutions WMS once, and point your agent at the MCP server. The connector and data mapping already exist, so an agent can be working with Bastian Solutions WMS the same day.
Yes. Bastian Solutions WMS has an MCP server through Makini, which hosts and maintains it. It lets AI agents connect to Bastian Solutions WMS without custom development, on SOC 2 Type II certified infrastructure.