Search / io.github.xcollantes/jira-mcp
jira-mcp
L0· runs locallyFeature-rich MCP for controlling Jira through LLM clients. Safe for corporate environments.
v0.2.2 · active · repository · descriptor JSON · versions
Search / io.github.xcollantes/jira-mcp
L0· runs locallyFeature-rich MCP for controlling Jira through LLM clients. Safe for corporate environments.
v0.2.2 · active · repository · descriptor JSON · versions
{
"mcpServers": {
"jira-mcp": {
"command": "uvx",
"args": [
"jira-tools-mcp==0.2.2"
],
"env": {
"JIRA_API_TOKEN": "${JIRA_API_TOKEN}",
"JIRA_AUTH_TYPE": "${JIRA_AUTH_TYPE}"
}
}
}
}claude mcp add jira-mcp -e "JIRA_API_TOKEN=${JIRA_API_TOKEN}" -e "JIRA_AUTH_TYPE=${JIRA_AUTH_TYPE}" -- uvx jira-tools-mcp==0.2.2[mcp_servers.jira-mcp]
command = "uvx"
args = ["jira-tools-mcp==0.2.2"]
env = { "JIRA_API_TOKEN" = "${JIRA_API_TOKEN}", "JIRA_AUTH_TYPE" = "${JIRA_AUTH_TYPE}" }
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jira-mcp": {
"type": "local",
"command": [
"uvx",
"jira-tools-mcp==0.2.2"
],
"enabled": true,
"environment": {
"JIRA_API_TOKEN": "{env:JIRA_API_TOKEN}",
"JIRA_AUTH_TYPE": "{env:JIRA_AUTH_TYPE}"
}
}
}
}{
"mcpServers": {
"jira-mcp": {
"command": "uvx",
"args": [
"jira-tools-mcp==0.2.2"
],
"env": {
"JIRA_API_TOKEN": "${JIRA_API_TOKEN}",
"JIRA_AUTH_TYPE": "${JIRA_AUTH_TYPE}"
}
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=jira-mcp&config=eyJjb21tYW5kIjoidXZ4IiwiYXJncyI6WyJqaXJhLXRvb2xzLW1jcD09MC4yLjIiXSwiZW52Ijp7IkpJUkFfQVBJX1RPS0VOIjoiJHtKSVJBX0FQSV9UT0tFTn0iLCJKSVJBX0FVVEhfVFlQRSI6IiR7SklSQV9BVVRIX1RZUEV9In19"
}{
"servers": {
"jira-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"jira-tools-mcp==0.2.2"
],
"env": {
"JIRA_API_TOKEN": "${JIRA_API_TOKEN}",
"JIRA_AUTH_TYPE": "${JIRA_AUTH_TYPE}"
}
}
}
}{
"mcpServers": {
"jira-mcp": {
"command": "uvx",
"args": [
"jira-tools-mcp==0.2.2"
],
"env": {
"JIRA_API_TOKEN": "${JIRA_API_TOKEN}",
"JIRA_AUTH_TYPE": "${JIRA_AUTH_TYPE}"
}
}
}
}extensions:
"jira-mcp":
enabled: true
name: "jira-mcp"
type: stdio
cmd: "uvx"
args:
- "jira-tools-mcp==0.2.2"
envs:
"JIRA_API_TOKEN": "${JIRA_API_TOKEN}"
"JIRA_AUTH_TYPE": "${JIRA_AUTH_TYPE}"
timeout: 300
Placeholders to fill from your own secret store: ${JIRA_API_TOKEN}. The registry never accepts secret values.
This is a local package: the command runs on your machine.
Not scored: fewer than three checks apply, usually because no remote answered a credential-free probe or the server is a local package.
protocol.modern, protocol.stateless, protocol.transport, protocol.list_ttlno remote answered a protocol handshake (not probed yet, unreachable, or local-only)auth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptions, tools.description_length, tools.schemas, tools.annotations, tools.directory_hints, tools.token_cost, tools.api_dumptool list unknown (behind auth, not probed, or empty)stability.changes, stability.rug_pulltool list unknowndeps.known_vulnsno known advisory in 37 resolved packagesdeps.mcp_sdk_versionmcp 2.2.0, no known advisorydeps.resolvable[email protected] resolved: 37 packagesNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+repository +namespace-matches-repo ~liveness-unmeasured -stale-267d
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
[email protected] PyPI36 dependencies, resolved · MCP SDK mcp 2.2.0 · advisories checked 2026-10-19
No known advisory affects this dependency graph.
Dependency graphs from deps.dev; advisories from OSV.dev, including the GitHub Advisory Database and the PyPI Advisory Database; all CC BY 4.0. The graph is what a clean install of this version resolves today; nothing was installed or run. How it is checked.
| package | registry | version | runtime | secrets |
|---|---|---|---|---|
jira-tools-mcp | pypi | 0.2.2 | – | JIRA_API_TOKEN |
No tools observed. Local packages are never executed by the registry.
Schemas: list_tools.
{
"name": "io.github.xcollantes/jira-mcp",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"version": "0.2.2",
"packages": [
{
"version": "0.2.2",
"transport": {
"type": "stdio"
},
"identifier": "jira-tools-mcp",
"registryType": "pypi",
"environmentVariables": [
{
"name": "JIRA_API_TOKEN",
"format": "string",
"isSecret": true,
"isRequired": true,
"description": "Your Jira API key for the service"
},
{
"name": "JIRA_AUTH_TYPE",
"format": "string",
"isRequired": true,
"description": "Your Jira authentication type"
}
]
}
],
"repository": {
"url": "https://github.com/xcollantes/jira-mcp",
"source": "github"
},
"description": "Feature-rich MCP for controlling Jira through LLM clients. Safe for corporate environments."
}