Reqres MCP. Mock API Endpoints for Testing Data Flows

Reqres gives your agent a sandbox API it can run against. Stop building backends just for testing—you'll spend too much time on stuff that doesn't matter. This server lets you mock user creation, manage project records (CRUD), simulate logins, and pull real-world resource data without setting up a single database or worrying about actual persistence.

It’s the standard toolkit for front-end prototyping and advanced agent development.

User Management: You can run through full identity flows by simulating new registrations using register_demo or running a login via login_demo, both of which return an access token you need. If you're testing user linking, use request_magic_link to kick off the magic link process for an app user, and then verify that link with verify_magic_link to get the session token.

To check a specific person’s profile, call get_user with their unique ID; if you just need details on who's running the tool, use get_me. You can list users across the whole system using list_users, or grab a paginated list of them with agent_users. For single-handedly managing records, you've got create_user to simulate making a demo user account, and delete_user removes that specified profile from the Demo API environment.

To update a user’s details partially, call patch_user; if you need to change every bit of their info, use update_user.

Project Record Management: When it comes to data collections—your project records—you can handle the full lifecycle. You'll start by generating and saving a new record into any project collection using create_record. If you need to build out a user-specific record, use create_app_record which saves it within an application collection scoped to the current user.

To pull data for one specific item, call get_record with its details; otherwise, you can fetch all records belonging to the current user by using list_app_records. If you need a comprehensive list of all items in a project collection, list_records gives you paginated results, and you can get multiple users' data by calling agent_orders which retrieves orders along with related info.

To update an existing record, you have two options: use patch_record to change only specific fields (a partial update), or call update_record if you need to replace the entire record with new data (full replacement). When a record is done and needs clearing out, delete_record removes it from any defined project collection.

Flow Testing & Utilities: You can simulate system failures for robust testing by calling trigger_scenario, forcing the agent sandbox into a specific error state. To check if your agent's connection is stable, run agent_health; this verifies the health and rate limit status of the Agent Sandbox. If you need to know what failure states are available, agent_scenarios lists all available scenarios within the environment.

For validating external data types, like Pantone colors, list_colors retrieves a list of resource colors from the Demo API. When working with applications, you can see every record belonging to your current user by running list_app_records, and you can also check how many users are available using list_users. The system also supports checking if there's an issue when listing records through agent_orders.

It's basically a complete mock environment for testing everything from identity to data persistence.