Local mock API server for frontend, QA, and full-stack teams

Run a local mock API server that stays predictable as your app evolves. Use the desktop UI or the mockphine CLI to mock endpoints where you need certainty, pass through where you need upstream truth, and verify everything in Live View.

Download macOS](https://downloads.mockphine.com/latest/mockphine.dmg) Choose macOS architecture
Download Windows](https://downloads.mockphine.com/latest/mockphine-windows.exe) Choose Windows build and architecture

Free tier: 1 server, 10 endpoints/server One-time licenses

What you can validate before you buy:

  • Deterministic route matching (exact, parameter, and wildcard paths).
  • Per-endpoint modes: mock, passthrough, or disabled.
  • Live View request stream with served-by source and response details.

Benefits

A local mock API server you can trust under change.

Local speed often breaks when request matching is fuzzy, passthrough is all-or-nothing and logs can’t explain what happened. Mockphine keeps behavior explicit and easy to verify.

Deterministic matching

Match by method + normalized path, then tighten behavior with query rules so your local API stays predictable as routes evolve.

Per-endpoint modes

Set each route to mock, passthrough, or disabled based on what you need today.

Live request inspection

Verify status, duration, and served-by source in a live stream so you know exactly what happened.

Workflow

From install to validated endpoints in minutes.

Use it like a real local API server: configure, run, and confirm behavior with real requests.

3-step setup

Minimal setup, direct feedback

  1. Create a local server from the desktop UI or the mockphine CLI with port, real backend URL, and fallback mode.
  2. Add endpoints and choose mock or passthrough per route.
  3. Run your app and confirm behavior in Live View.

FAQ

Common questions about running a local mock API server.

If you need full pricing details, you can also jump to licenses and pricing.

Is Mockphine CLI-based?
Yes. Mockphine now has both a desktop UI and a headless CLI named mockphine, so you can configure mocks visually or drive terminal-first workflows for scripts, CI, and AI agents.

Can it pass through to a real backend?
Yes. You can set routes to passthrough (or disabled) to forward to your configured real backend URL while keeping other routes mocked.

How does routing match requests?
Requests match on HTTP method + normalized path first, then optional query matching rules (none, exact, or contains required key/value pairs).

What happens when no route matches?
Fallback is configurable per server: return a strict 404 not mocked, or pass through unmatched requests to your real backend.

Does Mockphine keep request logs?
Yes. Live View keeps per-server request logs (capped) so you can inspect what happened without leaving your local environment.