# Cloud BOT MCP MCP > Cloud BOT MCP lets your AI agent run complex web tasks and automate entire workflows in the cloud. It's your full command center for Robotic Process Automation (RPA), allowing you to trigger bots, scrape data from forms, or navigate websites using natural conversation. You manage job execution, monitor real-time status, and even cancel runaway processes—all without leaving your chat window. ## Overview - **Category:** productivity - **Price:** Free - **Tags:** rpa, web-scraping, no-code, workflow-automation, cloud-execution, task-automation ## Description This MCP gives your AI agent full control over cloud-based browser robots. Instead of logging into individual bot dashboards to run a scrape or check a job's progress, you simply tell your AI client what needs doing. Your agent takes over the role of an RPA engineer, coordinating web tasks and data extraction in the background. You can list available bots, trigger complex runs with custom parameters, and track every step until completion. This is how Vinkius integrates high-fidelity browser automation into simple conversation flows. It lets you handle everything from lead generation to massive data dumps without writing a single line of boilerplate code. ## Tools ### cancel_job Stops an active job immediately by providing its specific job ID. ### execute_bot Starts a bot execution run, allowing you to pass custom parameters like URLs or JSON data. ### get_bot_details Pulls specific configuration and metadata for one particular bot by ID. ### get_job_status Checks the current status and logs of an existing job ID. ### list_bots Retrieves a list of every available RPA bot configured in your account. ### list_cloudbot_files Lists all files that have been saved or generated in the cloud storage area. ### list_jobs Shows a list of recent automation jobs that have run through the system. ## Prompt Examples **Prompt:** ``` List all available browser robots in my Cloud BOT account. ``` **Response:** ``` I've retrieved your robots. You currently have 3 active bots, including 'Price Scraper' (ID: bot_123) and 'Form Submitter'. Which one should we execute or inspect for details? ``` **Prompt:** ``` Execute the 'Price Scraper' bot (ID: 'bot_123') with URL 'vinkius.com'. ``` **Response:** ``` Automation triggered! I've started the 'Price Scraper' robot with your custom URL. The job ID is 'job_456'. I'll monitor the status and notify you as soon as the results are available. ``` **Prompt:** ``` Show the status and logs for automation job 'job_456'. ``` **Response:** ``` Fetching status... Job job_456 is currently 'Success'. The bot successfully extracted 15 data points. I've also found an output file 'results.csv' in your storage. Would you like the download link? ``` ## Capabilities ### Manage Bot Inventory You can list all available bots and retrieve detailed configuration for each one. ### Execute Web Tasks Trigger a bot execution, passing custom data like specific URLs or JSON parameters. ### Monitor Job Status Check the live status of any running automation job and pull detailed logs and results. ### Control Workflow Lifecycle Cancel jobs that are running too long or suspend processes when they’re finished. ### Manage Output Files Access and organize files created by the bots within the dedicated cloud storage area. ## Use Cases ### Daily Lead Scraping Cycle A growth marketer needs 50 competitor data points. They ask their agent to execute a bot, passing the target site URL and desired form fields as JSON parameters. The system runs the job, updates on progress, and saves all results for later download via `list_cloudbot_files`. ### Debugging Failed Pipelines A developer suspects a bot failed during execution. Instead of diving into complex logs, they ask their agent to check the job status using `get_job_status` and review the detailed output provided by the tool. ### Emergency Process Interruption An operations engineer runs a bot that starts cycling indefinitely. They quickly issue a command to cancel the job using `cancel_job`, preventing unnecessary resource consumption and system overload. ### Inventory Check Before Deployment A team leader needs to know what automation tools are available for a new project. They simply ask the agent to list all bots, which uses `list_bots` to provide an immediate inventory of every usable asset. ## Benefits - You stop manually logging into bot portals. Your AI agent handles all job orchestration, allowing you to trigger bots and monitor status simply by asking your client a question. - Need to check if the data is ready? Use `get_job_status` on an active job ID. You get real-time feedback and full logs immediately, so you know exactly where things stand. - Stop losing track of output files. By running `list_cloudbot_files`, your AI can show you every saved result and help you retrieve the download link instantly. - If a bot gets stuck or runs too long, don't panic. You can use `cancel_job` to stop it immediately with just its job ID. - The setup is clean. Instead of needing specific code for every action, your agent uses simple queries like those provided by `list_bots` and `get_bot_details` to guide you through the process. ## How It Works The bottom line is: Your AI client acts as a dedicated RPA coordinator, running complex browser tasks without you ever opening a web dashboard. 1. First, subscribe to this MCP on Vinkius. Then, get your Access Token, Secret Key, and Public ID from the Cloud BOT dashboard. 2. Next, connect those credentials to your AI client (Claude, Cursor, etc.). Your agent now has direct control over the bot's API. 3. Finally, tell your agent what you want done—like 'Run the lead scraper on vinkius.com.' The job runs in the cloud, and your conversation updates with the status. ## Frequently Asked Questions **How do I find out what bots are available using list_bots?** You simply ask the agent to call `list_bots`. It returns a full inventory of every bot you've set up, giving you their names and IDs so you know exactly what tools are at your disposal. **What happens if my job is running too long? Can I use cancel_job?** Yes. If a process runs indefinitely, you can ask the agent to `cancel_job`. You just need to provide the specific job ID for the bot to stop the execution immediately. **I ran a scrape; where do I find the output data? Should I use list_cloudbot_files?** The results are saved in the cloud storage. Ask your agent to call `list_cloudbot_files` to see what files were generated, and then you can retrieve the necessary download link. **How do I start a new scraping task using execute_bot?** You use `execute_bot`. You must provide all required parameters in JSON format—this includes the bot ID, the URL, and any specific fields you want the scraper to look for. **How do I view my historical runs and job IDs using list_jobs?** You can see a comprehensive log of all your past automation attempts. This function retrieves metadata for executed jobs, letting you track when they ran, who triggered them, and their initial status. It's essential for auditing performance or finding the ID needed to check an old job's specific details. **What information can I get about a specific bot using get_bot_details?** This tool gives you all the technical specifics of a single robot, including its configuration parameters and intended purpose. You use this to confirm if the bot is set up correctly for your task before triggering it. It’s how you verify that 'Price Scraper' actually expects a URL parameter. **If my web scraping job fails when I run execute_bot, where do I find the error log?** The detailed logs are retrieved using get_job_status. Instead of just looking for 'Success,' check the status field for failure codes and associated messages. This tells you exactly why the bot quit—whether it was a timeout, an element not found, or bad parameters. **I'm setting up my account; do I need to verify connectivity before using any tools?** Yes, always confirm your API connection first. While there isn't one specific tool for this, you can test the full setup by listing all available bots with list_bots. If that works, it confirms your access token and secret key are correctly registered with Vinkius. **How do I find my Cloud BOT API credentials?** Log in to your account, navigate to the **API Settings** section, and you will find your Access Token, Secret Key, and Public ID. **Can I pass custom parameters to a bot?** Yes! The `execute_bot` tool accepts a `params_json` string where you can provide a JSON object matching your bot's input configuration. **How do I check the results of an automation?** Use the `get_job_status` tool with a job ID to retrieve the execution status and any outputs or files generated by the bot.