2,500+ MCP servers ready to use
Vinkius

Dashdoc MCP Server for Claude Desktop 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Dashdoc and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "dashdoc": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Dashdoc
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 Dashdoc MCP Server

Integrate Dashdoc, the leading transport management system (TMS), directly into your AI workflow. Manage your transport orders, monitor your fleet of trucks and trailers, and track delivery addresses using natural language.

Claude Desktop is the definitive way to connect Dashdoc to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 10 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

What you can do

  • Transport Management — List and retrieve detailed information for all your transport orders and their statuses.
  • Fleet Monitoring — Track your trucks, trailers, and drivers registered in the Dashdoc system.
  • Address Book — Manage delivery and pickup addresses and create new records instantly.
  • Partner Insights — List contacts and business partners associated with your transport operations.

The Dashdoc MCP Server exposes 10 tools through the Vinkius. Connect it to Claude Desktop 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 Dashdoc to Claude Desktop via MCP

Follow these steps to integrate the Dashdoc MCP Server with Claude Desktop.

01

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

02

Add the MCP Server

Paste the configuration above into the mcpServers section

03

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

04

Start using Dashdoc

Look for the 🔌 icon in the chat. your 10 tools are now available

Why Use Claude Desktop with the Dashdoc MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Dashdoc through the Model Context Protocol.

01

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

02

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

03

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

04

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

Dashdoc + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Dashdoc MCP Server delivers measurable value.

01

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

02

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

03

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

04

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Dashdoc MCP Tools for Claude Desktop (10)

These 10 tools become available when you connect Dashdoc to Claude Desktop via MCP:

01

create_new_address

Persists site metadata including name, city, and postal code, returning the newly generated system ID for the address. Add a new address to your Dashdoc address book

02

get_my_user_info

Returns account-level metadata including user ID, role, and associated fleet/company configuration. Retrieve metadata for the current authenticated user

03

get_transport_details

Resolves internal IDs to human-readable names, including full site addresses, contact phone numbers, specific cargo items, and historical status logs. Get detailed information for a specific transport order

04

list_fleet_drivers

Returns driver profiles including internal identifiers, professional names, and link to associated vehicle units. List all drivers registered in the system

05

list_fleet_trailers

Returns metadata such as trailer type (e.g., refrigerated, tautliner), registration numbers, and fleet assignment status. List all trailers in your fleet

06

list_fleet_trucks

Includes license plates, vehicle types, maximum load capacity, and current operational status. List all trucks in your fleet

07

list_saved_addresses

Returns a collection of site objects with GPS coordinates, technical contact details, and site-specific instructions (e.g., gate codes, loading bay requirements). List all saved delivery and pickup addresses

08

list_transport_contacts

Resolves business partner identities, including legal names, tax identifiers, and primary communication channels for logistics coordination. List contacts and business partners

09

list_transports

Returns transport metadata including status (e.g., requested, confirmed, ongoing, done), pickup/delivery references, customer IDs, and scheduling timestamps. List all transport orders in Dashdoc

10

search_transports_by_reference

Matches the provided reference keyword against transport-level identifiers and customer references using case-insensitive partial matching. Search for transport orders by reference keyword

Example Prompts for Dashdoc in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Dashdoc immediately.

01

"List all transport orders that are 'Ongoing'."

02

"Show me the details for transport order 'TR123'."

03

"List all trucks in our fleet."

Troubleshooting Dashdoc MCP Server with Claude Desktop

Common issues when connecting Dashdoc to Claude Desktop through the Vinkius, and how to resolve them.

01

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
02

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
03

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Dashdoc + Claude Desktop FAQ

Common questions about integrating Dashdoc MCP Server with Claude Desktop.

01

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
02

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
03

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
04

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
05

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.

Connect Dashdoc to Claude Desktop

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