DummyJSON MCP. Mock every API call and data flow without a live backend.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
DummyJSON accesses a massive, simulated data pool for testing any API interaction—products, user profiles, posts, recipes, and carts. You don't need a backend; your AI agent handles all CRUD operations by calling specific tools like `add_product` or `list_users`.
It’s instant structured data mocking for development and QA.
What your AI agents can do
Add cart
Creates a new simulated shopping cart record.
Add comment
Simulates adding a new comment to content.
Add post
Adds a completely new post entry.
Your AI client performs login simulations using auth_login to generate JWT tokens, allowing it to test session-dependent calls like auth_get_me.
The agent can simulate adding, fetching, updating, and deleting products using tools like add_product, get_product, and delete_product.
You can test entire content ecosystems by retrieving posts (list_posts), finding comments for a specific post (get_comments_by_post), and updating the original data with tools like update_post.
The system allows your agent to narrow down results across multiple domains, using functions such as search_products, filter_users, or get_posts_by_user.
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
DummyJSON MCP Server: 61 Tools for Data & User Operations
These 61 tools allow your AI agent to perform every basic CRUD operation imaginable—from adding a post to updating user profiles—all using simulated dummy data.
019e5d13add cart
Creates a new simulated shopping cart record.
019e5d13add comment
Simulates adding a new comment to content.
019e5d13add post
Adds a completely new post entry.
019e5d13add product
Creates and simulates a new product listing in the catalog.
019e5d13add recipe
Adds a new recipe to the database.
019e5d13add todo
Adds a new task item (todo).
019e5d13add user
Creates and simulates a new user profile.
019e5d13auth get me
Retrieves the profile data for the currently authenticated user.
019e5d13auth login
Simulates user login and returns dummy JWT access and refresh tokens.
019e5d13auth refresh token
Extends the session by simulating a refresh token exchange.
019e5d13delete cart
Deletes an existing shopping cart record entirely.
019e5d13delete comment
Removes a specific comment by its ID.
019e5d13delete post
Permanently deletes a post entry from the content repository.
019e5d13delete product
Simulates removing a product from the catalog.
019e5d13delete recipe
Removes an existing recipe by ID.
019e5d13delete todo
Deletes a specific todo item.
019e5d13delete user
Simulates deleting a user account and associated data.
019e5d13filter users
Narrows down a list of users based on specific key/value criteria.
019e5d13get cart
Retrieves the details for a single shopping cart using its ID.
019e5d13get comment
Gets the content and metadata for one specific comment by ID.
019e5d13get comments by post
Retrieves all comments associated with a given post ID.
019e5d13get post
Fetches the full details of one specific post by its ID.
019e5d13get post comments
Retrieves all comments connected to a given post.
019e5d13get posts by user
Lists all posts written by a specific user ID.
019e5d13get product
Fetches the full details for one product using its unique ID.
019e5d13get products by category
Lists all products belonging to a specified category.
019e5d13get quote
Retrieves the details of one specific quote by ID.
019e5d13get random quote
Gets a single, random quote to simulate content feeds.
019e5d13get random quotes
Retrieves up to ten random quotes for bulk testing.
019e5d13get random todo
Pulls a single, randomly generated todo item.
019e5d13get recipe
Fetches the full details of one recipe using its ID.
019e5d13get recipes by meal type
Lists all recipes that match a specific meal type (e.g., breakfast, dinner).
019e5d13get recipes by tag
Filters and returns recipes based on one or more tags.
019e5d13get todo
Fetches the details for a single todo item by ID.
019e5d13get user
Retrieves the full profile of one user given their ID.
019e5d13get user carts
Lists all shopping carts associated with a specific user account.
019e5d13get user posts
Retrieves posts written by a particular user ID.
019e5d13get user todos
Lists all todo items belonging to one specific user.
019e5d13list carts
Retrieves a list of all existing shopping carts globally.
019e5d13list categories
Gets a full listing of available product categories.
019e5d13list category list
Returns a simple list containing all available category names.
019e5d13list comments
Retrieves every comment stored in the system.
019e5d13list post tags
Gets a comprehensive list of all available post tags.
019e5d13list posts
Retrieves a full listing of every post entry.
019e5d13list products
Returns a complete list of every product in the catalog.
019e5d13list quotes
Retrieves a full listing of all stored quotes.
019e5d13list recipe tags
Gets a complete list of tags used for recipes.
019e5d13list recipes
Retrieves every recipe entry in the database.
019e5d13list todos
Returns a complete listing of all todo items.
019e5d13list users
Gets a full roster of every user profile in the system.
019e5d13search posts
Searches through posts using specific keywords or filters.
019e5d13search products
Searches for products by name, description, or keyword.
019e5d13search recipes
Searches recipes based on keywords or ingredients.
019e5d13search users
Finds users matching specific search criteria (e.g., by name).
019e5d13update cart
Updates the items or quantities within a specified shopping cart.
019e5d13update comment
Modifies the text of an existing comment.
019e5d13update post
Edits the content and metadata of a post after it's been published.
019e5d13update product
Updates product details, such as price or description (simulated).
019e5d13update recipe
Modifies the ingredients or instructions of a recipe.
019e5d13update todo
Marks a todo item as complete or changes its due date.
019e5d13update user
Changes user details, like email or name, for an existing account.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with DummyJSON, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
DummyJSON gives your AI agent a massive sandbox to play in. You're not hooking up to a real backend, so you don't sweat setting up databases or worrying about live data integrity. This server lets your agent run any kind of CRUD operation—create, read, update, delete—against simulated structured data for testing and quality assurance.
It’s instant mocking for whatever API interaction you need."
"Your AI client handles the heavy lifting by calling specific tools. Here's a breakdown of what your agent can do with this pool of fake data:
User Accounts and Authentication Flow
It starts with user profiles. Your agent runs auth_login to simulate logging in, which returns dummy JWT access and refresh tokens, letting you test session-dependent calls like auth_get_me, which retrieves the profile for the logged-in user. To manage accounts generally, your agent can create a new profile using add_user, update existing details with update_user (like changing an email or name), and delete an account entirely via delete_user.
For directory testing, it runs list_users to get the full roster of every profile, or uses get_user and filter_users to pull specific user data based on criteria. Furthermore, your agent can see all shopping carts linked to a particular person using get_user_carts."
"### Product Catalog and E-commerce
Testing an e-commerce flow is simple. Your agent runs list_products for every item in the catalog or uses search_products to find goods by name, description, or keyword. For targeted testing, it pulls all items using get_products_by_category, which requires a category ID. The lifecycle of any product can be tested: your agent creates listings with add_product, fetches full details with get_product, modifies prices or descriptions using update_product, and simulates removal via delete_product.
You'll also find tools to manage categories, running list_categories for a complete listing or just list_category_list to get the simple names."
"### Content Management: Posts and Comments
This server lets you simulate an entire blogging platform. To view content, your agent runs list_posts to get every post entry available or uses search_posts to filter posts using keywords or specific criteria. You can fetch all details for one piece with get_post, and if the user is associated with a post, they can see it via get_user_posts.
The commenting system is robust: your agent retrieves every comment stored in the system by calling list_comments, or gets the full content of one specific comment using get_comment and its ID. When testing related posts, it calls get_comments_by_post to get all comments for a given post ID, or uses get_post_comments to retrieve those connected to a specific post object.
Creating new content involves running add_post, which adds an entirely new entry, or using update_post to edit the content and metadata of one that's already out there. For cleanup, it runs delete_post to permanently remove a piece of content."
"### Recipes and Cooking Data
If you’re building anything food-related, this works. Your agent can run list_recipes to see every recipe in the database or use search_recipes if it needs to find recipes based on keywords or ingredients. For specific filtering, it retrieves all meals matching a type (like dinner) using get_recipes_by_meal_type, or filters by required tags with get_recipes_by_tag.
The recipe lifecycle includes adding new ones with add_recipe, fetching full details via get_recipe, modifying ingredients through update_recipe, and removing them with delete_recipe. It also helps manage the taxonomy, running list_recipe_tags to see what tags are available."
"### Shopping Carts and To-Do Lists
For e-commerce transactions, your agent can run list_carts to get a global view of all carts. It creates a new cart with add_cart, reads the details of one specific cart using get_cart, modifies items or quantities in an existing cart via update_cart, and wipes it clean entirely with delete_cart. For task management, your agent runs list_todos to get every item.
It adds a new task with add_todo, fetches details for one specific todo using get_todo, marks things as done or changes due dates by running update_todo, and clears items out with delete_todo."
"### Quotes, Search, and Random Data
For quick content feeds, your agent pulls a single random quote using get_random_quote, or grabs up to ten for bulk testing by running get_random_quotes. It can list every stored quote with list_quotes or get one specific quote detail using get_quote. The system also offers general search capability: run search_users to find people matching criteria, or use the dedicated search_products and search_recipes functions for deep searches.
Finally, it includes helper tools like get_random_todo, which pulls a single random task item.
How DummyJSON MCP Works
- 1 Subscribe to the DummyJSON server on Vinkius.
- 2 Your AI client identifies the specific tool needed (e.g.,
add_cart) and passes the required parameters. - 3 The server executes the dummy operation and returns structured JSON data, which your agent then uses for the next step in the workflow.
The bottom line is: You get instant access to a massive set of simulated API endpoints, letting you test complex logic without ever touching a real database.
Who Is DummyJSON MCP For?
Any developer who needs predictable data for testing—QA engineers tired of setting up flaky mock servers; frontend developers blocked by slow backend development cycles; or AI researchers needing a controlled sandbox to train agents on API calls.
Needs immediate JSON structures for UI components. They use tools like list_products and get_user to mock data while the actual backend team works.
Tests edge cases, especially bad API responses or complex workflows. They rely on deterministic endpoints like delete_product and update_todo to validate system logic.
Trains agents on tool-calling sequences. The goal is teaching the agent to correctly chain calls, for example, using auth_login before calling any data retrieval tools.
What Changes When You Connect
- Test full user flows instantly. You can simulate the entire authentication process—calling
auth_loginto get tokens, then using those tokens with tools likeget_user_cartsorlist_products. It’s perfect for testing security logic without needing a real auth service. - Run complex CRUD operations across domains. Need to test product updates? Use
update_productand follow up by listing the new item viaget_product. This verifies your UI/UX handles data mutations correctly, even if it's just dummy data. - Simulate deep content interactions. You can model a full blog experience: retrieving all posts with
list_posts, then finding comments for a specific post usingget_comments_by_post, and finally simulating an edit withupdate_comment. It’s a perfect, contained test environment. - Test data constraints easily. Need to see how your app handles zero results? Use
search_productsorlist_userswith parameters that guarantee no matches. The predictable dummy response lets you build reliable error-handling code. - Manage multiple entities in one session. Don't jump between mock services for users, products, and recipes. You can run user setup (
add_user), then fetch their data (get_user), and finally simulate them buying a product usingadd_cartall within the same agent call.
Real-World Use Cases
A New E-commerce Feature Needs Testing
The client wants to test how their checkout page behaves. They ask their agent to first list available products using list_products. Next, they simulate a user adding three items using multiple calls to add_cart. Finally, the agent uses update_cart to change the quantity of one item and reports the final cart total. The problem is solved—the frontend logic works.
Debugging User Profile Data on Signup
A developer needs to verify that when a user signs up, their profile data updates correctly across multiple services. They first call add_user, then immediately use get_user and check the returned fields against the expected schema. This confirms the basic write/read cycle works before connecting it to production systems.
Building a Content Moderation Tool
The QA team must verify that deleting content triggers proper cascades. They run get_post to get an ID, then use get_comments_by_post to grab existing comments. Finally, they call delete_post, which confirms the main piece of data is removed and simulates clean-up.
Modeling a Recipe/Blog Integration
A researcher needs to show how recipes can be featured on blog posts. They use list_recipes to get available meal types, then use that list in conjunction with get_posts_by_user to retrieve the content where those recipes are mentioned.
The Tradeoffs
Assuming persistence between calls
The agent runs add_product and then asks for a list of all products. They expect the new product to appear, but it doesn't because they think the data is saved.
→
Remember this is a simulation. The tools only return dummy data based on their input structure. To test persistence, you must manually chain actions: 1. Use add_product (to create). 2. Immediately use get_product or list_products with the correct parameters to verify the simulated read.
Mixing search and list endpoints
Trying to find a specific user using list_users because they forget there's a dedicated search tool. This results in an unnecessarily large dataset.
→
If you know the criteria, always use the targeted search tools: Use search_user or filter_users. Only use list_users when you genuinely need to see every single record available.
Skipping authentication steps
Trying to call a protected endpoint like get_user_carts without first running auth_login. The API fails because it expects tokens.
→
Always start your workflow by simulating the login. Run auth_login first. This gives you the required dummy JWT tokens, which you then pass to all subsequent actions that require authentication.
When It Fits, When It Doesn't
Use this server if your goal is purely prototyping, demonstrating capability, or running integration tests where a live backend connection isn't available—or shouldn't be. The strength here is its breadth; it covers e-commerce (products/carts), content (posts/comments), and user management across dozens of endpoints. Don't use this if you need actual data persistence, payment processing, or real-time inventory counts. For those needs, connect to a true backend service using a dedicated API gateway tool instead.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by DummyJSON. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 61 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Waiting for the Backend Team is Dead Time.
You've got an amazing UI built out. The product manager says it looks great, but every time you hit 'checkout', or try to fetch a user profile, your code hits a 503 error: 'Backend service unavailable.' You spend hours writing placeholder logic and debugging the empty state.
With DummyJSON MCP Server, that stops immediately. Instead of waiting on flaky staging environments, you call `get_user` or `list_products`. Your agent gets back structured JSON data instantly. You get to build the whole experience—the 'happy path' and the 'error path'—without ever needing a database connection.
DummyJSON MCP Server: Master Data Operations in One Place
Manually mocking data used to mean maintaining dozens of separate mock endpoints across multiple services (one for users, one for posts, etc.). You had to switch between different documentation pages and copy/paste boilerplate JSON.
Now, you call a single tool. Need product info? Use `get_product`. Need user history? Use `get_user_carts`. The unified server means your agent sees one consistent namespace of data operations, making complex workflows feel native.
Common Questions About DummyJSON MCP
How do I test a full user session flow with DummyJSON MCP Server? +
Start by calling auth_login to get your dummy JWT tokens. Then, pass those credentials to any protected endpoint like get_user_carts or list_posts. The server simulates the entire authenticated journey.
Can I simulate updating multiple records at once? (DummyJSON) +
You can chain updates. For example, you first use update_product to change a price, and then follow up with another tool like get_products_by_category to verify the updated data is returned.
What's the difference between `list_posts` and `search_posts` in DummyJSON? +
list_posts retrieves every single post record available. Use it when you need a complete roster. However, if you only want posts about 'AI', use search_posts to filter down the results efficiently.
How do I test content deletion in DummyJSON? +
You just call the specific delete tool for that resource. To delete a comment, you run delete_comment. If you need to remove an entire post, use delete_post.
What should I use if my JWT token expires after running `auth_get_me`? +
You'll need to call the auth_refresh_token tool. This extends your session by using a refresh token you already have, allowing you to get a new access token without needing to re-enter credentials.
When should I use `get_user` versus calling `list_users`? +
Use get_user only when you know the user's specific ID and need their profile data instantly. If your goal is to browse, search, or check multiple users, you must call list_users first.
Does the server validate inputs like missing required fields for `add_product`? +
Yes, it simulates validation errors. If you pass an incomplete product record—for instance, omitting a name or price—the tool returns a structured error response detailing exactly which field is required.
Is this server meant for all types of content, or just e-commerce products? +
It simulates a full platform environment. You can manage and interact with various entities here, including users, carts, posts, recipes, and todos, not just products.
How can I retrieve a list of all products with a specific limit? +
You can use the list_products tool and provide the limit parameter to control the number of results returned by the API.
Is it possible to simulate adding a product to the database? +
Yes! Use the add_product tool. Note that this is a simulation; the API will return the new product object with an ID, but it won't be permanently stored.
How do I check the carts belonging to a specific user? +
Simply use the get_user_carts tool and provide the userId. The agent will return all shopping carts associated with that specific user ID.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Fourier Transform Engine
Calculate Fast Fourier Transforms (FFT) on time-series data local. Extract dominant frequencies from signals, audio, or financial cycles with mathematical perfection.
Gitea
Manage self-hosted Git via Gitea — list and manage repositories, track issues and pull requests, handle organizations, and audit branches directly from any AI agent.
TestLink
Navigate your self-hosted TestLink instance to inspect test plans, suites, cases, and builds natively via your AI agent.
You might also like
Kong Gateway
Manage your API Gateway infrastructure — list services, configure routes, and manage consumers or plugins directly from any AI agent.
HubSpot Analytics
View web analytics, track events, list reports, and get email campaign statistics through natural conversation.
Jira Cloud
Manage projects, search issues, and track tasks via Jira Cloud API.