How to Use the Dashdoc MCP in Cursor

Q: How do I configure the Dashdoc MCP Server in Cursor?

Create an mcp.json file in your project root or global .cursor directory. Add the Vinkius endpoint URL and enable Agent mode in your chat panel.

Q: Can Cursor pull live Dashdoc transport statuses while I code?

The agent reads current transport states using the listtransports tool. It fetches requested, confirmed, ongoing, or done statuses along with scheduling timestamps.

Build logistics tools by pulling real Dashdoc transport data directly into Cursor.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Dashdoc MCP to Cursor

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Query logistics data inside Cursor

The `get_transport_details` tool feeds real cargo items, site addresses, and status logs straight into your editor context. Your agent reads human-readable names and historical status logs instead of generating fake JSON stubs. You'll write parsing logic against actual data structures. Searching happens via the `search_transports_by_reference` tool. Cursor matches reference keywords against transport-level identifiers using case-insensitive partial matching. You can test your API wrappers by asking the agent to pull a real shipment and write the corresponding TypeScript interface.

Sync fleet assets via MCP Server

The `list_fleet_trucks` and `list_fleet_trailers` tools return current operational statuses, license plates, and trailer types. Cursor injects this metadata into your workspace. When you build a dispatch dashboard, the AI writes the frontend components using exact key names from the live database. Personnel tracking uses the `list_fleet_drivers` tool. The agent pulls professional names and linked vehicle units. You get immediate access to real driver profiles while coding the assignment logic for your application.

Manage sites and business partners

The `list_saved_addresses` tool returns site objects with GPS coordinates and technical contact details. Your agent reads gate codes and loading bay requirements to help you map out delivery logic. Writing new data works through the `create_new_address` tool, which persists site metadata and returns the new system ID. Partner identities are resolved using the `list_transport_contacts` tool. Cursor fetches legal names and tax identifiers for logistics coordination. You can also pull account-level metadata like user roles and company configurations via the `get_my_user_info` endpoint.

Setup guide

Set up Dashdoc 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 Dashdoc 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 Dashdoc transactions." If the MCP tools are loaded correctly, Cursor will call the Dashdoc tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "dashdoc-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 Dashdoc. 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 Dashdoc 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 Dashdoc MCP in Cursor

Create an `mcp.json` file in your project root or global `.cursor` directory. Add the Vinkius endpoint URL and enable Agent mode in your chat panel.

The agent reads current transport states using the `list_transports` tool. It fetches requested, confirmed, ongoing, or done statuses along with scheduling timestamps.

Mention the reference keyword in your prompt. The agent uses the search tool to execute a partial match and injects the resulting transport identifiers into your editor.

You can add new locations. The address creation tool writes the city, name, and postal code to the database and returns the generated ID.

The server accesses tax identifiers, driver profiles, GPS coordinates, and cargo details. Vinkius routes these requests through an ephemeral V8 isolate sandbox. Nothing persists after the connection closes.

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