MCP Audits
Overview
AI assistants can now create, update, and configure your integrations directly through MCP - which raises a natural question: what did the AI actually change, and when? MCP Audits answer that.
OpsHub Integration Manager records an audit entry for every configuration change made in the application, capturing the entity that was changed, the user who changed it, when the change was made, the type of change, and the field-level values that changed. Every audit entry also records the Origin of the change - the channel it came through. Since the same user can make changes from the OpsHub Integration Manager UI, the Admin API, or an MCP client, Origin makes it clear which one was used, so changes made by an AI assistant through MCP can always be told apart from the rest.
Audits are available for all audited entities, such as Systems, Integrations, Mappings, Workflows, Users, Roles, Login Servers, Excel Uploads, Job Schedules, API Keys, and Processing Failures. To view them, click the audit icon on the top right corner of the respective list view.
Origin Values
Filter and Sort by Origin
The Origin filter is available on every audit screen. Select a value to view only the changes made through that channel - for example, select MCP to review everything an AI assistant changed. Click Reset to restore the default view.
The Origin column can be sorted like the other columns, which is useful to group all the changes of a channel together.
Important Notes
Historical audit records are displayed with Origin as UI because the source channel was not captured before this OpsHub Integration Manager version upgrade. To maintain a complete and consistent audit trail, existing audit entries are backfilled with the value UI. Changes made after the upgrade correctly capture and display their actual Origin, such as UI, Admin API, or MCP.
Audit records show the account used to make the change, not the actual person behind it. If an MCP client or the Admin API uses a shared or service account, all changes will be recorded under that account. If you need to track changes back to a specific person, use individual user accounts or user-specific API Keys.
Last updated