McLeod Software MCP for AI. Track every order and dispatch in McLeod.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Connect to your AI in seconds.
McLeod Software MCP Server gives your AI agent direct access to McLeod LoadMaster and PowerBroker data. Manage every aspect of transportation logistics, from listing all open orders to tracking real-time dispatch movements.
Use it to pull detailed shipment metadata, inspect master records for carriers or customers, and orchestrate complex dispatches entirely through natural conversation.
It's the full command center for your fleet operations.
What your AI can do
Get dispatch details
Pulls the full details for one specific dispatch assignment.
Get order
Fetches all available metadata for a single, specified order ID.
List carriers
Provides a list of all master carrier records in the system.
You ask for a dispatch ID, and the agent pulls all current details—who's driving it, where it is, what the plan is.
The agent fetches complete details on any specific order number or searches across multiple orders using keywords.
You get a list of all recorded truckload movements, plus the exact sequence of stops for any given trip.
The agent lists or inspects master records for customers, carriers, and drivers so you never have to manually look up an ID.
You can get a list of all current dispatch assignments across your fleet, letting you see what's moving right now.
Ask an AI about this
Waiting for input…
McLeod Software MCP Server: 10 Tools for Logistics Data
Use these ten specialized tools to analyze order details, dispatch assignments, carrier records, and movement logs from your McLeod system.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using McLeod Software on VinkiusGet Dispatch Details
Pulls the full details for one specific dispatch assignment.
Get Order
Fetches all available metadata for a single, specified order ID.
List Carriers
Provides a list of all master carrier records in the system.
List Customers
Retrieves a complete list of master customer accounts.
List Dispatches
Lists every active and past dispatch assignment ID available in the system.
List Drivers
Retrieves a directory of all registered company drivers.
List Movements
Lists every recorded truckload movement, allowing you to see the scope of transport activity over time.
List Orders
Gets a comprehensive list of all transportation orders currently logged in McLeod.
List Stops
Provides the specific sequence and details for stops along any recorded movement...
Search Orders
Searches across all transportation orders using keywords or partial terms to narrow...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The McLeod Software integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with McLeod Software, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by McLeod Software. 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.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 10 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Manually tracking freight status is a nightmare of tabs and IDs.
Think about it: You get a call about an order. Your first instinct is to open McLeod, navigate to the Orders tab, then find the specific ID, check if there's a related dispatch assignment, click into that, and finally check the movements log to see the last stop recorded. It’s 5-7 clicks just to answer 'Where is it?'
With this MCP server, you just ask your agent: 'What's the status of order ORD-1234?' The system runs `get_order` and returns the full answer—status, carrier, next stop—in a single text block. It cuts out every click.
The McLeod Software MCP Server: Get the facts you need immediately.
Before this server, if your team needed to audit historical routes, someone had to run a complicated report in McLeod and then email it out. The data was static, required manual filtering, and could be outdated before anyone read it.
Now, you simply ask the agent to 'List all movements for last month.' You get the raw, structured data instantly via `list_movements`. It's real-time audit capability without the report generation headache.
What your AI can actually do with this
You connect your AI agent directly to McLeod LoadMaster or PowerBroker data. This server gives you the full command center for fleet operations, letting your agent manage everything from listing open jobs to tracking real-time movement using nothing but natural conversation.
For job orders, you can run list_orders and get a complete rundown of every transportation order logged in McLeod. If you know what specific job you're working on, use search_orders to narrow down results fast by throwing in keywords or partial terms across the whole backlog. Once your agent finds the right ID, it uses get_order to pull all the detailed metadata for that single shipment.
When you need to track a dispatch, first list every active and past assignment using list_dispatches. Then, by feeding in a specific dispatch ID, get_dispatch_details pulls the whole picture: it tells you who's driving it, where it is right now, and what the overall plan is for that run. To follow the physical movement of your fleet, start with list_movements, which spits out every recorded truckload movement over time.
If you need to know exactly where that truck stopped along the way, list_stops gives you the specific sequence and details for all stops on a given trip’s path.
Don't waste time looking up IDs manually; your agent handles core business entities for you. You can use list_customers to pull a full roster of master customer accounts or run list_carriers to see every registered carrier record in the system. If you need to know which company driver is handling the load, list_drivers gives you a directory of every assigned company employee.
019d75d0-dbd1-70a1-b5b4-f8eea3b4ba73 
Here's how it actually works
The bottom line is that you talk to your AI client, and it talks directly to McLeod Software for real-time operational data.
Subscribe to the server and provide your required credentials (McLeod Base URL, Client ID, Client Secret, Company ID).
Your AI client connects using these stored keys, establishing a direct link to your McLeod software instance.
You ask your agent a question like, 'What's the status of dispatch 555?' and the server runs the appropriate tool to return live data.
Who is this actually for?
This server is for the Operations Manager who needs a single source of truth. It's for the Dispatcher who can't afford delays waiting on manual lookups, and the Logistics Analyst who has to cross-reference customer IDs against movement logs daily. You need this if your job requires knowing 'where stuff is' or 'who owns it' without opening eight different tabs.
Uses the agent constantly to check get_dispatch_details and list_movements. They need real-time status updates for assignments and drivers.
Spends time running audits using list_orders, search_orders, and list_stops to verify billing records against physical routes.
Uses the agent to audit master data by listing customers (list_customers) or carriers (list_carriers), ensuring all operational records are current before a major dispatch begins.
What Changes When You Connect
Instant status checks: Instead of navigating through menus to find a single job's status, you just ask for it. Use get_dispatch_details to instantly confirm if an assignment is 'In Transit,' who the driver is, and what the next step is.
Master data lookup: Stop wasting time looking up customer or carrier IDs. Running list_customers or list_carriers pulls clean, accurate master records directly into your chat window for immediate use.
Full audit trail access: Need to prove where a shipment went? Use list_movements and then drill down with list_stops. You get the complete sequence of stops without manual report generation.
Targeted order retrieval: If you only care about orders in one area or related to one client, don't list everything. Run search_orders first—it cuts through noise so you can pinpoint exactly what you need with get_order.
Dispatch visibility: You can see the whole picture by calling list_dispatches, giving you an immediate overview of every active job that needs attention today.
See it in action
Figuring out a delayed shipment's exact location
The Ops Manager gets a call about a late load. Instead of asking the dispatcher to pull up the tablet, they ask their agent. The agent runs get_dispatch_details and then uses list_stops on that dispatch ID. Problem solved: They see exactly which stop caused the delay.
Auditing all shipments for a specific client
The Billing Analyst needs to verify if TechCorp was charged correctly for last week's run. The agent uses list_customers first, then runs search_orders using 'TechCorp.' Finally, they pull the full record with get_order to match invoice details.
Getting an overview of today’s fleet activity
The Dispatcher starts their shift by asking for all active jobs. The agent runs list_dispatches. If they notice a cluster of dispatches in one region, they can then run list_movements to check the status of those specific routes.
Cross-checking carrier credentials before onboarding
A new partner needs setting up. Instead of searching multiple tabs, the agent runs list_carriers. This confirms if the company is already listed and provides the necessary master record details for immediate use.
The honest tradeoffs
Asking for 'all orders' without filtering
The user just says, 'Show me all logistics data.' The agent runs list_orders, returning thousands of records that are useless noise.
Always narrow the scope. If you need a specific order, use get_order(ID). If you need to find it, run search_orders(keyword) first.
Assuming one tool covers everything
The user asks for 'the status of the movement and the customer details.' The agent can't pull both with a single call.
Use two steps. First, check the transport activity with list_movements. Then, cross-reference the involved party using list_customers.
Not specifying the type of data needed
The user says, 'Tell me about the drivers.' The agent might return a general list instead of current location status.
Be specific. If you need current status, ask for get_dispatch_details using the assignment ID.
When It Fits, When It Doesn't
Use this server if your workflow requires querying specific operational facts about shipments: 'Where is it?' or 'Who owns it?'. This setup excels at discrete data retrieval—pulling a record, listing entities, or tracking movement steps. Use get_order when you have the ID and need details; use search_orders when you only have keywords.
Don't use this server if your goal is financial reporting (use accounting software) or general HR functions. It’s a logistics data layer, not an ERP replacement. If you just need to know 'what kind of truck we own,' check the vehicle maintenance system instead; list_drivers only handles people.
Questions you might have
How do I check a specific order status using get_order? +
You provide the Order ID to the agent, and it runs get_order. The output gives you all available metadata—status, associated dispatch IDs, and required next steps.
Can I find a shipment if I don't know the order ID? Use search_orders. +
Yes. If you just know 'Chicago' or 'TechCorp,' run search_orders with those terms. It returns a list of matching Order IDs, which you can then use to get details.
How do I see all active jobs on the fleet? +
Run list_dispatches. This tool pulls every dispatch assignment ID currently in the system. You'll need to take one of those IDs and pass it to get_dispatch_details for specifics.
What is list_movements used for? +
list_movements gives you a log of every truckload movement that has ever happened. It’s your full historical record, essential for billing and compliance checks.
Before I run `list_carriers`, what credentials do I need to authenticate my AI client? +
You must provide your McLeod Base URL, Client ID, Client Secret, and Company ID. These four pieces of information are required for the server to access your specific organization's data.
If `get_dispatch_details` fails because the ID is wrong, what error message should I expect? +
You will receive a standard 'Not Found' status code (404). Your AI client handles this by notifying you that the specific dispatch ID doesn't exist. You can then try listing dispatches instead.
When I use `list_orders`, what parameters should I pass to filter for a date range? +
You usually specify start and end dates in the request payload. This is crucial because it filters massive result sets down quickly, letting you focus on activity from just last week or this month.
To get stop details using `list_stops`, what key identifier must I pass to the tool? +
It requires a Movement ID. You can't query stops without knowing the movement first. Run list_movements to grab that necessary movement identifier before running this function.
How do I get my McLeod API credentials? +
You typically need to contact your internal McLeod admin or partner@mcleodsoftware.com to enable the API and receive your OAuth 2.0 Client ID and Secret.
What is the Company ID? +
The Company ID is a unique string used in the X-com.mcleodsoftware.CompanyID header to identify your specific TMS database/company.
Is my transportation data secure? +
Absolutely. Your credentials are encrypted at rest and injected securely at runtime.
We've already built the connector for McLeod Software. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 10 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.