Your AI agent handles inbound load requests, routes them automatically, and gets the driver dispatched. Then someone has to manually call a warehouse to book the dock appointment. The automation stops at the one step that should be the easiest to fix.
This is not an edge case. It happens at companies that have already invested in building API integrations against Opendock. The API works. The integration is live. But the moment a new warehouse comes online or the workflow needs to run through an AI agent, the process breaks down and a person has to step in.
Two things shipping together address that problem directly: a new API discovery endpoint and the first MCP server built for dock appointment scheduling.
Opendock is API-first. Everything the platform does: schedule appointments, manage check-ins, update statuses, query availability,is accessible through the API. That has attracted real integrations from carriers and 3PLs with the technical resources to build them.
But building those integrations is harder than it should be, and the failure patterns are easy to spot in the data.
The core issue is discovery. Every warehouse on Opendock runs on its own scheduling rules. Required custom fields differ by facility. Available time slots, load type forms, and appointment windows are all configured per warehouse. To integrate with a new warehouse, a developer has to find all of that through documentation lookups, multiple API calls, and trial and error. There is no single call that returns everything needed to schedule at a specific facility.
That friction compounds as integrators try to expand. Companies that have built reliable integrations for a handful of facilities hit a wall when they try to scale. The discovery work multiplies with every warehouse they add.
The new API discovery endpoint collapses that process into a single call. It returns the scheduling rules, available time slots, required custom fields, load type forms, and facility-specific requirements for any warehouse on Opendock.
What previously required multiple calls and documentation review now happens in one request. For existing integrators, this makes expanding to new warehouses significantly easier. For teams that have been struggling to get their integration working at all, it removes the most common failure point.
This endpoint is also what powers the MCP server's ability to handle new warehouses automatically. You do not have to pre-map anything. The agent discovers what it needs when it needs it.
The MCP server is built for teams running AI agents. Any agent that supports MCP connections -- Claude, a custom-built agent, Happy Robot, GoAugment, Hubflow, Qued, CloneOps, or any other MCP-compatible platform -- can connect to Opendock and immediately schedule, modify, cancel, and query appointments.
The agent does not read API documentation. No developer writes integration code for each warehouse. The agent discovers what it can do through the MCP server and adapts automatically.
Here is what that looks like in practice. You tell your agent to schedule the earliest available appointment next week at a specific warehouse for a given PO. The agent calls the discovery endpoint to understand the warehouse's requirements, finds available time slots, fills in the required fields, creates the appointment, and confirms the booking. That all happens in a single interaction. No one read the docs. No one wrote warehouse-specific code.
The same logic applies to bulk operations. If you need to create dozens of appointments across multiple warehouses, you can paste your spreadsheet data into a Claude conversation connected to the MCP server. The agent creates all of the appointments at once. No API coding. No one-by-one portal entry.
Carriers and 3PLs with existing agents. If your team already uses AI agents for freight operations, dock scheduling is probably the one workflow they cannot complete on their own. If your agent supports MCP, that changes now. Connect to the Opendock MCP server and dock scheduling becomes part of the automated workflow.
Agentic workflow platforms. Companies like Happy Robot, GoAugment, Hubflow, and CloneOps are building platforms that automate freight operations end to end. Happy Robot, for example, currently receives carrier phone calls, uses AI to process them, and then has a human call the warehouse to schedule the appointment. With the MCP server, that last manual step is gone. The agent schedules directly in Opendock.
Teams struggling with traditional integration. The new discovery endpoint directly addresses the most common failure point for teams that have been trying to integrate with the API. And for teams that want to skip the custom build entirely, the MCP server is an alternative path that requires no integration code.
Heavy API users expanding to new warehouses. Companies already running healthy API integrations get the most immediate benefit from the discovery endpoint. Expanding to new warehouses no longer requires the same per-facility discovery work.
The carrier-side MCP server is what is launching now, alongside the new discovery endpoint. Carriers, 3PLs, brokers, and their agents can schedule, modify, and manage appointments across any Opendock warehouse.
Warehouse-side integrations are coming in a second release. Once a TMS or WMS supports MCP connectors (SAP already does), it will be able to connect to Opendock for bidirectional data sync. A second webinar in July will cover that use case in detail.
Aaron Thomas and Luiz Rosa walk through the capabilities in a 45 -minute session covering the new discovery endpoint and a live demo of carrier-side appointment scheduling through the MCP server. The session is built for technical audiences: engineering teams, IT leaders, and product managers at carriers, 3PLs, brokers, and agentic workflow platforms. [Watch the session here.]
For teams already building on the Opendock API or looking to connect their agent, the Opendock API Slack channel is the best place to get support and follow new MCP capabilities as they come online. Checking with Aaron if we should include the slack channel mention.
Most freight workflows have been automated for years. Dock scheduling has lagged because there was no infrastructure connecting AI agents to dock scheduling platforms. The MCP server is that infrastructure.
Carriers and 3PLs can start scheduling appointments across 4,000+ warehouses for free with Opendock. If you're building an agentic workflow and want to connect to the Opendock MCP server, reach out to get started.