MockMotor Documentation AI-generated
MockMotor is a mock/stub server for HTTP, SOAP, REST, GraphQL, WebSocket and LDAP services, built for teams that need a realistic, stateful, scriptable stand-in for a dependency that isn't available, is too slow, or is too risky to hit directly in testing.
This documentation covers current, day-to-day usage. For release announcements, longer write-ups, and "why we built it this way" pieces, see the blog.
Start here
Core Concepts
Environments, services, reactions and how a request finds its way to a response.
Environments
Ports, traffic type (HTTP or LDAP), logging, access control.
Services
Grouping reactions by URL prefix (or LDAP BaseDN).
Reactions
Matching, payload generation, headers, attachments, forwarding, delays.
Reaction Examples
Worked JSON & XML examples pulled from the live public demo - matching, account selection, account updates.
Data & scripting
Variables
Pulling values out of the request and into the response.
Mock Accounts
Stateful test data selected per-request and returned or updated.
Script Library & JWT
Shared JavaScript/XQuery functions and built-in JWT signing/verification.
Attachments & Binary Responses
SOAP SWA/MTOM/XOP, binary downloads, file attachments.
Protocols
LDAP Mode
Stubbing an LDAP directory: Bind, Search, BaseDN routing, entries.
Forwarding & Recording
Proxying to a real backend, and recording real traffic into new reactions.
CORS & Auth Basics
Automatic CORS handling, Basic Auth and JWT-secured mocks.
MCP & REST API
Driving MockMotor from an AI agent or a CI pipeline instead of the console.