How to Use the BugBug MCP in LlamaIndex

Q: How do I index BugBug test suites in LlamaIndex?

You load the tool outputs from listsuites directly into your document pipeline. LlamaIndex parses the suite names and descriptions, making them searchable for your agent.

Index your BugBug test results and query browser run data directly within LlamaIndex.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect BugBug MCP to LlamaIndex

Create your Vinkius account to connect BugBug to LlamaIndex and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup BugBug with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Index test runs with LlamaIndex

Turn your browser testing history into a queryable knowledge base. Your agent uses `list_test_runs` to pull down run logs and store them in your vector index. Instead of digging through old test reports, you can ask your agent which tests failed most often last week. It queries the indexed data from `get_test_run` to find the patterns.

Query your QA inventory via this MCP Server

Keep your RAG pipeline updated with your current testing assets. The agent calls `list_tests` and `list_suites` to index every automated test you have configured. When you write a prompt asking to test a specific user flow, the agent searches the vector store to locate the correct test IDs before calling `run_test`.

Retrieve whitelist IPs for secure testing

Keep your firewall rules synchronized with BugBug testing infrastructure. This MCP server gets current IP ranges using `get_ips` and indexes them for your security pipelines. This ensures your staging environments are always accessible to the test runners without exposing them to the wider web.

Setup guide

Set up BugBug MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all BugBug MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to BugBug tools.",
)
response = await agent.run("List recent BugBug data")

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by BugBug. 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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect BugBug now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about BugBug MCP in LlamaIndex

You load the tool outputs from `list_suites` directly into your document pipeline. LlamaIndex parses the suite names and descriptions, making them searchable for your agent.

Absolutely. If a user asks to verify the login page, the agent searches its index for the login test, gets the ID, and calls `run_test`.

Yes, it exposes tools that feed live test status into your query engines. You can combine static documentation with live data from `get_suite_run` to answer complex QA questions.

Use the standard asynchronous tool calling pattern in LlamaIndex. The MCP client handles async requests natively, allowing you to monitor multiple suite runs in parallel.

Your test metadata and execution logs reside in your local vector index or chosen database. Vinkius merely acts as an MCP pass-through for the API payloads, ensuring no test run details are stored on our servers.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript