JIRA using MCP connection is not showing the results

Support Help
1

Hi Team,

I can see the MCP connection is successful. But When I try to connect and collect data from JIRA using MCP tool , I couldnot get successful result. At the same time, JIRA data can be retrieved via JIRA REST API connection. So JIRA via MCP Connection is affected or need some attention. Could any of you help in this.

Note:

  1. My whole team is using the same connection without any issues except me.

  2. After some time, I got the message SSL certificate validation blocks the connection. When the whole team is accessible with same set of certificates maintained by company, Why do I have the error? Can anyone help in this

image
image1392×735 162 KB

6

From your screenshot, I can see you’re running a local MCP server (mcp-atlassian.exe) connecting to your self-hosted Jira at jira.trimble.tools. The SSL certificate error you’re seeing is likely the primary cause – your self-hosted Jira uses your company’s internal CA certificate, and the MCP server process doesn’t trust it by default.

To fix the SSL issue, add your company’s CA certificate to the MCP server’s environment. In your mcp.json, add an env block to pass the CA cert path:

"mcp-jira-local": {
"command": "C:/JIRA-MCP/mcp-atlassian.exe",
"args": [
"--jira-url", "``https://jira.trimble.tools``",
"--jira-username", "``[email protected]``",
"--jira-personal-token", "<your-token>"
],
"env": {
"NODE_EXTRA_CA_CERTS": "C:/path/to/trimble-ca-certificate.pem"
}
}

Ask your IT team or a teammate who has this working for the path to Trimble’s internal CA certificate (.pem or .crt file). If you’re unsure, ask one of your teammates to share their mcp.json configuration – they may already have this env block set up.

Additionally, verify your personal access token:

  1. Log into jira.trimble.tools in your browser

  2. Go to your Profile > Personal Access Tokens

  3. Confirm the token you’re using in mcp.json hasn’t expired

  4. If expired, generate a new one and update your config

After making changes, toggle the MCP server off and back on in Cursor Settings > MCP.

If the SSL issue persists and you need a quick workaround while sorting out the certificate, you can also check with your teammates how they have their MCP connection configured – since they’re using the same setup successfully, comparing configs should highlight the difference.

7

Thanks Mohitjain. Adding the ENV values resolved this issue.