Skip to main content
MCP Monitoring shows how your MCP Gateways are being used: which tools are called, by whom, how often, and how they perform. Find it at airia.ai/gateway/feeds/mcp. The page has two tabs, Overview and Activity, that share one time-range selector. The range runs from the last hour to the last 7 days and defaults to the last 24 hours.

​
Which tab to use

OverviewActivity
ShowsAggregate health and traffic across GatewaysIndividual requests, one row each
Use it toSpot trends, error spikes, and top tools at a glanceAudit a specific call, investigate an error, or trace a user’s report
GranularityCharts and summary countsPer-request log with full payloads

​
Overview tab

A high-level snapshot of Gateway health and traffic for the selected time range. It includes:
  • Active Gateway count
  • Total tool calls
  • Error rate
  • Typical response latency
  • A traffic chart broken out per Gateway
  • A table of your most-used tools

​
Activity tab

A searchable, filterable log of individual requests made through your Gateways. Each entry shows when and where a request happened, who made it, whether it succeeded, and how long it took. Every entry carries a Correlation ID you can reference when contacting support about a specific call. Each request records one of these statuses:
StatusMeaning
SucceededThe request completed successfully.
DeniedThe request was blocked by an access policy or guardrail before reaching its destination.
ErrorThe request reached its destination but failed.
Click any row to open the full request detail, including the raw Request and Response payloads exchanged with the MCP server. You can copy each payload to your clipboard.
You can restrict a user’s access to sensitive data from their account settings. A restricted user sees a notice in place of the raw Request and Response payloads.

​
Who can see what

Visibility on the MCP Monitoring page depends on the viewer’s role.
RoleScope of visibility
Platform Admin, Admin, Read-Only Admin, Security AdminThe entire tenant: every Gateway and every user’s requests
Project AdminOnly their own Personal Gateways (no automatic tenant-wide visibility)
End UserOnly their own Personal Gateways
If your organization uses custom roles, tenant-wide visibility is controlled by a dedicated analytics permission instead of the built-in roles above.
End Users and Project Admins need the MCP Gateway permission to open the MCP Monitoring page at all. An administrator configures it under Account Settings.

Tenant vs. Personal Gateways

Understand which activity each visibility level covers

Tool Scanning

See how guardrails decide what gets denied

Custom Roles

Grant the analytics permission for tenant-wide visibility

Set up a Gateway

Connect a Gateway to Cursor or Claude