> ## 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.

<CardGroup cols={2}>
  <Card title="Instrument your first server" icon="rocket" href="/guides/first-server">
    From an empty account to real numbers, including how to verify data is arriving.
  </Card>

  <Card title="Improve first-call success" icon="bullseye" href="/guides/improve-first-call">
    Find the tool costing you the most, work out why, and confirm the fix.
  </Card>

  <Card title="Cut context cost" icon="coins" href="/guides/cut-context-cost">
    Heavy payloads and dead schema, in the order worth fixing.
  </Card>

  <Card title="Find dead tools" icon="ghost" href="/guides/find-dead-tools">
    Tools nobody calls, priced against the sessions that pay for them.
  </Card>

  <Card title="Local development" icon="laptop-code" href="/guides/local-development">
    Point the SDK at an API on your own machine.
  </Card>
</CardGroup>

## 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.