HTTP Mock Server for Unity is a lightweight tool for emulating API requests directly within the Unity Editor.
It runs a local HTTP server that responds with pre-prepared JSON files,
allowing you to test your game's network interactions without connecting to a live server.
Key features:
1) Local stub server. Allows you to process HTTP requests (GET, POST, etc.) without internet connection.
2) Easy route configuration. All endpoints are defined in a single ScriptableObject — MockServerConfig.asset.
3) Flexible responses. Each route returns the contents of a JSON file located in the Responses folder.
4) Support for response codes and delays. You can specify a status (200, 404, 500, etc.) and an artificial response delay to simulate network connection.
5) Works directly in the Editor. Start via the Tools → Mock HTTP Server menu and stop with a single click.
Why it's needed:
1. Development without a real backend. Allows programmers, artists, and game designers to test server interactions
before the server is ready.
2. Logic and UI testing. You can emulate different API responses: successful, error, delayed, and empty.
3. Autonomous team work. Each developer can work locally, without relying on a shared test environment.
4. Rapid prototyping. You can instantly change the server response by simply changing the JSON file in Unity.
Suitable for:
1) Developers testing HTTP integrations in Unity
2) Teams whose server isn't ready yet
3) Those looking to speed up UI prototyping or offline API testing
Unique advantages:
1) Simple setup.
- All routes are configured via ScriptableObject and JSON files.
- No need to write attributes above functions or use an event-based system.
2) Direct access to JSON.
- Responses are taken from regular files in the Assets/HTTP Mock Server/Responses folder.
- You can instantly change responses by simply editing the JSON.
3) Lightweight Editor interface.
- Start and stop the server via Tools → Mock HTTP Server.
- No complex configuration or programming required.
4) Ideal for prototyping.
- Test UI, network logic, authorization, and inventory without an external server.
- Completely local, independent of the internet.
5) Minimal dependencies.
- Uses only the built-in HttpListener.
- Lightweight and fast, no third-party libraries required.
* Instructions included.