In this webinar, Aaron Thomas (Director of Engineering, Dock and Yard at Opendock) walks through how Opendock's API first approach and new MCP (Model Context Protocol) server let you connect Opendock to your TMS, WMS, ERP, and other systems, and how AI agents like Claude can act on top of that data. 

What's covered: 

• Opendock's API first architecture (155+ orgs integrated, 3M+ API calls per week)
• What an MCP server is and why it matters for connecting AI systems to your existing tools
• Live demo: bulk-creating appointments from a spreadsheet using Claude and the Opendock MCP server
• Live demo: a custom dock agent dashboard for daily operations, including pulling forward appointments, bulk approvals, and driver ETAs

• A live user access and roles report for auditing and deactivating accounts 

  What's next: custom, self-service analytics and Power BI style reporting powered by MCP MCP doesn't change how Opendock works today. 

  Your existing UI, APIs, and integrations stay the same. It just adds new capabilities on top. 

  Agents run with your permissions. They can only see and do what you're already allowed to do.