Connections, Audit Logs, and Asynchronous Jobs

Use the Odoo control center to see who is connected, what they called, which security context applied, and whether larger background jobs completed.

Connections

Open MCP Server > Connections. A normal MCP User sees their own connections; an MCP Administrator sees all connections.

• Identity: Odoo user, client application, client name, authentication method, and API key where applicable.
• Access: scopes, assigned bundles, effective access summary, and exposed model count.
• Status: active, expired, revoked, or disabled.
• Timing and metadata: connected time, last seen time, expiry, source IP, and user agent.

Disable a suspicious or unused connection without archiving the Odoo user. For OAuth, associated tokens are revoked; for an API-key connection, the key is deactivated.

Audit Logs

Open MCP Server > Audit Logs. Logs can record successful, denied, and failed requests.

• User and connection.
• Client application and client name.
• Endpoint, event type, tool or method, model, operation, and record IDs.
• Request and response summaries, status, HTTP status, and error message.
• Source IP, user agent, timestamp, and duration.

Use audit logs to explain missing tools, access denials, domain restrictions, failed writes, OAuth issues, slow calls, and unexpected client behavior.

Asynchronous jobs

Large count, CSV export, or JSON export work can be submitted as a persisted job. The standard limit is up to 5,000 records per job.

1. The MCP client submits the job with model, domain, fields, order, operation, and limit.
2. The job enters queued state and a scheduled action processes a small batch each minute.
3. The user checks queued, running, completed, failed, or cancelled state.
4. Completed files can be downloaded through Odoo or fetched by the MCP client in bounded base64 chunks.
5. Expired results are cleaned automatically.

Operating routine

• Daily: review failed or denied audit entries and unexpected active connections.
• Weekly: revoke unused keys, inspect high-volume clients, and review write/delete activity.
• After upgrades: reconnect or refresh clients, check tool discovery, and test one read and one permitted mutation on staging.