Bring Job Dispatching
to LlamaIndex
Learn how to connect Giddyup to LlamaIndex and start using 13 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Giddyup MCP Server?
Connect your Giddyup account to any AI agent and take full control of your roofing and construction workflows through natural conversation.
What you can do
- Lead Orchestration — List and manage potential customer records programmatically, including contact info and acquisition metadata
- Job Lifecycle — Monitor active roofing and construction projects and retrieve detailed technical metadata and status in real-time
- Customer Intelligence — Access your complete customer directory and retrieve detailed profiles to streamline field coordination
- Operational Visibility — Get a comprehensive overview of your construction pipeline using natural language commands
- Field Coordination — Access granular details for specific jobs to ensure your team has the latest project requirements
How it works
1. Subscribe to this server
2. Retrieve your API Authentication Key from your Giddyup settings (Custom Application Integration)
3. Start managing your construction CRM from Claude, Cursor, or any MCP client
No more manual toggling between project spreadsheets. Your AI acts as your dedicated construction operations coordinator.
Who is this for?
- Project Managers — instantly check job statuses and retrieve customer requirements using natural language
- Sales Teams — manage lead queues and update contact details without leaving your workspace
- Operations Leaders — monitor the entire construction pipeline and identify bottlenecks through automated queries
Built-in capabilities (13)
Verify connectivity
Create a job
Create a lead
Get customer details
Get job details
Get lead details
List customers
List invoices
List jobs
List leads
List technicians
Update a job
Update a lead
Why LlamaIndex?
LlamaIndex agents combine Giddyup tool responses with indexed documents for comprehensive, grounded answers. Connect 13 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.
- —
Data-first architecture: LlamaIndex agents combine Giddyup tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain Giddyup tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query Giddyup, a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what Giddyup tools were called, what data was returned, and how it influenced the final answer
Giddyup in LlamaIndex
Giddyup and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Giddyup to LlamaIndex through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Giddyup in LlamaIndex
The Giddyup MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 13 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in LlamaIndex only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Giddyup for LlamaIndex
Every tool call from LlamaIndex to the Giddyup MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Giddyup API Key?
Log in to your Giddyup account and navigate to the Custom Application Integration settings to generate your unique authentication key.
Can I list specific roofing jobs by ID?
Yes! Use the get_job tool and provide the unique job identifier to retrieve detailed technical data and status updates.
Does this integration support customer profile retrieval?
Absolutely. The list_customers tool allows you to retrieve your entire client directory for better field coordination.
How does LlamaIndex connect to MCP servers?
Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
Can I combine MCP tools with vector stores?
Yes. LlamaIndex agents can query Giddyup tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
Does LlamaIndex support async MCP calls?
Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.
BasicMCPClient not found
Install: pip install llama-index-tools-mcp