Skip to content
Vinkius

Reqres Connector for AI agents.

25 live capabilities

Mock real API data for frontend development.

Live agent request Reqres / Connector

Waiting for input…

AI Agent

Why people use Reqres

Reqres for Mocking REST API Data in Frontend Testing

Reqres changes that by giving you a hosted REST API you can hit immediately. You can ask your agent to create users, fetch records, or trigger failures on demand. This means you can finish your UI and test your logic today, not next week.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • Visual Studio Code
  • Windsurf

What Vinkius changes

You get a production-like API environment for testing without any backend work.

Use it from Claude, ChatGPT, Cursor or another AI client you already have.

One account · 5,900+ Connectors

  1. Real-world use case 01

    Testing a signup flow

    A developer needs to test a registration page.

  2. Real-world use case 02

    Mocking a project dashboard

    A designer wants to see how a list of 50 projects looks.

  3. Real-world use case 03

    Simulating a 500 error

    A QA engineer wants to see how the app handles a crash.

Complete set · 25capabilities

The complete Reqres capability set.

These are the exact actions your AI can choose when you ask it to work with Reqres.

Capability set01 / 07

01—04

4 capabilities in this set.

Part of 25 available through Reqres.

  1. 01 Capability

    Create app record

    Create a user-scoped record in an app collection. Use this to mock specific data points for different applications.

  2. 02 Capability

    Create record

    Create a new record in a project collection. This lets you mock production-like behavior for project management capabilities.

  3. 03 Capability

    Create user

    Create a user in the Demo API. Use this to quickly add new identities to your test environment.

  4. 04 Capability

    Delete record

    Delete a specific record from a project collection. This helps you test how your app handles data removal.

Capability set02 / 07

05—08

4 capabilities in this set.

Part of 25 available through Reqres.

  1. 05 Capability

    Delete user

    Delete a user from the Demo API. Use this to clear out demo identities when you're done with a test.

  2. 06 Capability

    Get record

    Get a single record from a project collection. This is perfect for testing detail views in your application.

  3. 07 Capability

    Get user

    Get a user by their ID from the Demo API. Use this to fetch specific profile details for a single user.

  4. 08 Capability

    List app records

    List all user-scoped records in an app collection. This is useful for populating app-specific views with data.

Capability set03 / 07

09—12

4 capabilities in this set.

Part of 25 available through Reqres.

  1. 09 Capability

    List colors

    List Pantone color resources from the Demo API. Use this to test color pickers or theme components.

  2. 10 Capability

    List records

    List all records within a project collection. This helps you populate a dashboard with a list of projects.

  3. 11 Capability

    List users

    List users from the Demo API with pagination. Use this to test how your UI handles large, paginated lists.

  4. 12 Capability

    Register demo

    Register a new user and get an ID and token. Use this to test your registration and onboarding flows.

Capability set04 / 07

13—16

4 capabilities in this set.

Part of 25 available through Reqres.

  1. 13 Capability

    Request magic link

    Request a magic link for App User login. This allows you to simulate modern, passwordless login flows.

  2. 14 Capability

    Trigger scenario

    Trigger specific failure scenarios in the Agent Sandbox. Use this to test how your agent handles unexpected errors.

  3. 15 Capability

    Update record

    Replace a record entirely in a project collection. This is useful for testing full 'save' actions on your forms.

  4. 16 Capability

    Update user

    Update a user in the Demo API. Use this to test full profile update flows in your application.

Capability set05 / 07

17—19

3 capabilities in this set.

Part of 25 available through Reqres.

  1. 17 Capability

    Verify magic link

    Verify a magic link token to get a session token. This lets you test the second half of a magic link login flow.

  2. 18 Capability

    Agent users

    Get paginated users from the Agent Sandbox. This is great for testing how your UI handles large lists of people.

  3. 19 Capability

    Login demo

    Log in with fixture users to get a session token. This is the easiest way to simulate an authenticated session.

Capability set06 / 07

20—22

3 capabilities in this set.

