Jama Connect claims to be the first engineering requirements management platform to ship a Model Context Protocol server, allowing developers to invoke their AI assistant of choice against Jama's Traceability Information Model without leaving their IDE. Supported clients at launch include Claude, OpenAI Codex, Cursor, GitHub Copilot, and Visual Studio, with the server enforcing Jama Connect's existing permission model, lifecycle workflows, and audit trail requirements — so AI-assisted queries cannot bypass access controls already configured in the platform. For engineering teams in regulated industries — aerospace, automotive, medical devices — where requirements traceability is both a design and compliance concern, this integration reduces the friction of cross-referencing specs during active development. The MCP pattern here is notable: rather than exporting requirements to a separate context, the server keeps the authoritative source of truth in Jama and serves it to the model on demand, which limits hallucination risk on requirement IDs and linkage. Teams evaluating AI tooling in regulated domains should assess whether the permission-enforcement guarantees meet their compliance needs before wide rollout.