> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getmcpulse.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Guides

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

The [Product](/introduction) pages describe what each screen and metric is. These are the end-to-end jobs.

> **[Instrument your first server](/guides/first-server)**
>
> From an empty account to real numbers, including how to verify data is arriving.

> **[Improve first-call success](/guides/improve-first-call)**
>
> Find the tool costing you the most, work out why, and confirm the fix.

> **[Cut context cost](/guides/cut-context-cost)**
>
> Heavy payloads and dead schema, in the order worth fixing.

> **[Find dead tools](/guides/find-dead-tools)**
>
> Tools nobody calls, priced against the sessions that pay for them.

> **[Local development](/guides/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](/guides/first-server).

If data is arriving, open [Insights](/insights/overview). The panel is sorted worst-first, and the top item is where a fix is worth the most.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.