Jira MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_URL | Yes | Your Jira instance URL (e.g., https://yourcompany.atlassian.net) | |
| JIRA_EMAIL | Yes | Your email address for Jira authentication | |
| JIRA_API_TOKEN | Yes | Your Jira API token for authentication |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_jira_issueC | Get detailed information about a Jira issue by its key (e.g., PROJ-123) |
| list_jira_projectsB | List accessible Jira projects with pagination and optional query. |
| get_jira_projectB | Get full metadata for a Jira project by key or ID. |
| get_project_statusesC | Get available statuses for each issue type in a project. |
| search_jira_issuesC | Search issues using JQL with pagination and field selection. |
| list_project_issuesB | List issues for a project with optional JQL tail filters. |
| get_jira_issue_commentsB | Retrieve comments for a Jira issue with pagination. |
| list_boardsB | List Jira boards with optional type and project filter. |
| list_board_sprintsB | List sprints for a given board with optional state filter. |
| list_sprint_issuesC | List issues in a given sprint with pagination. |
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 10 tools
Every tool has a clearly distinct purpose targeting specific Jira resources and actions. There is no overlap between tools like get_jira_issue (single issue details), list_project_issues (project-specific listing), and search_jira_issues (general JQL search), making misselection unlikely.
All tools follow a consistent verb_noun pattern with snake_case throughout. The naming convention is predictable with verbs like 'get', 'list', and 'search' clearly indicating the action type, and nouns specifying the target resource (e.g., jira_issue, project, boards).
With 10 tools, this server is well-scoped for Jira operations, covering core workflows like issue retrieval, project management, and board/sprint handling. Each tool earns its place without feeling excessive or insufficient for the domain.
The toolset provides strong read/search capabilities but has notable gaps in write operations. There are no tools for creating, updating, or deleting issues, comments, or other resources, which limits agents to read-only workflows and may cause failures in scenarios requiring modifications.