Prerequisites
Before configuring Jama Connect MCP, make sure that the following are in place and available.
Jama Connect access
Active Jama Connect tenant administrator access for configuration
Active Jama Connect Interchange platform and Jama Connect MCP connector
Defined project permissions for users whose credentials will be used
Enabled REST API access
A Named Creator license and assigned REST API credentials for anyone using Jama Connect MCP
MCP-compatible desktop environment
You must provide:
Node.js version 22.13.1 or later
To install Node.js, see https://nodejs.org/en/download
npm version 10.9.2 or later
npm is installed automatically with Node.js. If, for some reason, it isn't, you must install it manually.
To install npm, see https://docs.npmjs.com/downloading-and-installing-node-js-and-npm
An MCP-compatible client (such as IDE integration or a custom tool) that is able to delegate authentication to mcp-remote: https://www.npmjs.com/package/mcp-remote
Your own LLM provider (if applicable)
Important
Jama Connect doesn’t configure or manage your client-side LLM.
Your own model configuration
OAuth REST API credentials
OAuth REST API credentials must be generated for the user account that authenticates Jama Connect MCP calls. For more information, see Set REST API credentials.
The credentials determine:
Project access
Item-level permissions
Ability to create and edit entities
Ability to create relationships and baselines
All actions performed through Jama Connect MCP are executed under the identity of the credential owner.
Important
Jama Connect MCP doesn’t make REST API calls and doesn’t consume REST API bandwidth. Jama Connect MCP inherits only REST API authentication mechanisms.