Platform
The governed gateway between AI and your business apps
mcpbizapps sits between AI assistants and your business apps. People sign in by name, roles decide which tools they get, every change is previewed and approved where your rules require it, and every request lands in one audit log. One gateway, the same controls for every app and every assistant.
Architecture
Every request takes the same governed path
At a glance
The controls, one tile each
-
Who is asking, and what may they do?
Role-based tools
Only people your admin invites sign in, with their work email and a one-time code. Roles decide which tools each person can use from their assistant: read-only for most, sales orders for sales.
-
What will it change?
A preview before every change
The assistant shows exactly what it will create. Nothing happens in your app until the person confirms.
-
Who signs off?
Approval when it matters
Above the amount you set, a second person decides on the approval page. Nobody approves their own request.
-
What happened?
One audit log
Who asked what, through which assistant, with which result, and a link to the record created. Export it for your auditors.
-
Where does the data go?
Read live, not kept
Business data is read from your app when the assistant asks, returned and not stored. Conversations stay in your assistant.
-
Which apps?
Every app, one gateway
ERP, accounting, HR and CRM apps get the same sign-in, roles, previews, approvals and audit log. SAP Business ByDesign connects today; the other 14 apps are set up for your team in a guided pilot.
Any AI assistant
Works in the assistants your team already uses
Each person adds one connector URL to Claude, ChatGPT or Microsoft Copilot Studio and signs in with their work email. Any other assistant that supports Model Context Protocol with secure sign-in works too.
- No new app to learn
- Sign-in by work email and a one-time code, no passwords
- A consent screen shows exactly what the assistant may do
Every business app
One gateway for ERP, accounting, HR and CRM
Each business app is added as a pack on the same gateway, with business-level tools such as "Find customers" or "Prepare a sales order" instead of raw endpoints. Admins connect an app once with a dedicated integration user and a connection test.
- Tools named after tasks, so assistants pick the right one
- One integration user per app, credentials encrypted
- Connection health checked every few minutes
Access control
Role-based access for AI assistants
Only people your admin invites can sign in. Roles decide which tools each person can use from their assistant, so most people look things up while only some can prepare changes. Deactivate someone and every assistant they connected loses access on its next request.
- Built-in Admin, Approver and Member roles, plus your own
- Tools granted per role in one matrix
- Instant offboarding across every AI client
Governed changes
A preview before every change, approval when it matters
When an assistant prepares a change, the person sees a preview and confirms it. Above the amount you set, an approver gets an email and decides on the approval page. Nothing is created until those steps are done, and nobody approves their own request.
- Approval rules by amount and currency
- Approver roles you choose
- A switch per kind of change to allow previews only
Audit trail
Every request, decision and sign-in in one log
The audit log shows who asked what, through which assistant, in which app, with which result, and links to the record created. Filter it, open any event, and export it for your auditors.
- Tied to a named person, never a shared key
- Filters by person, event type, tool, result and date
- CSV export, kept one year by default
Data handling
Read live. Not kept.
Business data is read from your app when the assistant asks, returned and not stored. Conversations stay in your AI assistant. A prepared change waiting for confirmation or approval is kept encrypted and deleted when it ends.
- No copy of your business data
- Hosted on AWS in the United States
- Personal fields and free text removed from audit details
Questions people ask
How long does setup take?
The mcpbizapps side takes minutes. The app side needs your administrator to create an integration user with the access the tools need, and for some apps to turn on a few web services we provide. We do this with you during the pilot.
Does each person need a user in the business app?
No. mcpbizapps calls the app with one dedicated integration user per connection. People sign in to mcpbizapps with their work email, and the audit log and a note on created records name the real person. Check the license terms of your app for integration users.
What happens if the assistant gets something wrong?
Look-ups only read data. Changes are previewed and need the person to confirm, and larger ones need an approver. Nothing is created in the app until those steps are done.
Can we use several AI assistants at once?
Yes. Each person can connect the assistants their company uses. The same roles, rules and audit log apply to all of them.
How is mcpbizapps different from an API integration?
An API integration exposes every field and operation to whatever calls it. mcpbizapps exposes a few business tools, acts for a named person with that person’s roles, previews and approves changes, and logs everything in one place.
Last updated
See it with your own questions
In 30 minutes we show an AI assistant looking up and preparing work in a business app, with the approval and the audit trail. Bring the questions your team asks every week.