MCP Jira Scoped runs on your own machine — the client starts it, so there is no endpoint to ping. 58 installs a week from npm. Last commit 20 Sep 2026.
Jira MCP server with scoped API tokens via api.atlassian.com gateway
Nothing serious here today
Today is the operative word: we check MCP Jira Scoped every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp-jira-scoped -e 'JIRA_INSTANCE=<JIRA_INSTANCE>' -e 'JIRA_USER_EMAIL=<JIRA_USER_EMAIL>' -e 'JIRA_API_TOKEN=<JIRA_API_TOKEN>' -- npx -y mcp-jira-scoped{
"mcpServers": {
"mcp-jira-scoped": {
"command": "npx",
"args": [
"-y",
"mcp-jira-scoped"
],
"env": {
"JIRA_API_TOKEN": "<JIRA_API_TOKEN>",
"JIRA_INSTANCE": "<JIRA_INSTANCE>",
"JIRA_USER_EMAIL": "<JIRA_USER_EMAIL>"
}
}
}
}[mcp_servers.mcp-jira-scoped]
command = "npx"
args = ["-y", "mcp-jira-scoped"]
env = { JIRA_INSTANCE = "<JIRA_INSTANCE>", JIRA_USER_EMAIL = "<JIRA_USER_EMAIL>", JIRA_API_TOKEN = "<JIRA_API_TOKEN>" }{
"mcpServers": {
"mcp-jira-scoped": {
"command": "npx",
"args": [
"-y",
"mcp-jira-scoped"
],
"env": {
"JIRA_API_TOKEN": "<JIRA_API_TOKEN>",
"JIRA_INSTANCE": "<JIRA_INSTANCE>",
"JIRA_USER_EMAIL": "<JIRA_USER_EMAIL>"
}
}
}
}{
"servers": {
"mcp-jira-scoped": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-jira-scoped"
],
"env": {
"JIRA_API_TOKEN": "<JIRA_API_TOKEN>",
"JIRA_INSTANCE": "<JIRA_INSTANCE>",
"JIRA_USER_EMAIL": "<JIRA_USER_EMAIL>"
}
}
}
}Put your own values in place of
<JIRA_INSTANCE> (Jira instance name (e.g. 'mycompany' for mycompany.atlassian.net)), <JIRA_USER_EMAIL> (Email associated with the API token), <JIRA_API_TOKEN> (Scoped API token from https://id.atlassian.com/manage-profile/security/api-tokens).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
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).
Alternatives to MCP Jira Scoped
same job, measured the same wayJira and Confluence behind SSO via your own browser session: every mcp-atlassian tool, no API token
MCP server for Atlassian Jira Data Center - search, view, and create issues
MCP server for Atlassian Jira Data Center - search, view, and create issues
Connect to Atlassian Jira, Confluence, Loom, and more to search, create, and manage your work.
MCP server for self-hosted Jira instance with Personal Access Token authentication
MCP server for downloading, uploading, and deleting Jira Cloud attachments by ID.
MCP server for P4 Plan — tasks, sprints, bugs, comments, custom fields via GraphQL API.
MCP server connecting Jira (Cloud + Server) with GitHub/GitLab. Branches, issues, PRs, flows.
MCP Jira Scoped — questions
Answers built from our own checks of this server.