← Index

io.github.deepwired/mcp-jira-scoped

io.github.deepwired/mcp-jira-scoped·v1.0.0·Productivity & Project Mgmt

Jira MCP server with scoped API tokens via api.atlassian.com gateway

Trust verdict · v1 advisory · method
NOT YET SCREENEDno verdict on file

Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.

Own this server? Screen its description →

Environment variables
JIRA_INSTANCE
required

Jira instance name (e.g. 'mycompany' for mycompany.atlassian.net)

JIRA_USER_EMAIL
required

Email associated with the API token

JIRA_API_TOKEN
requiredsecret

Scoped API token from https://id.atlassian.com/manage-profile/security/api-tokens

JIRA_SCOPES

Comma-separated scopes: read:jira-work, write:jira-work, read:jira-user, read:me. Defaults to read:jira-work

JIRA_CLOUD_ID

Atlassian Cloud ID (auto-fetched if not set). Find at https://yoursite.atlassian.net/_edge/tenant_info

MCP quality score · maturity, not trust · methodology
freshness
21
completeness
10
installability
25
documentation
15
stability
10
Alternatives in Productivity & Project Mgmt