Provides tools for administering Jira Cloud and Jira Service Management Cloud, including issue management, project CRUD, workflow configuration, custom fields, service desks, request types, SLA metrics, and more.
Provides tools for Jira Cloud and Jira Service Management Cloud administration, enabling issue search and CRUD, project management, workflow operations, custom fields, service desk and queue management, request types, SLA monitoring, and group/user management.
Click on "Deploy 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., "@dtJiraMCPServer list all open tasks assigned to me"
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.
MCP Server for Jira Cloud and JSM Cloud administration via natural language.
dtJiraMCPServer provides a Model Context Protocol (MCP) server that bridges LLM clients (such as Claude Desktop or Claude Code) with Atlassian Jira Cloud and Jira Service Management (JSM) Cloud REST APIs. The server exposes 61 tools across 12 categories, enabling an LLM to perform administrative and operational tasks across both platforms.
Related MCP server: Jira MCP Server
61 tools across 12 feature areas
Read-only mode - restrict to non-mutating tools via JIRA_READ_ONLY
Self-documenting - LLMs can discover tools and read usage guides at runtime
Robust error handling - structured errors with retry, rate limiting, and backoff
Input validation - validates parameters before making API calls
Pagination - consistent pagination across all list operations
Stateless - no local state or caching; designed for containerised deployment
Category | Tools | Description |
Meta | 2 | Tool discovery and usage guides |
Issues | 7 | JQL search, issue CRUD, transitions |
Service Desk | 10 | Desks, queues, customers, organisations |
Request Types | 6 | Request type CRUD, fields, groups |
Fields | 10 | Custom fields, contexts, screens, screen schemes |
Workflows | 8 | Workflows, statuses, transitions |
Knowledge Base | 1 | Article search |
SLA | 2 | SLA metrics and detail |
Assets | 1 | Workspace queries |
Projects | 5 | Project CRUD operations |
Lookup | 3 | Issue types, priorities, user search |
Groups | 6 | Group CRUD, membership management |
See docs/tool-reference.md for the complete tool listing.
docker build -t dtjiramcpserver:latest .
docker run -i --rm \
--read-only \
-v dtjiramcp_data:/_working \
--security-opt=no-new-privileges \
--cap-drop=ALL \
-e JIRA_INSTANCE_URL=https://your-domain.atlassian.net \
-e JIRA_USER_EMAIL=user@example.com \
-e JIRA_API_TOKEN=your-api-token \
dtjiramcpserver:latestgit clone <repo-url>
cd dtJiraMCPServer
python -m venv .venv
.venv\Scripts\activate # Windows
# source .venv/bin/activate # Linux/macOS
pip install -e ".[dev]"
export JIRA_INSTANCE_URL=https://your-domain.atlassian.net
export JIRA_USER_EMAIL=user@example.com
export JIRA_API_TOKEN=your-api-token
python -m dtjiramcpserverSee docs/installation.md for detailed setup instructions.
Variable | Purpose | Required | Default |
| Atlassian Cloud instance URL | Yes | - |
| Atlassian account email | Yes | - |
| Atlassian API token | Yes | - |
| Restrict to read-only tools (true/1/yes) | No |
|
| Application log level | No |
|
{
"mcpServers": {
"jira": {
"command": "docker",
"args": [
"run", "-i", "--rm",
"--read-only",
"-v", "dtjiramcp_data:/_working",
"--security-opt=no-new-privileges",
"--cap-drop=ALL",
"-e", "JIRA_INSTANCE_URL=https://your-domain.atlassian.net",
"-e", "JIRA_USER_EMAIL=user@example.com",
"-e", "JIRA_API_TOKEN=your-api-token",
"dtjiramcpserver:latest"
]
}
}
}{
"mcpServers": {
"jira": {
"command": "python",
"args": ["-m", "dtjiramcpserver"],
"env": {
"JIRA_INSTANCE_URL": "https://your-domain.atlassian.net",
"JIRA_USER_EMAIL": "user@example.com",
"JIRA_API_TOKEN": "your-api-token"
}
}
}
}# Unit tests
pytest tests/unit/ -v --cov=dtjiramcpserver
# Integration tests (require Jira credentials)
export JIRA_INSTANCE_URL=https://your-domain.atlassian.net
export JIRA_USER_EMAIL=user@example.com
export JIRA_API_TOKEN=your-api-token
pytest tests/integration/ -vSee tests/README.md for test suite documentation.
Installation Guide - Setup and configuration
User Guide - How the LLM interacts with tools
Tool Reference - Complete tool listing and parameters
Transport: stdio (MCP SDK native)
Client layer: httpx-based async HTTP with rate limiting and retry
Tool framework: Auto-discovery registry with structured error handling
Application: dtPyAppFramework one-shot pattern
Python 3.10+
Atlassian Cloud instance with API token access
Docker (for containerised deployment)
MIT
This server cannot be deployed
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
