MCP quickstart

Give AI agents safe, governed access to the industrial systems your team runs on. With Makini MCP, an agent in Claude, Cursor or any MCP client can look up open work orders in a CMMS, check an asset's history, or create a work order the moment someone reports a fault. It works across every platform your workspace connects, and you decide which operations it may run.

What an agent can do

Read live data

Ask for open work orders, overdue preventive maintenance, spare-part stock or purchase orders, and get answers straight from the connected system.

Take action

Create and update records, such as a work order for a failing pump, through the same operations the system's own API offers.

One connector, many systems

One MCP server URL serves every platform your users connect. The agent names the platform on each call.

Governed by you

Choose visible platforms, and allow or block every tool per role and per user. Every call is logged.

How it works

Every MCP application gets its own server URL:

https://mcp.makini.io/<clientId>

<clientId> is your application's Client ID. The dashboard shows the full URL as the Connector URL on Get started.

Each person who uses an agent is an MCP user. MCP users sign in from their agent with a one-time code sent to their email. They need no password and never get dashboard access. Each MCP user connects their own accounts on the platforms you enable, so every call runs with that person's own access in the connected system.

Set up

Create an MCP application

When you sign up, choose MCP as your application type. If your workspace already has an API application, add the MCP one from Organization settings in your avatar menu. A workspace can hold one API application and one MCP application side by side.

Choose platforms and tools

Open Platforms. MCP applications start with every platform hidden, so you turn on only the systems your agents should reach. For each platform, Permissions sets which tools agents may run. See Users and permissions.

Invite MCP users

Open Users → MCP users and click Invite MCP user. Makini emails them the connector URL and how to add it to their agent. To give a colleague who is already in your workspace a seat, turn on their MCP access switch on the Users tab.

For an agent that runs unattended, with nobody to sign in, click Create agent instead. See Autonomous agents.

Add the connector to an MCP client

Each user adds the connector URL to their client. See the next section.

The first time the agent uses the connector, the client opens a sign-in page. The user enters their email address and the one-time code Makini sends. Before returning to the agent, they can connect any of the platforms you enabled. They can also connect more later, whenever the agent asks.

Add Makini to your MCP client

The connector uses the streamable HTTP transport and signs users in with OAuth. Your client handles the sign-in for you.

Claude

Cursor

Other MCP clients

Open Settings → Connectors.

Click Add custom connector.

Paste your connector URL, https://mcp.makini.io/<clientId>, and save.

Start a chat. Claude opens the Makini sign-in the first time it uses the connector.

In Claude Code, add it from the terminal:

The sign-in prompt is expected. It binds the agent to that user, so every tool call runs as them, against their own connections.

The four tools

Industrial systems expose thousands of API operations. Makini keeps the agent's context small with four tools: it discovers the right operation on demand, then runs it.

Tool	What it does
`list_platforms`	Lists the platforms this user can see. `has_connection` says whether they have connected each one.
`verify_platform_authentication`	Checks the user's connection to one platform. If they haven't connected it, it returns a Makini Link URL to open in a browser.
`search_platform_tools`	Searches a platform's operations with a short phrase, such as "open work orders" or "create purchase order". It returns each tool's exact name, its description and its input schema.
`execute_tool`	Runs one operation with its arguments and returns the system's response.

Every tool except list_platforms takes a platform key, because one user can connect several systems.

execute_tool takes its arguments grouped by where each value goes in the request, exactly as the tool's input_schema lists them:

{
  "platform": "inextia",
  "tool_name": "<name returned by search_platform_tools>",
  "arguments": {
    "path": { },
    "query": { },
    "body": { }
  }
}

Leave out any group the operation doesn't use.

Example: from a question to a work order

A maintenance planner asks their agent: "What's open on Line 2, and raise a work order for the leaking seal on pump P-101."

Find the system

The agent calls list_platforms and sees the planner's CMMS with has_connection: true.

Find the right operation

It calls search_platform_tools with the query "open work orders". It picks the matching operation and reads its input schema.

Read

It calls execute_tool with that name and a filter for Line 2. It then summarizes the open work orders for the planner.

Act

It searches again with the query "create work order". It calls execute_tool with the asset, the description and the priority in the body group. The CMMS returns the new work order, and the agent reports its number.

If the planner hadn't connected the CMMS yet, verify_platform_authentication would return a Makini Link URL. The planner opens it, enters their credentials once, and the agent carries on.

Responses and refusals

The system's own answer comes back as data. If the connected system rejects a call, the result looks like {"ok": false, "status": 422, "data": …}. The agent reads it, corrects the arguments and tries again.

Permissions are final. Search shows every operation on the platform, but execute_tool refuses the ones an administrator has turned off. The agent is instructed to stop and tell the user that an administrator can enable the tool, instead of looking for a way around it.

Connection states. verify_platform_authentication returns one of four states: connected, absent, expired or deactivated. absent and expired come with a Makini Link URL, so the user can connect or re-enter their credentials. deactivated means an administrator switched the connection off, and only an administrator can switch it back on.

Next steps

Users and permissions: roles, per-tool permissions, company-wide credentials, the MCP explorer and MCP logs.

Provider mode: agents for your customers: run agents for your own customers, with users provisioned from your backend.

MCP quickstart

What an agent can do#

How it works#

Set up#

Add Makini to your MCP client#

The four tools#

Example: from a question to a work order#

Responses and refusals#

Next steps#

What an agent can do

How it works

Set up

Add Makini to your MCP client

The four tools

Example: from a question to a work order

Responses and refusals

Next steps