How to Use the Giddyup MCP in LlamaIndex

Q: How does LlamaIndex prevent hallucinations with Giddyup data?

The agent pulls fresh data using getlead or getcustomer and injects it directly into the context window. This ensures every response is grounded in your actual field service database.

Index your Giddyup dispatch data directly into LlamaIndex vector stores to build search engines for your field operations.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Giddyup MCP to LlamaIndex

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Build a searchable Giddyup knowledge base

Turn your active construction schedules and work histories into a searchable index using this MCP Server. Your LlamaIndex agent uses `list_jobs` and `list_customers` to pull raw operational data and write it directly into your vector database. This lets you run semantic queries across past work orders instead of relying on rigid database filters. Your team can ask about past HVAC repairs or specific plumbing issues and get answers grounded in actual historical records.

Feed live dispatch data to your RAG pipelines

Stop letting your agents hallucinate schedule details or customer histories. The agent calls `get_job` and `get_customer` to retrieve real-time ground truth before answering any operational questions. This live data is combined with your internal manuals or policy documents inside the index. The result is an agent that knows both your company policies and the exact status of today's field technicians.

Track tech availability and lead status using this MCP Server

Keep your sales pipeline and technician schedules fully indexed. The agent calls `list_leads` and `list_users` to monitor which prospects are active and which technicians are currently deployed in the field. By indexing these updates, your system can identify capacity bottlenecks before they delay projects. You can query the index to see which regions have high lead volume but low technician coverage.

Setup guide

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

Install the LlamaIndex MCP tool package and pass your endpoint to the basic client. Convert the client to a tool list and hand it to your function agent to start querying dispatch data.

Yes, you can use the allowed tools filter during setup to restrict access. This lets you expose read-only tools like `list_jobs` while hiding write operations like `update_job`.

The agent pulls fresh data using `get_lead` or `get_customer` and injects it directly into the context window. This ensures every response is grounded in your actual field service database.

Yes, LlamaIndex excels at merging disparate data sources. You can index local PDF manuals alongside active job data retrieved from the server to give technicians complete context.

Your technician schedules and lead details are transmitted over encrypted connections directly to your local LlamaIndex instance. This hosted MCP Server ensures no operational data is cached or stored by the hosting infrastructure.

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