Use MCP server request logs to monitor activity, troubleshoot failed requests, and review execution details. Depending on the configured log mode, you can view request and response data and inspect the steps executed by tools built in Celigo.
View request history
MCP servers, including their request logs, are available only to account owners and administrators.
- Go to AI studio > MCP servers.
- Select Actions (…) next to the MCP server, and then select View request logs.
- In View request history, review the requests, with the most recent first. Scroll down to load older requests.
- Select Refresh to view the latest requests. Any applied filters remain unchanged.
Request history columns
| Column | Description |
|---|---|
| Time | The date and time the MCP server received the request. |
| User | The user associated with the request, based on the authentication method. |
| Status | Whether the request was a Success, Error, or Blocked. Blocked requests are rejected before they run, for example, when a request exceeds a traffic limit, comes from an IP address that a network policy doesn't allow, or uses a token or sign-in without access to the server. |
| Access token | The API token or personal access token (PAT) used to authenticate the request, when applicable. |
| Capability | The tool, prompt, or resource associated with the request. A Proxied badge identifies capabilities from an external MCP server. |
| Method | The MCP method invoked, such as tools/call or resources/read. |
| Duration (ms) | The time taken to process the request, in milliseconds. |
| Open trace view | Opens the request and execution details, when available. |
Note
The User column displays the authenticated end user for OAuth requests, the workspace user for PAT requests, or the account owner for API token requests. Use the Access token column to distinguish requests made using different tokens. If a user or token is deleted after a request, the request stays in the history with a Deleted badge next to the name.
Filter request history
Use the column filters to narrow the requests displayed:
- Time – Select a preset period or specify a custom date and time range. Request history is available for the last 29 days.
- Status – Filter by Success, Error, or Blocked.
- Method – Filter by one or more MCP methods.
Select Clear to remove the applied filters.
View request and execution details
- In View request history, locate the request you want to inspect.
- Select Open trace view for the request.
- In Trace view, select an item under MCP path to review its details.
The trace view can include:
- MCP Request – The request received from the MCP client.
- Tool steps – The steps executed by a tool built in Celigo, including their status and duration. Select a step to view its available details. Use Errored steps to show only failed steps.
- MCP Response – The response returned to the MCP client.
The information available depends on the log mode configured when the request ran.
Note
The trace view displays tool execution steps only for tools built in Celigo. Requests to APIs, proxied capabilities, and other MCP methods don't include tool execution details. In a sandbox environment, MCP server requests don't display tool execution steps.
Choose a log mode
Each MCP server has a log mode that determines how much request and execution information Celigo stores.
| Log mode | Request and response data | Tool execution details |
|---|---|---|
| No log | Not stored. Only request history is available. | None |
| Basic log | Stored for requests with an Error status. | Step status and duration. |
| Standard log | Stored for every request. | Step status and duration. |
| Detailed log | Stored for every request. | Step status, duration, request and response payloads, and headers. |
| Debug | Stored for every request during the selected debug period. | Everything in Detailed log, plus the inputs and outputs of mappings and transformations. |
New MCP servers use Basic log by default.
MCP servers created before log modes were introduced use Basic log if Store payload was enabled for the account, or No log if it was disabled.
Important
Request and response data can contain personal information, credentials, or sensitive business data. Choose the log mode that captures only the information you need.
Before you change the log mode
- Store payload must be enabled in Account > Company > Execution log preferences before you can choose any mode other than No log or start debug logging.
- Available log modes and maximum debug duration depend on your subscription.
- In accounts with production and sandbox environments, Change log mode isn't available for sandbox MCP servers.
Change the log mode
- Go to AI studio > MCP servers.
- Select Actions (…) next to the MCP server, and then select Edit MCP server.
- Select Change log mode.
- Select No log, Basic log, Standard log, or Detailed log.
- Select Save.
The updated log mode applies to subsequent requests.
Note
Changes to the log mode don't affect previously recorded requests. Existing entries retain the information captured when they ran.
If Store payload is disabled, select Enable from the log-mode panel to open the account's execution log preferences.
Capture debug logs
Use debug logging to capture detailed execution information temporarily when troubleshooting a tool.
- Go to AI studio > MCP servers.
- Select Actions (…) next to the MCP server, and then select Edit MCP server.
- Select Debug next to Change log mode.
- Specify the duration in Hours and Minutes.
- Select Start.
The remaining debug duration appears at the top of Edit MCP server. Select Stop debug to end the session early.
Debug logging automatically ends after the selected duration and returns to the previously configured log mode.
The maximum duration depends on your subscription:
| Subscription | Maximum debug duration |
|---|---|
| Free trial | 15 minutes |
| Standard | 1 hour |
| Professional | 24 hours |
| Enterprise | 72 hours |
Important
Debug logging captures detailed request and execution data that might contain sensitive information. Use it only for the time needed to troubleshoot an issue.
Troubleshoot missing log details
| Issue | What to check |
|---|---|
Trace view isn't available (tooltip: Trace view isn't available when no payload exists) |
Check whether the configured log mode captured request data and whether Store payload was enabled. If the logs were deleted, the data can't be recovered. |
| No tool steps appear | Confirm that the request ran a tool built in Celigo. API calls, proxied capabilities, and sandbox MCP server requests don't display tool execution steps. |
| Tool steps show status and duration but no data | Use Detailed log or Debug to capture additional execution information. |
| Older requests don't show new details | Log mode changes apply only to subsequent requests. Reproduce the request after changing the log mode. |
Delete stored request data
You can permanently remove stored request, response, and detailed execution data for a selected date range while keeping the request history entries.
Select Delete logs in request history to remove the stored data. The request entries remain available for monitoring and audit purposes.
Important
Deleting logs is irreversible, and deleted data can't be recovered. Deleting also removes the run logs of the MCP server's tools for the same period, including runs started by flows or APIs.
For instructions, see Delete logs from MCP server request history.
Frequently asked questions
How long does Celigo keep request history? For your account's data retention period, 30 days by default. After that, Celigo removes the requests and their stored data automatically.
Can I remove a request from request history? No. Requests stay in the history so the record of who called the server, and when, remains complete. You can delete their stored data.