opencode-jira-mcp
Provides tools for interacting with Jira Cloud, enabling issue tracking, project management, and agile features such as searching, creating, updating, transitioning issues, managing sprints, comments, attachments, and user assignments.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@opencode-jira-mcpFind all high-priority bugs in the PROJ project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
opencode-jira-mcp
MCP (Model Context Protocol) server that connects opencode with Jira Cloud, exposing issue tracking, project management, and agile features as structured tools for AI agents.
Requirements
Node.js >= 18
A Jira Cloud account with an API token
An MCP client (such as opencode, Claude Desktop, or any MCP-compatible host)
Related MCP server: Personal JIRA MCP
Installation
1. Authenticate with GitHub Packages
Create or edit your ~/.npmrc file and add:
//npm.pkg.github.com/:_authToken=YOUR_GITHUB_TOKEN
@DevelopmentAgentSDD:registry=https://npm.pkg.github.comGet a GitHub token at Settings → Developer settings → Personal access tokens → Tokens (classic) with the
read:packagesscope.
2. Global install (recommended)
npm install -g @DevelopmentAgentSDD/opencode-jira-mcp3. Using npx (no install)
npx @DevelopmentAgentSDD/opencode-jira-mcpFrom source
git clone https://github.com/DevelopmentAgentSDD/MCP-JiraCloud.git
cd MCP-JiraCloud
npm ci
npm run buildConfiguration
The server requires three environment variables:
Variable | Description |
| Your Jira Cloud domain (e.g., |
| Email address of your Atlassian account |
| API token generated at https://id.atlassian.com/manage-profile/security/api-tokens |
Configuring in opencode.json
Add the server to your opencode.json or MCP client configuration:
{
"mcpServers": {
"jira": {
"command": "npx",
"args": ["-y", "@DevelopmentAgentSDD/opencode-jira-mcp"],
"env": {
"JIRA_HOST": "my-company.atlassian.net",
"JIRA_EMAIL": "me@my-company.com",
"JIRA_API_TOKEN": "your-api-token-here"
}
}
}
}Available Tools
The server exposes 9 tools to the MCP host:
1. search_issues
Search for issues in Jira using structured parameters or raw JQL.
"Find all high-priority bugs in the PROJ project assigned to me"
"Search for issues containing 'login' in the summary or description"Parameters: projectKey, issueType, status, assignee, priority, labels, sprint, text, jql, startAt, maxResults, orderBy, fields
2. create_issue
Create a new Jira issue of any type (Task, Bug, Story, Epic, Subtask).
"Create a bug in PROJ: 'Login page crashes on mobile' with priority High"
"Create an Epic called 'Q2 Platform Migration' in the PROJ project"Parameters: projectKey, summary, issueType, description, priority, assignee, labels, parentKey (Subtask), epicName (Epic)
3. update_issue
Modify fields on an existing Jira issue.
"Update PROJ-123: change priority to Critical, add label 'security'"
"Set the assignee of PROJ-456 to unassigned"Parameters: issueKey, summary, description, priority, labels, assignee, components, customFields
4. transition_issue
Move an issue through its workflow or list available transitions.
"Move PROJ-123 to In Progress"
"What transitions are available for PROJ-456?"
"Close PROJ-789 with resolution 'Done'"Parameters: issueKey, transitionName, transitionId, resolution, comment, listTransitions
5. get_sprints
Retrieve sprints from a Jira board with optional issue details.
"Show me active sprints on the PROJ Scrum Board"
"List all sprints on board ID 42, including their issues"Parameters: boardId, boardName, state (active|future|closed), includeIssues, startAt, maxResults
6. assign_user
Assign or unassign a user to/from an issue.
"Assign PROJ-123 to John Doe"
"Unassign PROJ-456"Parameters: issueKey, accountId (set to null or "unassigned" to unassign)
7. manage_comments
List or add comments on a Jira issue.
"Show all comments on PROJ-123"
"Add a comment to PROJ-123: 'Fixed in PR #42, ready for review'"Parameters: action (list|add), issueKey, body (for add), startAt, maxResults
8. attach_file
Attach a file from the local filesystem to a Jira issue.
"Attach the file error-screenshot.png to PROJ-123"Parameters: issueKey, filePath (must exist, be readable, and <10 MB)
9. jira_health_check
Verify connectivity to Jira Cloud and validate authentication credentials.
"Check if the Jira connection is working"Parameters: none
Security
Token safety: the
JIRA_API_TOKENis never written to stdout, stderr, or error messages. All log entries and error responses redact the token.Headers sanitization:
Authorizationheaders are replaced withBasic [REDACTED]in all logs.Config sanitization: when logging the configuration, the token is displayed as
***SET***.Token rotation: generate new tokens at https://id.atlassian.com/manage-profile/security/api-tokens. The server picks up the new token on restart.
Troubleshooting
"JIRA_HOST is required"
Set the JIRA_HOST environment variable to your Jira Cloud domain without https://:
export JIRA_HOST=my-company.atlassian.net"JIRA_API_TOKEN is required"
Generate an API token at https://id.atlassian.com/manage-profile/security/api-tokens and set it:
export JIRA_API_TOKEN=your-generated-token"Authentication failed"
Verify your email matches the Atlassian account email
Ensure the API token is active (not revoked)
Check that
JIRA_HOSTis correct and does not includehttps://
"Access denied"
Your account does not have permission for the requested action. Verify your project permissions in Jira.
"Rate limit exceeded"
The server automatically retries with exponential backoff (up to 3 retries, max ~210s total). If you consistently hit rate limits, reduce request frequency or check your Jira Cloud plan limits.
Development
# Install dependencies
npm ci
# Run in development mode (with auto-reload)
npm run dev
# Type check
npm run typecheck
# Lint
npm run lint
# Format
npm run format
# Run tests
npm test
# Run tests with coverage
npm run test:coverage
# Build for production
npm run buildProject structure
src/
index.ts # Entry point (shebang, main function)
config/ # Zod-based env var validation
auth/ # Basic Auth header builder
services/ # JiraClient (HTTP client with retry)
tools/ # 9 MCP tool handlers + centralized registration
transport/ # Stdio transport setup
types/ # TypeScript interfaces
utils/ # Errors, retry logic, sanitization
tests/
unit/ # Unit tests (vitest)
integration/ # Integration tests (nock for HTTP mocking)
fixtures/ # Mock Jira responsesTech stack
Category | Technology |
Language | TypeScript 5.5+ (strict mode) |
Runtime | Node.js >= 18 |
MCP SDK | @modelcontextprotocol/sdk ^1.0 |
Validation | Zod ^3.24 |
Logging | Pino ^9.0 |
Testing | Vitest + nock |
Linting | ESLint + Prettier |
License
MIT — see LICENSE for details.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/DevelopmentAgentSDD/MCP-JiraCloud'
If you have feedback or need assistance with the MCP directory API, please join our Discord server