Jira MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_BASE_URL | Yes | The base URL of your Jira instance | |
| JIRA_PERSONAL_ACCESS_TOKEN | Yes | Your Jira personal access token in the format email@example.com:your_personal_jira_access_token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsC | List projects from Jira |
| list_boardsC | List boards from a project |
| list_sprints_from_boardB | List sprints from a board |
| list_issues_from_sprintC | List issues from a sprint |
| create_issueB | Create an issue in Jira |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct action: create issue, list boards, list issues from sprint, list projects, list sprints from board. No overlap.
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_issue, list_boards). No deviations.
5 tools is well-scoped for a Jira MCP server, covering essential listing and creation operations without bloat.
The set covers creation and listing of key entities but lacks update, delete, and search operations, which are common in Jira workflows.