ReqRes MCP: a hosted backend for your coding agent

Give Claude Code, Cursor or ChatGPT a ReqRes backend

1. 1Click Connect ReqRes free. There's no sign-in, so its tools are ready at once.
2. 2Every ReqRes tool is on after you connect. Keep `create_project`, `create_collection` and `create_record` for building, and switch off `delete_record` if your coding agent shouldn't remove stored data.
3. 3Add ContextGate to your AI app as a connector or MCP server. The steps for each app are on the Works with page.
4. 4Ask your coding agent to create a ReqRes project with a collection for test users, then open Activity to see the calls.

Backend tasks for your coding agent

• Create a hosted backend with `create_project`: a REST API with a persistent database, a manage key, a read-only public key and a claim link to keep the project.
• Add a collection for each kind of thing your app stores with `create_collection`; each gets its own REST endpoint.
• Save JSON records with `create_record`, then read, update or delete them later.
• Store data that's still there next session, without setting up your own backend.

Keep test backends tidy

• Switch off any ReqRes tool; it's hidden from your AI app and refused if called.
• Policies check every call, so a real API key or password headed for a test collection can be blocked.
• Activity records every ReqRes call your coding agents make.

What you get with ReqRes and ContextGate

• Your AI apps can use ReqResClaude, Cursor, ChatGPT and other AI apps reach ReqRes through the one ContextGate connection you add to them.
• You choose which tools they can useSwitch off any ReqRes tool you don't want used. It's hidden from your AI apps and refused if called.
• Every call is checked and recordedYour policies check each call (for example, personal data is hidden and secrets are blocked), and Activity keeps a record of it.

ContextGate sees only the tool calls that go through it, not your AI app's built-in tools or your chats.

ReqRes tools

Examples of what your AI apps can do in ReqRes. You'll see the exact list of tools after you connect it.

• create_projectCreate 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
• list_collectionsList the collections in the project.
• create_collectionCreate 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.
• list_recordsRead the records stored in a collection (paginated).
• create_recordSave a record (a JSON object) in a collection so it persists. Pass the fields as data; the API returns it with an id.
• update_recordReplace a record's fields.
• delete_recordDelete a record from a collection.