Bring Field Operations
to LlamaIndex
Learn how to connect Grid to LlamaIndex and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Grid MCP Server?
Connect your WorkOnGrid account to any AI agent and take full control of your field operations and operational data management through natural conversation.
What you can do
- Worksheet Orchestration — List all operational worksheets and retrieve detailed technical metadata and structures programmatically
- Field Data Capture — Create, update, and search for records within your worksheets to track inspections, asset status, and team productivity
- Operational Visibility — Monitor analytical dashboards and manage team member access to maintain high-fidelity oversight of your workflows
- Asset Tracking — List and manage supported asset types to ensure precise inventory management and field record accuracy
- System Monitoring — Check API health and manage outbound webhooks directly through your agent for reliable operational automation
How it works
1. Subscribe to this server
2. Retrieve your Client ID and Secret from the Grid dashboard (Integrations / API Connectors)
3. Start managing your field data and operations from Claude, Cursor, or any MCP client
No more manual report entry or digging through complex data tables. Your AI acts as your dedicated field operations coordinator.
Who is this for?
- Operations Managers — instantly retrieve field reports and monitor project progress using natural language
- Field Supervisors — update worksheet records and track team activities without leaving your workspace
- Data Analysts — automate the extraction of operational data for custom reporting and BI integration
Built-in capabilities (12)
Verify Grid API connectivity
g., a new inspection report) into a specific worksheet. Add a new record to a worksheet
Get authenticated user info
Get details for a specific worksheet
List active webhooks
List available dashboards
List all operational worksheets
List common asset categories
List organization users
List records from a worksheet
Delete a record from a worksheet
Modify an existing operational record
Why LlamaIndex?
LlamaIndex agents combine Grid tool responses with indexed documents for comprehensive, grounded answers. Connect 12 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 Grid tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain Grid tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query Grid, a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what Grid tools were called, what data was returned, and how it influenced the final answer
Grid in LlamaIndex
Grid and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Grid 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 Grid in LlamaIndex
The Grid 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 12 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
Grid for LlamaIndex
Every tool call from LlamaIndex to the Grid 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 Client ID and Secret?
Log in to your Grid dashboard, navigate to the Integrations or API Connectors section to generate and copy your unique credentials.
Can I add a record to a specific worksheet via AI?
Yes! The create_new_operational_record tool allows you to push new data directly into any authorized worksheet in your Grid account.
How do I check available analytical dashboards?
Use the list_grid_dashboards tool to retrieve a list of all configured analytical views and monitors in your Grid environment.
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 Grid 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