An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Reqres to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Mock real-world data interactions without building a backend.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 25 capabilities

We ship only the actions that matter.

Capability set01 / 07

01-04

4 capabilities in this set.

Part of 25 available through Reqres.

  1. 01

    Create app record

    This capability creates a new user-scoped record within a specific app collection.

  2. 02

    Create user

    This capability generates a new user in the Demo API for testing identity flows.

  3. 03

    Delete record

    This capability removes a specific record from a project collection.

  4. 04

    Delete user

    This capability deletes a user from the Demo API.

Capability set02 / 07

05-08

4 capabilities in this set.

Part of 25 available through Reqres.

  1. 05

    List colors

    This capability retrieves a list of Pantone color resources from the Demo API.

  2. 06

    List records

    This capability pulls a list of all records currently in a project collection.

  3. 07

    Request magic link

    This capability initiates a magic link request for App User login flows.

  4. 08

    Verify magic link

    This capability verifies a magic link token to retrieve a session token.

Capability set03 / 07

09-12

4 capabilities in this set.

Part of 25 available through Reqres.

  1. 09

    Agent users

    This capability fetches paginated users using cursor pagination from the Agent Sandbox.

  2. 10

    Login demo

    This capability logs you in using fixture users to return a valid token.

  3. 11

    Patch user

    This capability performs a partial update on an existing user in the Demo API.

  4. 12

    Agent health

    This capability checks the health probe and rate-limit status of the Agent Sandbox.

Capability set04 / 07

13-16

4 capabilities in this set.

Part of 25 available through Reqres.

  1. 13

    Get me

    This capability retrieves information for the current app user.

  2. 14

    Agent orders

    This capability fetches orders containing relational data from the Agent Sandbox.

  3. 15

    Agent scenarios

    This capability lists the available failure scenarios in the Agent Sandbox.

  4. 16

    Create record

    This capability adds a new record to a project collection.

Capability set05 / 07

17-19

3 capabilities in this set.

Part of 25 available through Reqres.

  1. 17

    Get record

    This capability retrieves a single record from a project collection by its ID.

  2. 18

    Get user

    This capability fetches a specific user by their ID from the Demo API.

  3. 19

    List app records

    This capability lists all user-scoped records within an app collection.

Capability set06 / 07

20-22

3 capabilities in this set.

Part of 25 available through Reqres.

  1. 20

    List users

    This capability returns a paginated list of users from the Demo API.

  2. 21

    Patch record

    This capability applies a partial update to a record in a project collection.

  3. 22

    Register demo

    This capability registers a new user using fixture data to return an ID and token.

Capability set07 / 07

23-25

3 capabilities in this set.

Part of 25 available through Reqres.

  1. 23

    Trigger scenario

    This capability activates a specific failure scenario within the Agent Sandbox.

  2. 24

    Update record

    This capability performs a full replacement of a record in a project collection.

  3. 25

    Update user

    This capability replaces an existing user in the Demo API.

Real work

What teams actually run

01

Prototyping Frontend Apps

Connect your UI to Reqres to see how your components handle user lists and profile data.

02

Testing Agent Robustness

Use the Agent Sandbox to trigger failures and see if your agent recovers correctly.

03

Automated API Validation

Run scripts through your AI client to verify that CRUD operations work as expected.

04

Auth Flow Verification

Test registration and login logic using magic links and fixture user tokens.

Automate a task

Put Reqres to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Reqres works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put Reqres to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

1113ms average. Fast in production.

Reqres is checked daily against the live service.

Daily averagePeak 1691ms
Oct 3Today
Fastest day
889ms
Slowest day
1691ms
14-day trend
Stable+2%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 25 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Reqres, so you can see the experience inside your AI.

It does not authenticate your account with Reqres. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Reqres Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_AtxnuBtQ26tiOA6pBRuixOGykiHBrl8ytWq6813r/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Reqres capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "reqres-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_AtxnuBtQ26tiOA6pBRuixOGykiHBrl8ytWq6813r/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Reqres in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Reqres owners hand off.

This MCP is built for technical professionals who need to validate data-driven applications without building their own backend infrastructure.

  • 01

    Frontend Developers

    They use it to mock data and test UI components before the real API is ready.

  • 02

    QA Engineers

    They use it to automate API testing and validate response structures.

  • 03

    AI Builders

    They use it to provide agents with a sandbox for practicing capability usage and data manipulation.

FAQ

Questions Reqres owners ask.

  • 01

    Do I need to host my own API to use this?

    No. Vinkius hosts the MCP, and Reqres provides the hosted REST API for your data interactions.

  • 02

    Can I use this with Claude or Cursor?

    Yes. This MCP works with any MCP-compatible client, including Claude, Cursor, and Windsurf.

  • 03

    Is authentication required?

    The MCP supports authentication. You can enter an API Key or Session Token, though some demo capabilities work without it.

  • 04

    How do I test error handling?

    You can use the Agent Sandbox capabilities to trigger specific failure scenarios and monitor how your agent responds.

  • 05

    What kind of data can I manage?

    You can manage demo users, Pantone color resources, and custom project records using slugs.

  • 06

    How can I see the list of available demo users?

    You can use the list_users capability. It supports pagination, so you can specify which page you want to retrieve from the demo database.

  • 07

    Can I test authentication flows like login and registration?

    Yes! Use login_demo or register_demo with fixture emails (like 'eve.holt@reqres.in') to simulate successful authentication and receive a token.

  • 08

    How do I manage custom data for my specific project?

    Use the Project API capabilities like list_records and create_record. You just need to provide a slug to identify your collection and the JSON data payload.

Explore

More in Developer Tools

Suggestions

Connect Reqres to Claude, Cursor, ChatGPT & more