Configuring Jama Connect MCP for LLM plugins (organization level)
You can configure Jama Connect MCP as a custom plugin for LLMs like ChatGPT.
Jama Connect MCP supports two authentication options, available in root admin:
OAuth service provided by Jama Connect
Customer-provided OAuth through your organization’s identity provider
If you use Jama Connect Cloud, contact Support for help configuring authentication.
OAuth service provided by Jama Connect
Use the OAuth service provided by Jama Connect to authenticate Jama Connect MCP applications. Once in root admin, the Authorization Code Client Properties page:
Lets you create new static registration clients that accept a Redirect URI from your LLM.
Generates a Client ID and Client Secret to use in your LLM when setting up MCP with Jama Connect.
For example setup instructions with ChatGPT, see <link>.
Customer-provided OAuth
Customer-provided OAuth lets you manage Jama Connect MCP sign-in through your identity provider. When you enable this option as root admin, Jama Connect no longer uses its internal OAuth flow for Jama Connect MCP authentication in LLM plugins. Instead, Jama Connect MCP trusts tokens issued by your identity provider.
Each token must:
Come from the configured issuer.
Be validated against the issuer’s published public signing keys.
Contain the expected audience.
Identify a user who matches a valid Jama Connect user.
This approach lets your organization manage sign-in through its identity platform while Jama Connect continues to enforce tenant boundaries.
For more information, see <link>.