Server data from the Official MCP Registry
Jira MCP server with scoped API tokens via api.atlassian.com gateway
Jira MCP server with scoped API tokens via api.atlassian.com gateway
Set these up before or after installing:
Environment variable: JIRA_INSTANCE
Environment variable: JIRA_USER_EMAIL
Environment variable: JIRA_API_TOKEN
Environment variable: JIRA_SCOPES
Environment variable: JIRA_CLOUD_ID
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-deepwired-mcp-jira-scoped": {
"env": {
"JIRA_SCOPES": "your-jira-scopes-here",
"JIRA_CLOUD_ID": "your-jira-cloud-id-here",
"JIRA_INSTANCE": "your-jira-instance-here",
"JIRA_API_TOKEN": "your-jira-api-token-here",
"JIRA_USER_EMAIL": "your-jira-user-email-here"
},
"args": [
"-y",
"mcp-jira-scoped"
],
"command": "npx"
}
}
}This is a well-structured Jira MCP server with proper authentication, good security practices, and appropriate permissions for its business tools purpose. Minor findings relate to broad exception handling and lack of explicit input sanitization, but the server demonstrates excellent security consciousness with token redaction, delete confirmation guards, and proper scope-based access control. Supply chain analysis found 4 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.
Scanned 7 files · 8 findings
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Be the first to review this server!