Manufact
Monitor and debug MCP traffic in production
See which clients are calling your tools, find slow or failing requests, and inspect the session behind an error. Cloud Inspector follows traffic through the Manufact gateway, whether you host with us or use our proxy.
Our open source tools are used by developers at top companies
From a production error to the request that caused it
Filter gateway requests by status, client, and MCP method. Open an event to follow the session from initialization through tool calls and errors. Request metadata is captured by default; enable payload capture when you need stored arguments and responses.
- 01Route client traffic through Manufact
Use your hosted server's gateway URL, or enable the Manufact proxy for a server hosted elsewhere and connect clients to its gateway URL.
- 02Find the failing or slow request
Open Gateway Requests and filter by status, client, or method. Review the timestamp, duration, and session context.
- 03Inspect the recorded session
Follow the event timeline to see what the client did. With Capture payloads enabled, inspect stored request and response bodies for additional context.
Request tracing
Inspect individual gateway events with status, method, client, timing, and session context. Narrow the stream to the requests you need to investigate.
Session history
Review initialization, tool discovery, calls, and errors in order. Session replay is a view of recorded events, so you can investigate without re-executing a tool.
Errors and latency
Use Analytics to compare tool and client health, investigate recurring issues, and follow matching sessions from error and latency trends.
Connect production traffic, then choose what to capture
Keep your current hosting or deploy on Manufact. Cloud Inspector shows the traffic routed through your gateway URL.
- Can I monitor a server hosted elsewhere?
Yes. Connect your existing MCP server, enable the Manufact proxy in its settings, and point clients at the Manufact gateway URL. A direct external connection alone enables dashboard testing tools, but does not capture production traffic or enable Gateway Requests, Analytics, or Sessions.
Connect an existing server and enable the proxy- Are request and response bodies stored automatically?
No. Request metadata is stored by default. Enable Capture payloads in the server's Analytics settings to store request and response bodies for subsequent events. Payloads may contain customer data; review your data-handling requirements before enabling capture and disable it when you no longer need it.
Read about gateway requests and payload capture- How long can I inspect past requests?
Current analytics retention is 30 days on Free and pay as you go, 90 days on Pro, and 365 days on Enterprise. Legacy and contracted plans retain their agreed terms. Gateway Requests uses the same retention window.
Compare current plans- How is this different from the open-source Inspector?
Use the open-source Inspector to connect to a local or remote server and deliberately test tools, resources, prompts, and widgets. Use Cloud Inspector to investigate gateway traffic from real clients and review recorded sessions. The open-source tool is available online, locally, and self-hosted.
Explore the open-source Inspector
Follow request errors and timing in session timelines, or compare tool and client health in MCP Analytics.
Investigate your production MCP traffic
Host on Manufact or route an existing server through the proxy. Open Gateway Requests to inspect live events and follow their session history.
