Armaor MCP: Connect AI Agents to Armaor, With Approval and Audit

Key takeaways

• Nobody offers a public Armaor MCP server yet. Contro1 gives your AI agents the Armaor actions through its own MCP server and API.
• Armaor stays inside your network. A small connector on its server links it to Contro1, with no open ports and no VPN.
• You choose each Armaor action per agent. Reads run on their own, and putting an order in production can wait for one or two people.
• One agent works in Armaor and Priority together. Every call in both lands in one record of who asked, which agent and who approved.

Armaor MCP: what it is

Armaor, the rebar production software from Ariadis, runs on a server inside the plant: orders, BBS lines, production planning, cutting tags, stock, deliveries. Its Web API answers only on the plant network, and it has no MCP server of its own.

So an AI agent cannot ask Armaor "which orders are late" or "put this order in production". Someone still opens Armaor, looks it up and types it in, and then types the same thing again in the ERP.

Contro1 serves Armaor's operations as tools on the Contro1 MCP server. Claude, ChatGPT, Microsoft Copilot, Cursor or an agent you build calls them like any other tool. A connector installed on the Armaor server runs each call inside your network.

Before anything runs, Contro1 checks which agent is calling, for whom, and whether that agent may use that action. Where you said so, a person approves first. Every call is recorded.

Watch it in the agent capsule: Armaor added to an agent that already works in Priority, each action chosen, approval set, approved, and on the record.

How an AI agent reaches an Armaor server inside the plant

Armaor stays where it is, on your own server, on-prem or self-hosted in your cloud. You install a small connector on that server, or on another always-on server that reaches it. The connector opens a secure outgoing connection to Contro1 and waits for work.

When an agent calls an Armaor action, Contro1 checks the grant and the policy, waits for approval if needed, and hands the signed job to the connector. The connector calls Armaor at its local address, for example http://127.0.0.1:3001, and returns the answer.

Installing the connector, on a Windows server:

Connect AI agents to internal and on-prem applications, with install steps for IT

What an agent can do in Armaor

These are the Armaor Web API operations Contro1 reviewed at its first Armaor install: 68 operations, 32 that read, 30 that write and 6 that delete. Each one has its effect and risk set, and none runs for an agent until someone allows it in Access. Your Armaor version may expose more or fewer; we check yours before you publish.

A sensible start for most plants:

Ariadis: Armaor rebar software

Armaor and Priority (or any ERP) in one agent

Most Armaor plants also run an ERP. In Israel that is often Priority; elsewhere SAP Business One, Microsoft Dynamics or something else. Today the two meet through a person retyping, or a sync nobody wants to touch.

An agent can work in both, with the same controls. In the clip, Production Planner already has three Priority actions; Armaor is added beside them. Each system keeps its own grants and approvers, and both appear in one record.

Priority and the other systems are connected as your own applications: on your server through the same connector, or in the cloud. Tell us which ERP you run and we will check its API with you.

See who touched what in Armaor

Armaor's own log shows that the API user changed an order. It cannot show which agent did it, for which person, or who approved it. Contro1 records that for every call, in Armaor and in every other system the agent uses:

Which AI agent actions should require approval

Lists in and out: Armaor through MCP or the Contro1 API

Every Armaor action you allow is available two ways, with the same grants, approvals and record.

Over MCP, for AI clients: add the Contro1 MCP address to Claude, ChatGPT, Copilot, Cursor or Claude Code, or connect an agent with the Contro1 CLI. The agent sees only the Armaor actions it was given.

https://api.contro1.com/api/centcom/mcp

An agent listing this month's orders. Path and query parameters go in by name; a request body goes under "body".

invoke_action({
  action_id: "armaor.get_orders_2a3d3f0d017c.call",
  input: { createdFrom: "2026-10-01", limit: 200 },
  context: {
    user_request: "Which orders from this month are not in production yet?",
    reason: "Listing this month's orders to compare them with the production plan."
  }
})

