ReqRes is a remote MCP server that lets an assistant create a hosted REST backend with persistent collections and records, without signup.
What you can do
Create a hosted project with a REST API, database, manage key, read-only public key and starter products collection in one call, with no account or API key needed. List the collections in a project and create new collections, each with its own REST endpoint. Read paginated records from a collection, save new JSON records, replace a record's fields, and delete records.
When to use it
Useful when a user needs a live API and persistent storage for a prototype, app or frontend without setting up a database or signing up for a service. Also suited to quickly standing up collections for things like tasks, users or orders.
Requirements
A remote streamable HTTP endpoint; no local runtime, account, API key, environment variables or headers are declared. Network access is required, and the assistant needs the manage key returned when a project is created to work with that project.
Before you install
Creating a project provisions a real hosted backend and returns a manage key that grants control over it; treat that key as a secret. Records written, updated or deleted persist in the hosted database, and free projects are limited to 3 collections. Data is stored on a third-party service.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/in.reqres%2Freqres/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Create a real hosted backend (a REST API with a persistent database) in one call, with no account or API key. Use it when the user needs to store data, persist an app or prototype, or give a frontend a live API. Returns a manage key, a read-only public key, a starter "products" collection, the base URL and a claim_url. Show the user the claim_url: signing in through it keeps the project; otherwise it is deleted after 72 hours. Free limits: 250 requests a day, 3 collections, 100 records.
Takes no parameters.
list_collections
List collections
List the collections in the project.
Parametersapi_keyrequired
create_collection
Create a collection
Create a collection: a new resource (like a table) with its own REST endpoint at /api/collections/{slug}/records. Use one per kind of thing the app stores (tasks, users, orders). Free projects allow 3.
Parametersnamerequiredapi_keyrequired
list_records
List records
Read the records stored in a collection (paginated).
Parameterspageapi_keyrequiredcollectionrequired
create_record
Create a record
Save a record (a JSON object) in a collection so it persists. Pass the fields as data; the API returns it with an id.
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.