ReqRes
MCP server by ReqRes
Create a hosted REST backend with persistent JSON collections and API keys, with no signup, and manage records from your agent.
Connect to ReqRes
No sign-in needed. Connect with ReqRes’s own URL:
Paste it into any client that supports remote MCP servers. Your client talks to ReqRes directly, not through mcp.tc.
Share this server
Opens this page, with the URL and setup steps.
mcp.tc/i/reqresAbout
ReqRes is a hosted REST backend with persistent JSON collections, app-user auth and request logs. This server lets an agent create a project, define collections and create, list, update and delete records over plain HTTP.
It runs as a hosted Streamable HTTP endpoint at https://reqres.in/mcp. No sign-in or API key is needed to start: create_project returns a manage key, a public key and a claim URL. Projects created this way are deleted after 72 hours unless a person claims them through the claim URL. Free projects allow 3 collections.
What you can do
- Create a hosted backend project with no account
- List and create collections
- List records in a collection with pagination
- Create, update and delete records
- Get a claim URL to keep a project beyond 72 hours
Tools 12
create_projectWritesCreate a hosted backend with keys, a starter products collection and a claim URL.
list_collectionsRead-onlyList the collections in the project.
create_collectionWritesCreate a collection with its own records endpoint.
list_recordsRead-onlyList records in a collection, paginated.
create_recordWritesCreate a record in a collection from data fields.
get_recordRead-onlyGet a record
patch_recordWritesChange some fields of a record
create_app_userWritesCreate an app user
create_app_user_sessionWritesSign in as an app user
list_logsRead-onlyList request logs
update_recordCan deleteReplace a record's fields.
delete_recordCan deleteDelete a record from a collection.
Read from the live server on 18 Nov 2026. Read-only, Writes and Can delete are hints the server declares; your client decides whether to ask before running a tool.
Example prompts
Create a ReqRes project and add a todos collection.
Add three sample records to the products collection.
List all records in my orders collection.
Delete record 5 from the todos collection.
Set up
Every client connects to reqres.in. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport http reqres https://reqres.in/mcp- Start Claude Code and type
/mcp. reqres should show as connected.
Add --scope user to make it available in every project, not just this one.
Claude Desktop
- Open Customize → Connectors, click + Add, then Add custom connector.
- Name it ReqRes and paste this URL:
https://reqres.in/mcp- Click Add. Its tools appear in the chat’s tools menu.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
claude.ai
- Open the connector form on claude.ai. This button fills in the name and URL for you:
Add to claude.ai (opens in a new tab)
- Check that the URL reads
https://reqres.in/mcpand click Add. - Turn it on in a chat from the tools menu.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.
ChatGPT
- On chatgpt.com, go to Plugins, select +, then Add custom MCP server.
- Enter a name for the server.
- Under Connection, paste
https://reqres.in/mcpas the server URL, then for authentication choose No authentication. - Check I understand and want to continue, then select Create as a plugin.
Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"reqres": {
"url": "https://reqres.in/mcp"
}
}
}VS Code
Install in VS Code (opens in a new tab)
Or from a terminal:
code --add-mcp '{"name":"reqres","type":"http","url":"https://reqres.in/mcp"}'Or commit it to the repo in .vscode/mcp.json:
{
"servers": {
"reqres": {
"type": "http",
"url": "https://reqres.in/mcp"
}
}
}Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"reqres": {
"serverUrl": "https://reqres.in/mcp"
}
}
}- Refresh the MCP server list in Cascade.
Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.
Codex
codex mcp add reqres --url https://reqres.in/mcpOr edit ~/.codex/config.toml directly:
[mcp_servers.reqres]
url = "https://reqres.in/mcp"Gemini CLI
gemini mcp add --transport http reqres https://reqres.in/mcpThis adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.
{
"mcpServers": {
"reqres": {
"type": "http",
"url": "https://reqres.in/mcp"
}
}
}Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.
Client only starts local servers? Bridge it with npx -y mcp-remote https://reqres.in/mcp.
Embed
Show ReqRes in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work
The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.
README badge
[](https://mcp.tc/i/reqres)<a href="https://mcp.tc/i/reqres"><img src="https://mcp.tc/i/reqres/badge.svg" alt="ReqRes on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/reqres.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/reqres" title="ReqRes on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/reqres.jsonAI prompt
Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the ReqRes card to your site.
Add the mcp.tc card for ReqRes, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.
Put this tag where the card should appear. The card renders right before it:
```html
<script src="https://mcp.tc/w/reqres.js" async></script>
```
To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.
```html
<div data-mcptc="reqres"><a href="https://mcp.tc/i/reqres">ReqRes on mcp.tc</a></div>
```
Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.
If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).
For a README or other Markdown docs, use the badge instead:
```markdown
[](https://mcp.tc/i/reqres)
```
Reference: https://mcp.tc/embedChange history
We read this server’s tool list every 3 hours and record what changes. Last read 18 Nov 2026, 02:37 UTC.
-
5 tools added and 1 tool changed.
Details, 8 Nov 2026, 23:49 UTC
Added 5
create_app_userWritesAdd an end user to the project (for apps where each user sees only their own records). No email is sent. Then call create_app_user_session to act as that user.
create_app_user_sessionWritesGet a 6-hour session token for an app user without email. Send it as Authorization: Bearer <session_token> to https://reqres.in/app/collections/{collection}/records, where the user only sees their own records. Real users sign in with an emailed code via /api/app-users/login.
get_recordRead-onlyRead one record by id.
list_logsRead-onlySee recent requests to the project (method, path, status, timing), newest first. Use it to debug why an app's calls fail.
patch_recordWritesMerge the given fields into a record and keep the rest, e.g. {"done": true} to tick off a task. Use this for most edits.
Changed 1
update_recorddescription and titleBeforeReplace a record's
fields.AfterReplace all of a record's fields: fields you leave out are removed. To change some fields and keep the rest, use patch_record.
title
BeforeUpdatea recordAfterReplace a record
-
7 tools changed.
Hint changed: may modify data
Details, 21 Oct 2026, 13:42 UTC
Changed 7
create_collectionhintsreadOnlyHintnot set changed to nodestructiveHintnot set changed to noopenWorldHintnot set changed to noidempotentHintnot set changed to no
create_projecthintsreadOnlyHintnot set changed to nodestructiveHintnot set changed to noopenWorldHintnot set changed to noidempotentHintnot set changed to no
create_recordhintsreadOnlyHintnot set changed to nodestructiveHintnot set changed to noopenWorldHintnot set changed to noidempotentHintnot set changed to no
delete_recordhintsreadOnlyHintnot set changed to nodestructiveHintnot set changed to yesopenWorldHintnot set changed to noidempotentHintnot set changed to yes
list_collectionshintsreadOnlyHintnot set changed to yesopenWorldHintnot set changed to no
list_recordshintsreadOnlyHintnot set changed to yesopenWorldHintnot set changed to no
update_recordhintsreadOnlyHintnot set changed to nodestructiveHintnot set changed to yesopenWorldHintnot set changed to noidempotentHintnot set changed to yes
-
4 tools changed. Server instructions changed.
New server instructions
Details, 16 Oct 2026, 13:40 UTC
Changed 4
create_collectiondescriptionBeforeCreate a
collection (a RESTresource with its ownrecords endpoint).Free projects allow3 collections.AfterCreate 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.
create_projectdescriptionBeforeCreate a hosted
ReqResbackend with noaccount: returns keys,a starter "products"collectionand a claim_url.Free-plan limits. Deletedafter 72hours unlessahuman claims it via claim_url.AfterCreate 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.
create_recorddescriptionBeforeCreatea record in acollection.Pass therecordfields asdata.AfterSave a record (a JSON object) in a collection so it persists. Pass the fields as data; the API returns it with an id.
list_recordsdescriptionBeforeListrecords in a collection (paginated).AfterRead the records stored in a collection (paginated).
Server instructions
BeforeReqRes
isa hostedREST backend:persistent JSONcollections, app-user authand requestlogs, called with plain HTTP.Start with create_project (no accountneeded) to get a project, a managekeyand a public key.Then use the collection and record tools, or call https://reqres.in/api/collections/{collection}/records directly with the x-api-key header (record bodies are wrapped as {"data": {...}}).Projects created this wayare deleted after 72hours unlessahuman claims them: always give the user the claim_url.AfterReqRes gives you a real hosted backend in one call, with no signup: persistent JSON collections the app can read and write over HTTP, API keys and request logs. Use it whenever the user needs somewhere to store or serve data: a database or backend for an app, prototype, demo or script; saving data from this conversation so it persists; a live REST API for a frontend to call; or realistic data behind a real endpoint. Start with create_project (no account or API key needed). Then use the collection and record tools, or call https://reqres.in/api/collections/{collection}/records directly with the x-api-key header (record bodies are wrapped as {"data": {...}}). Always show the user the claim_url and tell them that signing in through it keeps the project for free. Unclaimed projects are deleted after 72 hours. Free limits: 250 requests a day, 3 collections and 100 records per project.
-
Tracking started: 7 tools.
FAQ
Can I paste mcp.tc/i/reqres into my MCP client?
No. mcp.tc links are pages, not server addresses. Connect with https://reqres.in/mcp, so your client talks to ReqRes directly. The quick link is for sharing: it opens this page, with setup steps for every client.
Does ReqRes need an API key or a sign-in?
No. ReqRes doesn’t ask for an account or key.
Is ReqRes a remote or a local server?
Remote. ReqRes hosts it at https://reqres.in/mcp, and it speaks Streamable HTTP. There’s nothing to install.
What can ReqRes do?
It has 12 tools, including create_project, list_collections and create_collection. You can create a hosted backend project with no account, list and create collections and list records in a collection with pagination.
Which clients can use it?
Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.
Does mcp.tc track changes to ReqRes?
Yes. ReqRes’s History tab shows each change we find to its tools, down to descriptions and parameters, plus new versions and edits by its owner. Follow the listing to get an email when it changes.
Who wrote this page?
mcp.tc’s robot read ReqRes’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
mcp.tc isn’t affiliated with ReqRes. This page was built from ReqRes’s public metadata, last checked on 18 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.