fleetsync-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLEETSYNC_API_KEY | Yes | Your FleetSync API key | |
| FLEETSYNC_BASE_URL | No | The base URL of the FleetSync API (default: https://api.fleetsync.io/v2) | https://api.fleetsync.io/v2 |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fleetsync_get_orderA | Get a FleetSync order by its number. Returns order details including status, client, address, delivery date, driver, and proof of delivery info. |
| fleetsync_orders_by_dateA | Get all FleetSync orders for a specific date. Returns list of orders scheduled for that day with their statuses. |
| fleetsync_orders_by_routeA | Get all FleetSync orders assigned to a specific route by its code. |
| fleetsync_orders_status_changesA | Get FleetSync orders that had status changes after a specific date/time. Useful for checking recently delivered/updated orders. Date format: YYYY-MM-DDTHH:mm:ss. Minimum: UTC - 1 day. |
| fleetsync_order_historyA | Get the history of a FleetSync order (last 25 entries). Useful for tracking changes and re-deliveries. |
| fleetsync_create_orderA | Create a new unscheduled order in FleetSync. Requires: Number (max 50 chars), Client, Address, Date (YYYY-MM-DD). Optional: Phone, Email, Note. |
| fleetsync_update_orderA | Update an existing FleetSync order. Requires: Number. Optional fields to update: Client, Address, Phone, Email, Date, Note. |
| fleetsync_delete_orderA | Delete a FleetSync order by its number. This action is irreversible. |
| fleetsync_orders_by_route_dateA | Get all FleetSync orders for a specific date grouped by their assigned routes. |
| fleetsync_get_routesA | Get all FleetSync routes. Returns a list of all route summaries. |
| fleetsync_routes_by_dateA | Get all FleetSync routes for a specific date. Returns route details including driver, status, and order count. |
| fleetsync_get_routeA | Get a specific FleetSync route by its code. Returns route details, driver assignment, orders, and status. |
| fleetsync_create_routeA | Create a new route in FleetSync. Requires Code and Date. Optional: DriverName, DriverVehicle, Depot, Orders. Query options: update, updateAddressGps, mergeAddresses. |
| fleetsync_update_routeB | Update an existing FleetSync route. Requires Code. Optional: Date, DriverName, DriverVehicle, Depot, Orders. Query options: update, updateAddressGps, mergeAddresses. |
| fleetsync_delete_routeA | Delete a FleetSync route by its code. This action is irreversible. |
| fleetsync_analyze_route_distancesA | Analyze distances between consecutive orders in a route. Flags order pairs exceeding the distance threshold. Useful for diagnosing poorly optimized routes. |
| fleetsync_get_driversA | Get all FleetSync drivers. Returns list of drivers with their names, vehicles, phones, and active status. |
| fleetsync_testA | Test FleetSync API authentication and check rate limits. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/RobsonAdvincula/fleetsync-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server