Request logs
The Logs page is the request-by-request record of traffic to a server. Each entry is one MCP request: the method that was called, whether it was a standard JSON-RPC call such astools/list or a specific tool invocation, the status the
gateway returned, and when it happened. A histogram above the list shows request
frequency over the selected time range, so a spike or a gap is visible before you
read a single row.
Selecting a request opens its full detail, including the acting user or service
account, identified MCP client, request and response payloads, and gateway
processing. Gateway plugins report whether they passed, modified, blocked, or
errored on the request. This makes access-policy filtering and sensitive-data
redaction visible in the same record as the resulting response.
This is the first place to look when a client reports that a call failed: you can
confirm whether the request reached the gateway, how it was routed, and whether
it was accepted or rejected before assuming the problem is in server code.
Filter to errors only to narrow a noisy stream down to the requests that did not
succeed. For control over which payloads are stored, see
Data handling.
Logs refresh live as new requests arrive, and pause when you want to study a
fixed window without rows shifting underneath you.
Usage
The Usage page summarizes how clients use a server. It shows tool calls, unique actors, error rate, and p95 latency over the selected window, then breaks that traffic down by actor and capability. Actors include both users and service accounts, using the verified identity the gateway attached to each request. Calls that FastMCP Gateway cannot attribute appear under Unknown. This usually means the calls were not authenticated through FastMCP Gateway. These calls do not increase the unique actor count. Select an actor, including Unknown, to see the capabilities it used, or select a capability to see its callers. Tools, prompts, and resources appear together, each marked with an icon for its kind. After selecting an actor or capability, choose View logs to open the request log with the same target, time range, actor, and capability filters applied. For how actor identity is established, see Authentication.Server logs
Request logs and usage describe traffic from the outside. The logs the server itself produced live with the deployment that produced them, reached from a build or deployment on the Deployments page.
Server logs open at the newest output and continue to refresh while you stay at
the bottom of the stream. Scroll upward to load earlier output without moving
your place. Floating controls jump to the deployment’s first log, step backward
or forward in time from what you are viewing, or return to the live stream.
For what the runtime captures from your server’s output, see
Compute model.
Programmatic access
The FastMCP Gateway REST API exposes request, build, and deployment runtime logs. Authenticate with a personal or service-account API key, then use the log routes in the API reference.Time ranges and history
Analytics views provide time-range selectors for recent windows, and live views refresh on their own so a dashboard left open keeps current. Request, build, and server logs are available for the last days in the dashboard and the API. Older logs are not returned.Related docs
Gateway
See how requests are received, routed, and recorded before reaching server code.
Compute model
Learn how the runtime handles requests, memory, timeouts, and server logs.
Deployments
Find build and server logs for a specific build or deployment.
Authentication
Learn how the actor identity shown in usage analytics is verified.