



















































































Works out-of-box with your favorite AI agents
0
tools across every object in
InMapz
. Your agent calls the same endpoint for all of them.
Update an existing work request. Change status, priority, or details.
Submit a new work request for an asset or location. Capture the issue, requester, and priority before it becomes a work order.
Find work requests by status, requester, asset, or location. Returns the request detail and whether it has become a work order.
Update an existing work order. Change status, priority, assignee, scheduling, or completion details.
Open a new work order against an asset or location. Set priority, description, due date, and assignee.
Find work orders by status, priority, asset, location, or date. Returns assignee, schedule, and the linked asset.
Find work centers by site or status. Returns capacity, location, and the operations each can perform.
Update an existing vendor. Change profile, contact, or terms.
Create a new vendor record. Set name, contact, and payment terms.
Find vendors by name, status, or identifier. Returns supplier profile and terms.
List units of measure used for items and inventory.
List tax rates and their codes used on transactions.
Find stock records by item, location, or bin. Returns on-hand quantity, reservations, and lot or serial details.
Find spaces within sites by type or status. Returns rooms, zones, or areas used for operations or maintenance.
Find sites by name or region. Returns the physical facilities in the organization.
Find shipment orders by status, destination, or date. Returns the goods in transit and their delivery progress.
Update an existing sales order. Change lines, quantities, status, or fulfillment details.
Create a new sales order for a customer. Set line items, quantities, pricing, and delivery details.
Find sales orders by customer, status, or date. Returns order lines, quantities, pricing, and fulfillment status.
Find sales opportunities by stage, owner, or account. Returns deal value, stage, and the associated customer.
Find production routings by product or work center. Returns the sequence of operations to manufacture an item.
Find return orders by customer, vendor, or status. Returns the items being returned and the reason.
Find requests for quotation by vendor, status, or item. Returns pricing requests sent to vendors and their responses.
Update an existing receivable. Change amount, due date, or status.
Record a new receivable. Set the customer, amount, and due date.
Find receivables by customer, status, or due date. Returns outstanding amounts owed to the organization.
Update an existing receipt. Adjust received quantities or correct receipt details.
Record receipt of goods against a purchase order or transfer. Update on-hand inventory and trigger downstream payables.
Find goods receipts by purchase order, vendor, or date. Returns received quantities and their effect on on-hand inventory.
Find quotes by customer, status, or date. Returns quoted items, pricing, and validity.
Find putaway tasks by status, item, or bin. Returns where received goods are being stored.
Find internal purchase requisitions by status, requester, or item. Returns requested goods and approval status before they become purchase orders.
Update an existing purchase order. Change lines, quantities, status, or terms.
Issue a new purchase order to a vendor. Set line items, quantities, pricing, and delivery terms.
Find purchase orders by vendor, status, or date. Returns order lines, quantities, pricing, and delivery terms.
Find properties by type or owner. Returns the physical properties and facilities tracked in the system.
Update an existing production order. Change quantity, status, scheduling, or allocation.
Create a production order to manufacture a product. Set the product, quantity, and schedule.
Find production orders by product, status, or date. Returns quantities, materials, and work center allocation.
Find operations within production orders by work center or status. Returns step-level progress on the shop floor.
Find pick tasks by order, status, bin, or picker. Returns the items and quantities to pick and from where.
Find people by name or identifier. Returns individual person records across the system.
Find payments by partner, method, or date. Returns incoming and outgoing payment records.
List payment terms used on orders and invoices.
List available payment methods.
Find payables by vendor, status, or due date. Returns outstanding amounts the organization owes.
Update an existing partner. Change its type, profile, or contact details.
Create a new partner entity. Set its type, name, and contact details.
Find partner entities by type or status. Returns customers, vendors, and other trading partners in one view.
Find organizations by name or identifier. Returns the legal or operating entities in the account.
Update an existing meter reading. Correct the value or timestamp.
Record a new meter reading for an asset. Capture the value and timestamp that can trigger maintenance.
Find meter readings by meter, asset, or date. Returns recorded measurements over time.
Find meters by asset or type. Returns the measurement points tracked on equipment, such as run hours or cycles.
Find maintenance triggers by asset or condition. Returns the schedules and meter thresholds that launch maintenance.
Find maintenance templates by asset type or category. Returns the predefined task sets used to generate recurring maintenance.
Update an existing location. Change its name, type, or hierarchy.
Create a new location. Define its name, type, and place in the site hierarchy.
Find locations by name, type, or site. Returns warehouses, areas, and storage points in the facility hierarchy.
List localities such as regions or states used in addresses.
List languages configured in the system.
Update an existing journal entry. Change lines or reference before posting.
Post a new journal entry. Set the accounts, debits, credits, and reference.
Find journal entries by account, date, or reference. Returns posted debits and credits.
Find supply records for items by source or status. Returns expected incoming supply and timing.
Update an existing item. Change its attributes, category, units, or status.
Create a new item in the item master. Set its name, SKU, category, and units.
Find items by name, SKU, category, or status. Returns item master details including identifiers and units.
Update an existing invoice. Change lines, amounts, or status.
Create a customer invoice against a sales order. Set line items, amounts, and terms.
Find invoices by customer, status, or date. Returns billed amounts, lines, and payment status.
Update an existing inventory transfer. Change quantities, locations, or status.
Move inventory between locations or bins. Set the item, quantity, source, and destination.
Find inventory transfers by item, source, destination, or status. Returns quantities moving between locations.
Update an existing inventory adjustment. Correct quantities or reason codes.
Adjust on-hand inventory for an item at a location. Record the quantity change and reason.
Find inventory adjustments by item, location, or reason. Returns the quantity change and reason for each.
Update an existing fulfillment. Change quantities, status, or shipment details.
Create a fulfillment against a sales or shipment order. Record what is being picked, packed, or shipped.
Find fulfillments by order, status, or date. Returns picked, packed, and shipped quantities against an order.
List fiscal years defined in the system.
List fiscal periods within the accounting calendar.
List fiscal calendars defining the accounting year structure.
Find employees by name, role, or status. Returns employee records and assignment details.
Update an existing cycle count. Record counted quantities or change status.
Start a new cycle count for a location or bin. Define what to count and the expected quantities.
Find cycle counts by status, location, or date. Returns counted quantities versus expected on-hand.
Update an existing customer. Change profile, contact, or account details.
Create a new customer record. Set name, contact, and account details.
Find customers by name, status, or identifier. Returns customer profile and account details.
List currencies and their codes used in pricing and financials.
Find credit notes by customer or invoice. Returns credits issued against billed amounts.
List countries and their codes used across records.
Find contracts by partner, status, or date. Returns terms, value, and renewal details.
Find contacts by name, company, or role. Returns individual contact details linked to partners or accounts.
Find business units by organization or status. Returns the divisions used to segment operations and reporting.
Find budgets by period, unit, or account. Returns planned amounts for comparison against actuals.
Find storage bins by location, zone, or status. Returns bin identifiers and their place in the warehouse layout.
Find bills of materials by product or status. Returns the components, subassemblies, and quantities needed to build a product.
Find bank accounts by organization or bank. Returns the account details used for payments.
Connect once over MCP. Your agent reads data and triggers actions in InMapz, plus 2,000 other systems, without you building or maintaining a single integration.
Log in. That's the integration. Pick
InMapz
and sign in with the credentials you already use. No API keys to chase, no integration to build. Connected in under a minute.
One endpoint, scoped and logged. Makini gives you a single MCP endpoint and a token scoped to that login. The agent can only touch what those credentials allow, and every call lands on the log.
One config block, any MCP client. Paste the endpoint into Claude, n8n, LangChain, or whatever you run. Your agent gets the same tools it uses on every other system: search, get, create, update.

