Guides

Walkthroughs for the jobs MCPulse exists to do — instrumenting a server, and then acting on what it tells you.

The Product pages describe what each screen and metric is. These are the end-to-end jobs.

Instrument your first server

From an empty account to real numbers, including how to verify data is arriving.

Improve first-call success

Find the tool costing you the most, work out why, and confirm the fix.

Cut context cost

Heavy payloads and dead schema, in the order worth fixing.

Find dead tools

Tools nobody calls, priced against the sessions that pay for them.

Local development

Point the SDK at an API on your own machine.

Where to start

If you have not instrumented anything, start with your first server.

If data is arriving, open Insights. The panel is sorted worst-first, and the top item is where a fix is worth the most.