Jama Connect MCP Server
FeaturedOfficialby Jama Software
Jama Software shipped the first engineering-management Model Context Protocol server on May 4, 2026, alongside Jama Connect 9.35. If you build aircraft, medical devices or vehicles, this matters more than any chatbot launch this week. The problem the server solves is brutal and old. Engineers in regulated industries write requirements, validations and traceability inside Jama Connect. AI assistants live somewhere else — in Claude Code, Cursor or Codex CLI — and have no idea what the live spec actually says. Every prompt either gets stale exported PDFs or no context at all. The agent ends up generating code that violates a requirement no one remembered to paste in. The MCP server fixes that. It exposes Jama Connect's requirements graph as live tools and resources to any MCP-compatible client. Claude can pull the current acceptance criteria for a function it is implementing. Cursor can check which downstream tests would break if a requirement changes. Codex can verify that a generated module actually traces back to a parent requirement before the agent claims the task is done. This is what Jama is calling Spec-Driven Development. The agent does not guess what the spec is. It reads the spec on every turn, the same way a junior engineer would crack open the requirements doc. The difference is the agent does it in 200 milliseconds and never gets tired. Distribution is enterprise-controlled — the server ships with Jama Connect 9.35 and is intended for installation alongside an existing Jama deployment. That is the right choice for the customer base (aerospace, medical, automotive, defense), where running an unsanctioned MCP server against the requirements database would be a non-starter for compliance. The strategic read: Jama is the first engineering-management vendor to ship an MCP server, and that head start matters. Polarion, IBM DOORS and Codebeamer all have credible MCP roadmaps, but none of them are live yet. If you are evaluating ALM tools right now and your engineering organization is going AI-native, Jama just moved itself to the top of the shortlist. Related on Skila: for governance of the agents that consume Jama Connect requirements, see Microsoft Agent 365. For multi-agent coding workflows that pair well with spec-driven development, see jcode. For the broader enterprise AI shift driving MCP adoption, read Anthropic's consulting JV breakdown.
Installation
Key Features
- ✓Live access to Jama Connect requirements, validations and traceability via MCP tools
- ✓First engineering-management MCP server in market — shipped with Jama Connect 9.35
- ✓Built for regulated industries: aerospace, medical devices, automotive, defense
- ✓Compatible with Claude Code, Cursor, Codex CLI and any MCP-aware agent
- ✓Read live acceptance criteria, downstream test impact and parent-child traceability
- ✓Enterprise-grade distribution alongside existing Jama Connect deployments
- ✓Replaces stale PDF exports with on-demand requirement queries
Use Cases
- →An aerospace team has Claude generate a new flight-control module that traces correctly to the parent safety requirement
- →A medical device firm uses Cursor to refactor a verification suite without losing FDA-relevant traceability
- →An automotive ADAS team queries downstream test impact before approving a requirement change
- →A regulatory engineer validates that an AI-written module actually implements the requirement it claims to satisfy
- →Codex CLI agents verify spec coverage before marking a sprint task complete