How to Use the Vibrato MCP in LlamaIndex

Q: What happens when I use a template with Vibrato and LlamaIndex?

When you run createcallfromtemplate, the parameters used are captured by the MCP Server. This structured data gets indexed, allowing future queries to reference which specific playbook was deployed.

Q: Can I see all available templates in LlamaIndex?

Sure thing. You use listtemplates first to gather all template names and parameters. This output is then passed to the indexer, making them searchable for your users.

Build RAG knowledge bases using LlamaIndex with the Vibrato MCP Server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Vibrato MCP to LlamaIndex

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Grounding answers in live call data

Instead of hallucinating, your index uses real API results. When you execute a call via `create_call`, the resulting details—like the prompt used and the locale—get indexed into your knowledge base. This means if someone asks about 'our last billing query,' LlamaIndex can pull up the actual record from `list_calls` and ground its answer in that specific data.

Query past call status records

Need to know why a campaign failed? You run `get_call_status` for a given ID. This output becomes part of the indexable knowledge base. Users can then query their history and get answers about call outcomes, not just summaries. This moves beyond simple retrieval; it builds a searchable record of operational performance.

Building templates into search knowledge

You can make your negotiation scripts part of the index. Use `list_templates` to pull all available call templates, and then feed that output into LlamaIndex. The agent can answer questions like, 'What kind of template should I use for a service renewal?' It turns static code into actionable knowledge.

Setup guide

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

The MCP Server ensures that tool output becomes part of your searchable vector store. When the agent calls `create_call`, those parameters (phone number, prompt) are indexed immediately for later retrieval.

You index communication metadata like call status, list results from `list_calls`, and template details. This gives your RAG application a functional view of past operations.

When you run `create_call_from_template`, the parameters used are captured by the MCP Server. This structured data gets indexed, allowing future queries to reference which specific playbook was deployed.

Sure thing. You use `list_templates` first to gather all template names and parameters. This output is then passed to the indexer, making them searchable for your users.

The server touches communication metadata, specifically phone numbers and call status records. All access is managed by Vinkius, ensuring the integrity of the indexed data.

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