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

# MockServer

> Mock and proxy any HTTP or HTTPS service with ease. Set up expectations, verify requests, and debug traffic — in Java, JavaScript, Ruby, or via the REST API.

MockServer lets you mock any system you integrate with over HTTP or HTTPS, and proxy live traffic for inspection and debugging. Use it in tests, local development, or CI pipelines to isolate dependencies and control responses.

<CardGroup cols={2}>
  <Card title="Quick Start" icon="bolt" href="/quickstart">
    Get MockServer running and mock your first request in under 5 minutes.
  </Card>

  <Card title="Running MockServer" icon="server" href="/running-mockserver">
    Deploy via Docker, Helm, Maven, npm, or as a standalone JAR.
  </Card>

  <Card title="Creating Expectations" icon="list-check" href="/mocking/expectations">
    Define request matchers and response actions to control what MockServer returns.
  </Card>

  <Card title="REST API Reference" icon="code" href="/api/overview">
    Explore the full REST API for managing expectations, verification, and state.
  </Card>
</CardGroup>

## How MockServer works

MockServer acts as a controllable HTTP server. You configure it with **expectations** — rules that match incoming requests and define what response to return. You can then verify which requests were received after your tests run.

<Steps>
  <Step title="Start MockServer">
    Run MockServer via Docker, as a JAR, or embedded in your test framework.
  </Step>

  <Step title="Set up expectations">
    Use a client library or the REST API to define how MockServer should respond to requests.
  </Step>

  <Step title="Run your tests">
    Point your application at MockServer. It intercepts requests and returns your configured responses.
  </Step>

  <Step title="Verify requests">
    Assert that your application made the expected calls — method, path, headers, body, and more.
  </Step>
</Steps>

## Explore by use case

<CardGroup cols={2}>
  <Card title="OpenAPI Mocking" icon="file-code" href="/mocking/openapi">
    Auto-generate expectations from an OpenAPI v3 specification.
  </Card>

  <Card title="Response Templates" icon="wand-magic-sparkles" href="/mocking/response-templates">
    Return dynamic responses using Mustache, Velocity, or JavaScript templates.
  </Card>

  <Card title="Proxy & Record" icon="arrows-left-right" href="/proxying/record-replay">
    Proxy live traffic, record requests and responses, then replay them.
  </Card>

  <Card title="Client SDKs" icon="puzzle-piece" href="/clients/java">
    Use the Java, JavaScript, or Ruby client to control MockServer programmatically.
  </Card>
</CardGroup>