Through the Contro1 API, for your own programs, scripts or automation tools: call the same Action with an Agent Credential. Use it to pull lists out of Armaor (orders, planning, stock, delivery notes) and to push lists in (BBS lines, products, clients, stock entries).

curl -X POST https://api.contro1.com/api/centcom/v1/actions/invoke \
  -H "Authorization: Bearer $CONTRO1_AGENT_CREDENTIAL" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
    "action_id": "armaor.post_productions_by_id_0e4ad126f046.call",
    "input": { "orderCode": "24-1187" },
    "context": {
      "user_request": "Get order 24-1187 into production today",
      "reason": "Sales order SO-30418 is confirmed for Thursday and the BBS is complete."
    }
  }'

# While a person decides, the answer is "awaiting_approval". Read the invocation
# until it is "executed", then use its result. Never retry an uncertain write.
curl https://api.contro1.com/api/centcom/v1/actions/<invocation_id> \
  -H "Authorization: Bearer $CONTRO1_AGENT_CREDENTIAL"

curl -X POST https://api.contro1.com/api/centcom/v1/actions/invoke \
  -H "Authorization: Bearer $CONTRO1_AGENT_CREDENTIAL" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
    "action_id": "armaor.post_bbs_by_id_d5a93d946a31.call",
    "input": {
      "code": "24-1187",
      "body": { "order": [ { "name": "Column C1", "qty": 4, "lines": [ ... ] } ] }
    },
    "context": {
      "user_request": "Load the BBS from the engineer's schedule into order 24-1187",
      "reason": "The schedule has 38 members; Armaor numbers the rows."
    }
  }'

The Action ids above are the ones Contro1 gives the Armaor operations; your agent gets the exact list from list_actions. An Action that needs approval answers awaiting_approval first and runs only after the approvers say yes.

Action Gateway docs: call an Action from your own code

Connect Armaor, step by step

From your first message to the first approved call. Most of it is one session with your IT person.

Questions IT and the plant will ask

Frequently asked questions

Is there an Armaor MCP server?

Not a public one that we know of, as of October 2026. Contro1 serves the Armaor Web API's operations as tools on the Contro1 MCP server, so Claude, ChatGPT, Copilot, Cursor or your own agent can use Armaor, each action allowed per agent and the important ones approved by a person.

Does Armaor have an API?

Armaor installations can include the Armaor Web API, a REST API on the Armaor server. At our first install it exposed 68 operations: orders, BBS lines, planning, production, tags, traceability, stock, clients, sites, suppliers, products, deliveries and factory data. Ask Ariadis whether your version includes it.

How do I connect Claude or ChatGPT to Armaor?

Install the Contro1 connector on the Armaor server, publish the Armaor operations in Contro1, give your agent the actions it needs in Access, and add the Contro1 MCP address to Claude or ChatGPT. The agent then calls Armaor actions as tools, and the connector runs them inside your network.

Can Armaor and Priority work together through an AI agent?

Yes. One agent can be given Armaor actions and Priority actions, each with its own approvers. For example, it can read a confirmed sales order in Priority and create the order in Armaor, or set Priority invoice numbers on Armaor delivery notes. Every call in both systems is in one record.

Do we need to open a port or a VPN for Armaor?

No. The connector on the Armaor server only makes outgoing secure connections to Contro1. Armaor stays off the internet and nothing is opened to incoming traffic.

Can an agent change production in Armaor without a person?

Only if you allow it. Each Armaor action is allowed per agent, and you choose which ones run on their own and which wait for one or more people. Putting an order in production is high risk and waits for approval by default.

Can I load lists into Armaor, such as BBS lines or products, through the API?

Yes. Writes such as replacing an order's BBS lines, creating products, clients or stock entries are Actions you can call over MCP or the Contro1 API, with approval where you want it. Lists come out the same way: orders, planning, cutting tags, stock and delivery notes.

Which servers does the Armaor connector support?

Windows Server 2016 or later, Linux with systemd, or macOS. It runs as a service. The first Armaor install ran on Windows Server 2025.

Related resources