MCP server
Connect an AI assistant such as Claude to iQBus, describe the integration you need in plain language, and the assistant builds it in your Application.
The iQBus MCP server speaks the Model Context Protocol, the standard AI assistants use to work with other systems. Once it is on, your assistant can create and change the artifacts of an integration for you, signed in as you, with your roles, and every change it makes lands in Audit Logs.
The MCP connection is off by default. A System Administrator turns it on in Settings, System, on the MCP connection card: one switch, with a status that reads On, Off or Unavailable. Turn it off again and every connected AI client loses access at once.
Each person connects their own AI client once. In Claude Desktop:
- Open Connectors and add a custom connector.
- Enter your iQBus address followed by
/mcp, for examplehttps://iqbus.contoso.com/mcp. - Sign in with your Microsoft Entra ID account when the client asks.
That is all. The assistant now lists iQBus among its tools, and you talk to it as you would to a colleague who knows the product.
An agent works inside the Applications you hold a role on, and it can do everything the Application’s Artifacts menu offers. That is enough to build an integration end to end, from the Authentication to the last port.
| Area | What the agent can do |
|---|---|
| Artifacts menu | Everything, in any Application you have a role on: Activity Notifications, Authentications, Message Types, Ports, Maps, Variables, Constants, Pipelines, Schemas, Pipeline Components, Custom Functions, NuGet Packages and the Application’s Users. |
| Settings menu | Nothing. System, Snapshots, Monitoring, Domains, Users and Audit Logs stay with the people who use the portal. |
The agent signs in as you and holds exactly your roles. On an Application where you are a Reader, the agent can read but not change; an Application you have no role on, it cannot see. There is no separate agent account to manage and nothing extra to grant.
Every change the agent makes is recorded in Audit Logs under your name, exactly as if you had made it in the portal. Example: an agent that creates a port at 10:42 shows up as you creating that port at 10:42.
Describe the whole integration in one request, the way you would brief a colleague:
In the Orders application, build an integration that picks up order CSV files from our SFTP server every 15 minutes, turns each order into JSON, and posts it to https://erp.contoso.com/api/orders. If a delivery fails, email ops@contoso.com.
From that one request the agent creates what you would otherwise build by hand, for example:
- An Authentication for the SFTP server and one for the ERP API.
- Message Types for the CSV order and the JSON order, with a map between them.
- A receive port on the SFTP Listener that checks the folder every 15 minutes.
- A send port on the API Caller that posts each order.
- An Activity Notification that emails the operations team when a delivery fails.
Everything it builds appears in the portal like anything you built yourself, so you can open it, review it and change it, by hand or by asking the agent.
That is the whole setup
Turn the MCP connection on, add your iQBus address to your AI client, sign in, and describe what you need. The agent builds it as you, and Audit Logs keep the record.