Jira MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| jira_list_projectsC | Lists all Jira projects the user has access to |
| jira_get_issueC | Retrieves details of a specific Jira issue by key |
| jira_search_issuesC | Searches for Jira issues by project and assignee |
| jira_list_project_membersC | Lists all members of a specific Jira project |
| jira_check_user_issuesC | Checks if a user is a member of a project and lists their assigned issues |
| jira_create_issueC | Creates a new issue in a Jira project with specified details |
| jira_list_sprintsC | Lists current sprints in Jira with filtering options |
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 7 tools
Every tool has a clearly distinct purpose targeting specific Jira resources and actions, such as checking user issues, creating issues, getting issue details, listing project members, listing projects, listing sprints, and searching issues. There is no overlap or ambiguity between these functions.
All tool names follow a consistent 'jira_verb_noun' pattern with snake_case, such as jira_create_issue and jira_list_projects. This predictable naming scheme makes it easy for agents to understand and select the right tool.
With 7 tools, this server is well-scoped for Jira operations, covering core functionalities like issue management, project access, and sprint tracking. Each tool earns its place without being overwhelming or insufficient for the domain.
The toolset provides good coverage for basic Jira workflows, including issue CRUD (create, get, search), project and member listing, and sprint management. A minor gap exists in missing update and delete operations for issues, which agents might need to work around.