How to Use the Bringg MCP in Cursor

Q: How do I configure the Bringg server in Cursor?

Add the Vinkius endpoint credentials to your .cursor/mcp.json file. Once configured, Cursor's agent mode can immediately access all your delivery and driver tools via the MCP protocol.

Q: What tool should I use to verify if a driver is en route?

You should ask the editor to run gettasktimeline or listactivetasks. This returns the real-time status of the delivery so you can see if the route has started.

Code and test custom Bringg delivery workflows with live dispatch data inside Cursor.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Bringg MCP to Cursor

Create your Vinkius account to connect Bringg to Cursor 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 Bringg with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Build Bringg apps using real fleet data in Cursor

The `list_fleet_drivers` tool brings real driver data directly into your Cursor workspace so you do not have to write code against mock JSON objects. This lets Cursor write actual, working code that processes real-time logistics. You can test your dispatch logic instantly by letting Cursor invoke `list_active_tasks` to see how your code handles active orders.

Debug delivery timelines directly in the editor

Use `get_task_timeline` inside Cursor to inspect the live state of a broken task next to your code. You do not need to switch back to your terminal or open a browser. Use Cursor's agent mode to run `update_task_details` and verify if your payload changes fix the pipeline bug.

Automate driver assignment tests

Run the `assign_driver_to_task` tool to test your manual dispatch overrides directly from the editor. You can also test edge cases like canceling a dispatch using `cancel_task_dispatch` to make sure your code handles deletions correctly. This MCP Server makes building custom logistics software much faster.

Setup guide

Set up Bringg MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Bringg MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Bringg transactions." If the MCP tools are loaded correctly, Cursor will call the Bringg tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "bringg-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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 Bringg. 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 Bringg 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 Bringg MCP in Cursor

Add the Vinkius endpoint credentials to your `.cursor/mcp.json` file. Once configured, Cursor's agent mode can immediately access all your delivery and driver tools via the MCP protocol.

No. Your API keys are managed securely by Vinkius. Cursor only communicates with the secure V8 sandbox to execute MCP tools like `create_delivery_task` without exposing raw credentials.

Yes. You can ask the Cursor agent to write a script and run `update_task_details` sequentially on a list of active tasks to update delivery notes in bulk.

You should ask the editor to run `get_task_timeline` or `list_active_tasks`. This returns the real-time status of the delivery so you can see if the route has started.

Every request to modify your active dispatch schedule or driver details is executed in a zero-trust, ephemeral sandbox. No customer data or fleet logs are stored on disk after the tool finishes running.

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