Set up the MCP server
The process of setting up the MCP server includes reviewing the prerequisites and completing the configuration steps. It is also helpful to review Supported MCP capabilities, Validated example workflows, and Operational constraints and known limitations.
To configure the MCP server:
Confirm that MCP access has been enabled for your tenant by Jama Software. If unsure, contact your Customer Success Manager.
Generate the API token:
Log in to Jama Connect and create the MCP OAuth credentials.
Important
You must generate new credentials once MCP has been enabled. Pre-existing credentials don't work.
Make sure that your user is enabled in Admin > REST API > Managed Access Control.
Create OAuth Client ID and Secret: https://help.jamasoftware.com/ah/en/get-started/setting-up-your-work-environment/set-api-credentials.html
Store the credentials in a secure place.
To configure a generic MCP-compatible client, use the following example code, replacing the variables the way your MCP client defines or configures MCP servers.
This code snippet was tested against the Copilot plugin in IntelliJ.
{ "Jama Connect MCP": { "command": "npx", "args": [ "-y", "mcp-remote@latest", "/mcp/mcp-core", "--host", "127.0.0.1", "--static-oauth-client-info", "" ] } }Replace this...
With this...
tenant-urlYour Jama Connect subdomain.
<jama-oath-credentials-file>File location where you stored your credentials.
client-id
Your generated REST API client ID.
client-secret
Your generated REST API client secret.
Example
@/Users/username/.mcp.auth.json { "client_id": "", "client_secret":"" }See your MCP client documentation for additional configuration details.
Launch the MCP client:
Log in to the Jama Connect environment linked to your MCP server.
Launch the MCP server, following the instructions for your IDE. In many cases, a Start button appears near the server configuration in the mcp.json file.
The MCP server is now enabled and available for use.