MCP shows up in job scheduling — agent plumbing is standardising faster than agent capability

Protocol adoption in developer tooling proves little; that community adopts and abandons standards quickly. Adoption in enterprise job scheduling, bought on multi-year cycles by buyers hostile to churn, is a different kind of evidence.

JAMS Software shipped its JAX agent and MCP connector to general availability for enterprise job scheduling. Job scheduling is deeply unglamorous and absolutely load-bearing — which is exactly why a GA connector there means something a developer-tool integration would not.

Why the buyer matters more than the feature

Enterprise scheduling software is procured on long cycles by organisations that treat change as risk. A protocol reaching GA in that segment has cleared a procurement bar, not a novelty bar. That is the difference between a standard being popular and a standard being depended upon.

Plumbing before capability is the right order

Agent capability is still moving fast enough that anything built tightly against a specific model will need rewriting. A stable interface with models swapped behind it survives that; a stable model behind shifting interfaces does not. The industry appears to have stumbled into the correct sequencing, which is not something it manages often.

The counter-pressure

Meta shipping its first paid developer API alongside Muse Spark 1.1 pulls the other way. Metered access creates an incentive to differentiate at the interface, because a perfectly standard interface makes you interchangeable. Every vendor benefits from the standard existing and from being slightly special within it.

Watch whether MCP stays thin. Protocols die of extension, not neglect.

Agentic.ai — Agentic AI News — July 2026 launches, models and research → · ThursdAI — July 2026 AI Releases →