3,400+ MCP servers ready to use
Vinkius
L

Bring Rpa
to LlamaIndex

Learn how to connect Cloud BOT to LlamaIndex and start using 7 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

Cancel JobExecute BotGet Bot DetailsGet Job StatusList BotsList Cloudbot FilesList Jobs

What is the Cloud BOT MCP Server?

Connect your Cloud BOT account to any AI agent and take full control of your cloud-based Robotic Process Automation (RPA) and browser-based workflows through natural conversation.

What you can do

  • Robot Orchestration — List and manage all browser automation robots in your account programmatically, retrieving detailed configuration and input parameter metadata
  • Automated Job Execution — Programmatically trigger bot executions with custom JSON parameters to coordinate high-fidelity web scraping and data entry tasks
  • Workflow Monitoring — Track the real-time status of your automation jobs and retrieve detailed logs and results to maintain perfectly coordinated RPA operations
  • File Architecture — Access and manage files within the Cloud BOT storage used or generated by your robots to maintain high-fidelity data cycles
  • Lifecycle Management — Programmatically cancel or suspend running jobs and verify API connectivity directly through your agent for instant operational reporting

How it works

1. Subscribe to this server
2. Retrieve your Access Token, Secret Key, and Public ID from the Cloud BOT dashboard (API settings)
3. Start automating your web-based workflows from Claude, Cursor, or any MCP client

No more manual logging into individual bot portals to check job progress. Your AI acts as your dedicated RPA engineer and browser automation coordinator.

Who is this for?

  • Operations Teams — instantly trigger data extraction bots and check execution histories using natural language commands
  • Growth Marketers — automate lead generation and web monitoring tasks without leaving your workspace
  • Developers & Ops — integrate high-speed browser automation into custom workflows through simple AI queries

Built-in capabilities (7)

cancel_job

Cancel a running job

execute_bot

You can pass optional input parameters as a JSON string. Trigger a bot execution

get_bot_details

Get details for a specific bot

get_job_status

Check the status of a job

list_bots

List all available RPA bots

list_cloudbot_files

List files in Cloud BOT storage

list_jobs

List recent execution jobs

Why LlamaIndex?

LlamaIndex agents combine Cloud BOT tool responses with indexed documents for comprehensive, grounded answers. Connect 7 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.

  • Data-first architecture: LlamaIndex agents combine Cloud BOT tool responses with indexed documents for comprehensive, grounded answers

  • Query pipeline framework lets you chain Cloud BOT tool calls with transformations, filters, and re-rankers in a typed pipeline

  • Multi-source reasoning: agents can query Cloud BOT, a vector store, and a SQL database in a single turn and synthesize results

  • Observability integrations show exactly what Cloud BOT tools were called, what data was returned, and how it influenced the final answer

L
See it in action

Cloud BOT in LlamaIndex

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Cloud BOT and 3,400+ other MCP servers. One platform. One governance layer.

Teams that connect Cloud BOT to LlamaIndex through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

3,400+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself3,400+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Cloud BOT in LlamaIndex

The Cloud BOT MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 7 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in LlamaIndex only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Cloud BOT
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Cloud BOT for LlamaIndex

Every tool call from LlamaIndex to the Cloud BOT MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

How does LlamaIndex connect to MCP servers?

Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.

05

Can I combine MCP tools with vector stores?

Yes. LlamaIndex agents can query Cloud BOT tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.

06

Does LlamaIndex support async MCP calls?

Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.

07

BasicMCPClient not found

Install: pip install llama-index-tools-mcp