2,500+ MCP servers ready to use
Vinkius

Bringg MCP Server for LlamaIndex 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools Framework

LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add Bringg as an MCP tool provider through Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    agent = FunctionAgent(
        tools=tools,
        llm=OpenAI(model="gpt-4o"),
        system_prompt=(
            "You are an assistant with access to Bringg. "
            "You have 10 tools available."
        ),
    )

    response = await agent.run(
        "What tools are available in Bringg?"
    )
    print(response)

asyncio.run(main())
Bringg
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About Bringg MCP Server

Connect your Bringg account to any AI agent and take full control of your final-mile delivery and dispatch operations through natural conversation.

LlamaIndex agents combine Bringg tool responses with indexed documents for comprehensive, grounded answers. Connect 10 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.

What you can do

  • Delivery Tasks — Create, update, list, and cancel delivery tasks dynamically before the truck leaves your hub
  • Fleet Dispatch — Manually assign specific drivers to tasks, bypassing default optimization algorithms
  • Live Timelines — Pull real-time geolocated tracking data and status estimates for any active order
  • Force Progression — Manually trigger task start or completion states to keep the dispatch board accurate
  • Driver CRM — List all human drivers across the fleet, track their availability, and analyze active limits
  • Customer Database — Instantly retrieve historical data for past delivery recipients

The Bringg MCP Server exposes 10 tools through the Vinkius. Connect it to LlamaIndex in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Bringg to LlamaIndex via MCP

Follow these steps to integrate the Bringg MCP Server with LlamaIndex.

01

Install dependencies

Run pip install llama-index-tools-mcp llama-index-llms-openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.py and run: python agent.py

04

Explore tools

The agent discovers 10 tools from Bringg

Why Use LlamaIndex with the Bringg MCP Server

LlamaIndex provides unique advantages when paired with Bringg through the Model Context Protocol.

01

Data-first architecture: LlamaIndex agents combine Bringg tool responses with indexed documents for comprehensive, grounded answers

02

Query pipeline framework lets you chain Bringg tool calls with transformations, filters, and re-rankers in a typed pipeline

03

Multi-source reasoning: agents can query Bringg, a vector store, and a SQL database in a single turn and synthesize results

04

Observability integrations show exactly what Bringg tools were called, what data was returned, and how it influenced the final answer

Bringg + LlamaIndex Use Cases

Practical scenarios where LlamaIndex combined with the Bringg MCP Server delivers measurable value.

01

Hybrid search: combine Bringg real-time data with embedded document indexes for answers that are both current and comprehensive

02

Data enrichment: query Bringg to augment indexed data with live information before generating user-facing responses

03

Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying Bringg for fresh data

04

Analytical workflows: chain Bringg queries with LlamaIndex's data connectors to build multi-source analytical reports

Bringg MCP Tools for LlamaIndex (10)

These 10 tools become available when you connect Bringg to LlamaIndex via MCP:

01

assign_driver_to_task

Manually override optimization and assign a specific driver to a task

02

cancel_task_dispatch

Cancel and permanently remove a delivery task from the dispatch schedule

03

create_delivery_task

Create a new delivery task (order) in the Bringg Delivery Hub

04

force_task_complete

Force a delivery task status to COMPLETE (successfully delivered)

05

force_task_start

Force a delivery task status to START (driver en route)

06

get_task_timeline

Retrieve comprehensive details and live timeline for a specific task

07

list_active_tasks

` mapping the SaaS dashboard directly isolating pending deliveries. Retrieve a paginated list of active delivery tasks/orders

08

list_customer_crm

List historical delivery recipients (customers) registered in Bringg

09

list_fleet_drivers

List all human drivers (users) within the Bringg fleet network

10

update_task_details

Modify existing delivery task details such as customer notes or dropoff info

Example Prompts for Bringg in LlamaIndex

Ready-to-use prompts you can give your LlamaIndex agent to start working with Bringg immediately.

01

"Show me the top 3 most recent active deliveries in the hub."

02

"Where is the order for Task ID 3109 and what's its exact timeline?"

03

"Force mark task 9481 as complete, the driver forgot to do it."

Troubleshooting Bringg MCP Server with LlamaIndex

Common issues when connecting Bringg to LlamaIndex through the Vinkius, and how to resolve them.

01

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

Bringg + LlamaIndex FAQ

Common questions about integrating Bringg MCP Server with LlamaIndex.

01

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.
02

Can I combine MCP tools with vector stores?

Yes. LlamaIndex agents can query Bringg tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
03

Does LlamaIndex support async MCP calls?

Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.

Connect Bringg to LlamaIndex

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.