# GoRest MCP > GoRest provides direct access to a full suite of mock RESTful data resources, perfect for building prototypes and running QA tests. Your AI agent performs standard CRUD operations on users, posts, comments, and todos—simulating a real social platform environment without needing a live backend connection. ## Overview - **Category:** productivity - **Price:** Free - **Tags:** rest-api, mock-data, crud, testing, json-api ## Description Building out a new feature that needs realistic data? You don't want to spend time setting up mock databases just for testing; you need immediate access. GoRest lets your agent interact with structured resources like user profiles, blog posts, and comments using standard API actions. This means you can run complex data flows—for example, simulating a comment being added to a specific post, or creating an entire user account from scratch. It’s essential for developers needing repeatable testing environments or just wanting to quickly simulate how real-world application data moves through different parts of your logic. Since Vinkius hosts this MCP in the catalog, you connect once using your preferred AI client and get all these data actions instantly available. ## Tools ### create_comment Adds new comment content to an existing piece of material. ### create_post_comment Attaches a new comment specifically to a targeted post ID. ### create_post Generates and saves a brand-new blog post record. ### create_todo Generates and saves a simple task item. ### create_user_post Generates and saves a post while automatically linking it to a specified user ID. ### create_user_todo Creates a new todo item and assigns ownership to a specific user. ### create_user Creates an entirely new user profile record in the system. ### delete_post Removes an existing blog post from the system. ### delete_user Permanently removes a user profile account. ### get_comment Retrieves and displays content for one specific comment record. ### get_post Fetches the details of a single post by its ID. ### get_todo Retrieves all data for one specific task item. ### get_user Fetches the complete profile details for a single user. ### list_comments Retrieves paginated lists of all comments across the platform. ### list_post_comments Lists and retrieves all comments associated with a given post ID. ### list_posts Retrieves paginated lists of all available posts. ### list_todos Retrieves paginated lists of all tasks across the system. ### list_user_posts Lists every post that has been authored by a specific user ID. ### list_user_todos Lists all to-dos owned by and assigned to a specific user ID. ### list_users Retrieves paginated lists of all user accounts in the system. ### replace_user Overwrites or replaces an existing user profile with new data (full replacement). ### update_post Modifies specific details of a post that already exists. ### update_user Makes partial changes to an existing user profile, leaving other fields untouched. ## Prompt Examples **Prompt:** ``` List the first 10 active female users from GoRest. ``` **Response:** ``` I've retrieved the users. Here are the first 10 active female profiles, including 'Aditi Sharma' (ID: 12345) and 'Meera Patel' (ID: 12346). ``` **Prompt:** ``` Create a new post for user 54321 with the title 'MCP Integration' and a short body text. ``` **Response:** ``` The post has been successfully created for user 54321. The new post ID is 98765. ``` **Prompt:** ``` Delete the user with ID 13579. ``` **Response:** ``` User 13579 has been successfully deleted from the system. ``` ## Capabilities ### Manage User Profiles Create, read, update, and delete user accounts; you can also fetch specific details like gender or status. ### Handle Content Lifecycle Build and manage posts, including fetching all comments associated with a particular piece of content. ### Manage Tasks (Todos) Create, retrieve, or update simple to-do list items tied to specific user accounts. ### Simulate Data Creation Automatically generate related data records, like creating a post and assigning it immediately to an existing user. ### Filter Specific Records Query the system for users or posts using filters based on attributes like name, email, or status. ## Use Cases ### Simulating Content Moderation A QA engineer needs to check if a user can only delete content they created. They ask their agent to first run `create_user` and then use `create_post_comment`. Finally, they test the deletion using `delete_post`, confirming that ownership checks pass every time. ### Building Onboarding Flow Prototypes A developer needs to show a client how new users interact with the system. They ask their agent to use `create_user` and then immediately follow up by calling `list_user_todos` for that newly created ID, proving the todo list is initialized. ### Debugging Data Consistency A data analyst needs to know all content associated with a specific user. They combine calls: first using `get_user` to confirm identity, then running `list_user_posts`, and finally calling `list_user_todos` for completeness. ### Testing Account Suspension An engineer needs to simulate a user being suspended. They run `get_user` to fetch the original record, then use `update_user` to change their status attribute, proving that related content (like posts) can still be retrieved but flagged as inactive. ## Benefits - Build out user stories quickly. You can use `create_user` and `update_user` to simulate a user changing their status or profile details, letting you test complex state logic immediately. - Test content relationships easily. Combine tools like `get_post` with `list_post_comments` in your agent workflow; this lets you prove that every post can correctly pull all its related comments. - Manage the entire data lifecycle. From creating a user (`create_user`) to deleting them (`delete_user`), your agent handles the full account flow, which is crucial for testing permissions and cleanup routines. - Improve QA coverage with targeted tools. Instead of fetching everything, you can use `list_user_posts` or `list_user_todos` to only grab content relevant to a specific user ID, making tests faster and more precise. - Prototype complex interactions. Need a new post assigned immediately? Use the combination of `create_user_post` which handles both creation steps in one call, simulating real-world data pipelines. ## How It Works The bottom line is: You connect with your credentials once and use structured commands to perform complex mock operations on demand. 1. First, subscribe to this MCP and enter your GoRest Access Token. 2. Your AI client authenticates with the Vinkius platform and establishes a connection using that token. 3. You then tell your agent exactly which data operation you need—for instance, 'List all posts authored by user 54321'—and it executes the request. ## Frequently Asked Questions **How do I list every user and their associated posts using GoRest MCP?** You must first use the `list_users` tool to get all IDs. Then, for each ID you need content from, call `list_user_posts` to gather all related posts. **Can I simulate a user deleting their account with GoRest MCP?** Yes. You use the `delete_user` tool to remove the profile. If you also want to clear their content, run `list_user_posts` first to get all post IDs, and then delete those posts individually. **What is the difference between `create_post` and `create_user_post`?** `create_post` only makes a stand-alone blog post. Use `create_user_post` when you need to ensure that the new post record is immediately and correctly associated with a specific user ID. **Does GoRest MCP support fetching comments on old posts?** Yes, use `get_post` first to get the target content. Then, run `list_post_comments`, providing the post ID you just retrieved, to fetch all associated comment data. **What is the best practice for handling rate limits when I use `list_posts`?** You should implement exponential backoff logic into your agent. If you hit a limit, wait and retry the request. This prevents temporary service blocks and ensures reliable data retrieval. **If I call `create_post_comment` with an invalid Post ID, what error should my AI client expect?** The API will return a 404 Not Found status code. Always confirm the parent resource exists before attempting to add a comment to it. **How does the MCP handle authorization when I use `update_user`?** Your agent must provide an access token with sufficient scope permissions. The system validates that the authenticated user has permission to modify the target profile data. **Can I filter results beyond pagination when listing records with `list_users`?** Yes, you can apply advanced filters directly in the list query parameters. You can narrow down searches by attributes like status or gender before retrieving the final set of users. **Can I filter users by their status or gender using this server?** Yes! The `list_users` tool supports optional filters for `name`, `email`, `gender`, and `status`, allowing you to narrow down the results easily. **Is it possible to perform partial updates on a user profile?** Absolutely. Use the `update_user` tool to modify specific fields like email or status without needing to provide the entire user object. **How can I view all comments across the platform?** You can use the `list_comments` tool, which supports pagination to help you browse through all recorded comments in the system.