Jama Connect Cloud Model Context Protocol (MCP) server
The Model Context Protocol (MCP) server for Jama Connect Cloud allows you to connect approved MCP-compatible clients, such as Integrated Development Environment (IDE) or Command-Line Interface (CLI) tools, to Jama Connect to securely retrieve information and execute supported actions through controlled tool calls.
The process of setting up the MCP server includes reviewing the prerequisites and completing the configuration steps. It is also helpful to review supported operations, validated workflows, and known limitations.
Important considerations
Jama Software does not host or manage the Large Language Model (LLM) used by your MCP client. You are responsible for providing and securing the LLM according to your organization’s requirements.
Jama Software does not use MCP interactions to train external AI models.
MCP tools access only the data that is scoped to your Jama Connect tenant.
Authentication and authorization are enforced through your credentials and permissions.
Best practices
Limit token permissions to the minimum required scope.
Avoid high-frequency polling via
search_jama_entities.Validate entity IDs before performing destructive operations.
Test workflows in a non-production project before scaling.
Before launching the IDE or Client that uses MCP (such as Cursor, CodeX, or Claude Desktop), first log in to Jama Connect in your default browser. This avoids some IDEs or Clients from blocking the login action.