How to Use the VWO MCP in LlamaIndex

Q: How does VWO account info work with LlamaIndex?

Running getvwoaccountinfo indexes your basic account details. You can then query this data later to confirm credentials or scope, grounding your application's answers in real API information.

Q: What kind of metrics are tracked by VWO using LlamaIndex?

The server tracks click and revenue goals via listconversiongoals. Indexing these results allows you to query historical goal definitions alongside your internal company documents.

Q: Can I manage feature flags with VWO and LlamaIndex?

Yes. While togglefeatureflag performs the action, indexing the list of all flags via listfeatureflags means you can ask an agent to check if a flag can be toggled before attempting it.

Q: How are VWO environments managed with LlamaIndex?

Calling listvwoenvironments provides the list of available settings (like Production or Staging). Indexing this data lets your application answer questions about which environment a specific flag is configured for.

Q: If I need campaign results, how does VWO expose that with LlamaIndex?

You use getcampaignresults to pull the stats. By indexing this output, you build an answer base that lets users query past performance data semantically, not just by ID.

Index VWO A/B test results and configurations with LlamaIndex.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect VWO MCP to LlamaIndex

Create your Vinkius account to connect VWO 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 VWO with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Search past campaign details.

Use `get_campaign_details` to pull specs for a specific VWO campaign. This output is immediately indexed into your knowledge base. Later, you can query that historical data and get grounded answers without needing the API call again. This means you build RAG applications where past test setups are part of your searchable index, not just transient API calls.

Query feature flag configurations.

The `get_feature_flag_details` tool retrieves the configuration for any VWO feature flag. When you run this through LlamaIndex, that raw JSON structure becomes a searchable document in your vector store. You can then ask natural language questions like 'What was the status of Flag X?' and get answers based on actual API data.

Find all conversion goals metrics.

Call `list_conversion_goals` to see every metric being tracked, whether it's clicks or revenue. Indexing this list means you can combine goal definitions with documents and ask complex questions about tracking setup. This lets your application answer 'Which goals are currently set up for the Staging environment?' using a unified index.

Setup guide

Set up VWO 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 VWO 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 VWO tools.",
)
response = await agent.run("List recent VWO 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 VWO. 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 VWO 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 VWO MCP in LlamaIndex

Running `get_vwo_account_info` indexes your basic account details. You can then query this data later to confirm credentials or scope, grounding your application's answers in real API information.

The server tracks click and revenue goals via `list_conversion_goals`. Indexing these results allows you to query historical goal definitions alongside your internal company documents.

Yes. While `toggle_feature_flag` performs the action, indexing the list of all flags via `list_feature_flags` means you can ask an agent to check if a flag *can* be toggled before attempting it.

Calling `list_vwo_environments` provides the list of available settings (like Production or Staging). Indexing this data lets your application answer questions about which environment a specific flag is configured for.

You use `get_campaign_results` to pull the stats. By indexing this output, you build an answer base that lets users query past performance data semantically, not just by ID.

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