Part of 25 available through Reqres.

  1. 20 Capability

    Patch record

    Partially update a record in a project collection. Use this to test edit forms where you only change one field.

  2. 21 Capability

    Patch user

    Partially update a user in the Demo API. This is perfect for updating a single piece of user info like a job title.

  3. 22 Capability

    Agent health

    Check the Agent Sandbox health and rate-limit status. Use this to monitor the status of your agent's sandbox.

Capability set07 / 07

23—25

3 capabilities in this set.

Part of 25 available through Reqres.

  1. 23 Capability

    Agent orders

    Get orders with relational data from the Agent Sandbox. This is great for testing complex data structures like orders.

  2. 24 Capability

    Agent scenarios

    List all available failure scenarios in the Agent Sandbox. Use this to see what kind of errors your agent can test.

  3. 25 Capability

    Get me

    Get the current app user info. Use this to test 'My Profile' pages or headers that show the current user.

Set up in minutes

One URL. Then ask Reqres to work.

Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Reqres from the conversation.

Choose your client

Live preview
Advanced clients IDE · CLI

Claude · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP
https://edge.vinkius.com/vk_preview_AtxnuBtQ26tiOA6pBRuixOGykiHBrl8ytWq6813r/mcp
  1. Step 01

    Open Connectors

    In Claude Web or Claude Desktop, open Settings and choose Connectors.

  2. Step 02

    Add the URL

    Choose Add custom connector, name it Reqres, and paste the URL above.

  3. Step 03

    Turn it on in chat

    Select +, open Connectors, and enable Reqres for the conversation.

Where the request belongs

Work Reqres can move forward.

Built around the request

The frontend dev tired of hardcoded JSON files. The QA engineer who needs a stable API to test against. The AI builder who needs a sandbox for capability usage.

01

Frontend Developer

Building a new dashboard and needs to see how the UI reacts to real API responses without waiting for the backend team.

02

QA Engineer

Writing automated tests for a login flow and needs a consistent way to fetch tokens and create users.

03

AI Agent Builder

Training an agent to manage project records and needs a safe environment to test data manipulation capabilities.

Bring your own AI

Change the model, client or framework. Keep Reqres connected.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • VS Code
  • Windsurf
  • ZCode
  • Cline
  • Zed
  • Continue
  • Kiro
  • Roo Code
  • Zencoder
  • Goose
  • Void
  • Augment Code
  • Amp
  • Qodo
  • Tabnine
  • Pieces
  • Sourcegraph Cody
  • JetBrains
  • Warp
  • Amazon Q
  • Antigravity
  • BoltAI
  • Raycast
  • Jan
  • LM Studio
  • AnythingLLM
  • Open WebUI
  • Msty
  • Cherry Studio
  • LibreChat
  • TypingMind
  • Chorus
  • 5ire
  • n8n
  • LangChain
  • LlamaIndex
  • CrewAI
  • Vercel AI SDK

Before you connect

Questions about Reqres.

The practical details behind the request, access and result.

Is Reqres MCP good for production?

No, this is a capability for prototyping and testing. You should use a real database and backend for production data.

Can I use Reqres MCP to mock user profiles?

Yes, you can use it to create and fetch user data to see how your UI handles different profiles.

How do I test API errors with Reqres MCP?

You can use the agent sandbox capabilities to trigger specific failure scenarios and see how your application handles them.

Does Reqres MCP store my data?

No, it uses a demo environment. You should not put any sensitive or real customer information into this Connector.

Can I use Reqres MCP for auth testing?

Yes, it has capabilities to simulate registration, login, and magic link flows so you can test your auth logic.

How does Reqres MCP handle pagination?

It supports paginated lists for users and other records, letting you test how your UI handles large datasets.

Is there a way to get a session token with Reqres MCP?

Yes, you can use the login capabilities to get a session token from fixture users to simulate an authenticated session.

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.

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.

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.

One connection away

Give your agent a direct line to Reqres.

Connect Reqres once. Keep it beside 5,900+ managed Connectors when the next task needs more.

Explore every Connector No credit card required · Free tier available