{
"mcpServers": {
"makini": {
"command": "npx",
"args": ["-y", "mcp-remote@latest",
"https://mcp.makini.io/UNIQUE_ID"]
}
}
}
claude mcp add --transport http makini https://mcp.makini.io/UNIQUE_ID--scope project to save the config to .mcp.json in the current directory only.
{
"mcpServers": {
"makini": {
"command": "npx",
"args": ["-y", "mcp-remote@latest",
"https://mcp.makini.io/UNIQUE_ID"]
}
}
}
{
"servers": {
"makini": {
"type": "http",
"url": "https://mcp.makini.io/UNIQUE_ID"
}
}
}
{
"mcpServers": {
"makini": {
"command": "npx",
"args": ["-y", "mcp-remote@latest",
"https://mcp.makini.io/UNIQUE_ID"]
}
}
}
{
"mcpServers": {
"makini": {
"url": "https://mcp.makini.io/UNIQUE_ID",
"disabled": false,
"autoApprove": []
}
}
}
{
"context_servers": {
"makini": {
"url": "https://mcp.makini.io/UNIQUE_ID"
}
}
}
MCP is an open standard for giving AI agents tools to act. Makini runs as a managed MCP server in front of InMapz and your wider stack. Your agent hits one endpoint, and Makini handles auth, real-time pass-through, and logging across all 2,000+ products behind it.
Makini MCP
The hard part of an agent isn't the model. It's giving it safe, reliable access to the systems that actually run the business. Makini handles that part. Connect once over MCP and your agent reads and acts on InMapz plus 2,000 other systems, with auth, scoping, and logging built in.
Your agent calls the same four tools, search, get, create, update, across all 2,000 systems. It runs real endpoints, objects, and filters, exposed in real time. Custom fields and custom objects included. No abstract data model to learn, and nothing lost in translation.
Plenty of industrial software never shipped a REST API or an MCP server, including 20-year-old on-prem systems (SAP R/3, MP2, ABS NS, CorrigoPro, etc.). Your agent reaches them anyway. Almost no other MCP provider can.
Pick a product and sign in with the credentials you already use, whether it's you, your code, or an agent over MCP. The same login flow works everywhere.
Connect to InMapz
Each connection runs on its own token and can only do what those credentials allow in the source system. Every call the agent makes is logged and searchable, so you can see exactly what it did.
Point Claude, ChatGPT, Cursor, or n8n at your endpoint with one config block. No custom adapters, no lock-in, switch clients anytime.
mcp.makini.io/v1
1 endpoint
Makini monitors every tool call and alerts you the moment one fails, with the error detail to fix it. Your agent is never quietly calling a tool that went dead.
Writing to a live CMMS or ERP is where teams get nervous, and they are right to be. Makini hands you the controls. Every connection is scoped to what its credentials can do, every call the agent makes is logged. Highest security rating from the most demanding in the business. SOC 2 Type II, UK Cyber Essentials, and GDPR compliant.
InMapz is an indoor mapping and navigation platform that digitizes facility floor plans to enable asset tracking, wayfinding and spatial visualization across warehouses, plants and large sites. With Makini's MCP server, AI agents interact with InMapz data and workflows out of the box, without any development overhead.
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 InMapz 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 the adapter, so your agent reaches those systems through the same MCP endpoint as everything else, typically in 1 day to a few weeks, regardless of how custom the system is.
Same platform, two entry points. The MCP server lets AI agents (Claude, ChatGPT, Cursor, and others) reach your systems through the Model Context Protocol. The Unified API covers traditional app and backend integrations over REST. Both expose the same normalized tools and the same 2,000+ systems behind one connection.
Yes. Enterprises connect through Makini specifically because it's more secure and takes a minute: you pick a system, log in once, and we handle the auth and token management. Credentials stay with the system of record, and your agent never has to store or rotate per-system secrets.






.webp)


