Jama Connect Ships an MCP Server: Spec-Driven Development Comes to Regulated Engineering

In brief: Jama Software announced on 2026-05-04 that Jama Connect 9.35 is the first engineering management platform to ship a Model Context Protocol (MCP) server. Engineers in regulated industries can now query, trace, and reason over specifications from Claude, Cursor, GitHub Copilot, Codex, or Visual Studio without dropping their permissions, lifecycle workflows, or audit requirements at the door.

What Changed

Jama Connect 9.35 added a built-in MCP server that exposes the platform’s specifications, items, and traceability graph to any MCP-compatible client. Anthropic, OpenAI, Microsoft, and the Cursor team have all standardized on MCP as the wire protocol for tool calls, so a single server endpoint serves every major coding assistant on the market today.

The pitch from Jim Davidson, Jama’s CTO, is that this is “the only product enabling Spec Driven Development via MCP for multidisciplinary engineering teams.” That phrasing matters. Most MCP servers shipping in May 2026 are point integrations: a database adapter, a ticketing connector, a vector store. Jama is exposing an entire requirements-and-traceability model, including the semantic relationships between disciplines, specifications, and versions that regulated industries use to prove conformance.

According to the announcement, the server is engineered to scale to 10 million items and 100 million instances of those items. That ceiling is aimed at aerospace, defense, automotive, medtech, semiconductor, and energy programs where a single product line generates millions of linked artifacts.

The release does not change Jama’s permission model. Existing roles, workflows, and audit policies pass through to AI sessions, so a contractor whose Jama account cannot read certain export-controlled specs cannot read them through Claude either.

Why It Matters

Three audiences win here, and we think the second one is the largest.

First, regulated engineering teams finally get an answer to the question “can our engineers use AI assistants without breaking compliance?” The MCP server is the bridge. AI sessions inherit Jama’s existing controls, and traceability gets recorded by the same system that auditors already trust. For teams operating under DO-178C, ISO 26262, IEC 62304, or similar frameworks, that is the difference between a conditional yes and a hard no.

Second, operations and program leads at non-regulated mid-market companies get a template. Most automation-focused teams we talk to are still trying to figure out how AI assistants should touch source-of-truth systems like CRMs, ticket trackers, and product catalogs. Jama’s pattern, which is to put an MCP server in front of the system that owns the data and let it enforce the rules, is the cleaner approach than scraping or syncing. Expect Salesforce, ServiceNow, and Atlassian to ship versions of this within the year.

Third, MCP itself gains a high-stakes reference customer. The protocol hit 1.0 stable in April with the MCP Apps extension formalized as SEP-1865. A regulated-industry vendor publicly committing to MCP at this scale is the kind of validation that pulls cautious enterprise buyers off the fence.

How to Use It

Jama Connect 9.35 is available today for existing customers, and the MCP server is part of the release rather than a separate SKU. Pricing was not disclosed in the announcement.

To connect Claude Desktop, Cursor, or any other MCP-aware client, you point it at your Jama Connect tenant’s MCP endpoint. The exact configuration syntax varies by client, but every major MCP client uses a JSON config file with the same general shape:

// Illustrative: based on standard MCP client config patterns from Anthropic and Cursor docs (verified 2026-05-05). Confirm exact endpoint and auth fields against Jama Connect 9.35 release notes when you set this up.
{
  "mcpServers": {
    "jama-connect": {
      "url": "https://your-tenant.jamacloud.com/mcp",
      "auth": {
        "type": "bearer",
        "token": "<JAMA_API_TOKEN>"
      }
    }
  }
}

We have not yet run this exact configuration ourselves against a Jama tenant. The snippet above is the standard MCP client pattern, not a tested Jama-specific example. Confirm the endpoint path and auth method against Jama’s 9.35 release notes before deploying. If you are evaluating, the practical first step is to spin up a sandbox tenant, point Cursor at it, and ask the agent to explain a single high-level requirement back to you. If the trace returns, the auth is working and the permission model is being enforced.

Operations teams considering this for non-engineering use cases should note that Jama Connect is priced for regulated engineering programs, not workflow tooling. The pattern is reusable; the product license is not.

Best MCP Servers 2026. Our running roundup of MCP servers worth deploying, refreshed monthly.
What Is MCP (Model Context Protocol)?. Primer on the protocol Jama is building on.
MCP 1.0 Stable and the MCP Apps Spec. Context on why MCP became safe to commit to in April.
Building Your First MCP Server with Pipedream. Practical walkthrough if you want to ship your own server before vendors ship theirs.

This post is part of Pondero’s daily coverage of AI tool updates. See all MCP guides →