A CERN developer presents how they built an MCP server to help coordinate scheduling at the Large Hadron Collider. The LHC scheduling problem involves thousands of tasks with complex physical, safety, and technical constraints, all managed in a massive MS Project file. The solution exposes the scheduling backend's APIs via an MCP server so coordinators can query conflicts in plain English using a local LLM. Key lessons: keep business logic in code rather than delegating it to the LLM, shape data to minimize context window usage, and return clear structured signals (e.g. a conflict list) rather than raw data dumps for the LLM to reason over.

13m watch time

Sort: