How to Use the OneLocal LocalReviews MCP in LlamaIndex

Q: How do I inject OneLocal LocalReviews data into a LlamaIndex vector store?

Use llama-index-tools-mcp to load the tools. Create a FunctionAgent that calls the tools to fetch data, then write the outputs to your Document store for embedding.

Q: Can LlamaIndex query specific branches using OneLocal LocalReviews?

Yes. Your agent can call getlocation to fetch specific branch details before answering user queries about regional performance.

Q: How does LlamaIndex handle PII when indexing OneLocal LocalReviews data?

When your agent calls getreview, it retrieves real customer names and complaint details. You control the chunking and embedding process locally, ensuring PII stays within your own vector store and never leaks to public models.

Index local business feedback directly into LlamaIndex using the OneLocal LocalReviews MCP integration.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers — Included with Plan

Connect OneLocal LocalReviews MCP to LlamaIndex

Create your Vinkius account to connect OneLocal LocalReviews to LlamaIndex — we handle the hosting, security, and runtime updates so you don't have to. No server setup required.

GDPR Included with Plan

Setup OneLocal LocalReviews with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity Vinkius runs on Gemini

Gemini

Grok

Embed Customer Feedback

Your LlamaIndex application pulls live customer feedback straight from the source. By calling `list_reviews` and `get_review`, your system converts raw text from angry or happy customers into embedded documents inside your vector store. Now you can query your knowledge base to find out exactly why the downtown branch struggled last month. The agent grounds its answers in real customer complaints rather than guessing.

Ground Queries in Location Data

Local SEO strategy requires understanding your physical footprint and customer advocacy. You use `list_locations` and `list_referrals` to inject structural business data into your RAG pipeline. When a user asks which branch generates the most word-of-mouth traffic, LlamaIndex searches the embedded referral records. It returns an exact answer based on the live data it just fetched from the OneLocal API.

Index MCP Server Campaigns

Historical marketing data usually rots in a dashboard. The OneLocal LocalReviews MCP Server lets you pull `get_campaign` and `get_reputation` outputs directly into your queryable index. You ask your agent to compare Q3 review campaigns against Q4 reputation scores. It retrieves the embedded campaign parameters and generates a report backed by hard numbers.

Setup guide

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

Use `llama-index-tools-mcp` to load the tools. Create a FunctionAgent that calls the tools to fetch data, then write the outputs to your Document store for embedding.

Yes. Your agent can call `get_location` to fetch specific branch details before answering user queries about regional performance.

The tools fetch data on demand. You need to set up a cron job or scheduled LlamaIndex workflow to periodically call the list tools and update your vector store.

LlamaIndex handles the conversion automatically. The MCP tool returns JSON, which the framework parses into text nodes before generating embeddings.

When your agent calls `get_review`, it retrieves real customer names and complaint details. You control the chunking and embedding process locally, ensuring PII stays within your own vector store and never leaks to public models.

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