Skip to main content
Glama
thisIsRasel

jira-mcp-server

by thisIsRasel

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JIRA_TOKENNoBearer token for authentication. If set, takes priority over username/password.
JIRA_BASE_URLNoThe base URL of your Jira instance, e.g. https://your-jira-instance.com
JIRA_PASSWORDNoPassword for basic authentication.
JIRA_USERNAMENoUsername for basic 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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
jira_searchB

Search Jira issues using JQL

jira_get_issueC

Retrieve Jira issue details

jira_create_issueC

Create a Jira task

jira_add_commentC

Add comment to issue

jira_assign_issueC

Assign issue to user

jira_transition_issueC

Move issue to another workflow state

jira_projectsC

Get Jira projects

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a distinct Jira operation: search, retrieve, create, comment, assign, transition, and list projects. There is no overlap or ambiguity between them.

Naming Consistency4/5

All tools share the 'jira_' prefix and use snake_case, with most following a verb_noun pattern (e.g., jira_get_issue). The exception is jira_projects, which is a simple noun rather than 'list_projects', but this is a minor deviation.

Tool Count5/5

With 7 tools, the server is well-scoped for common Jira operations. Each tool covers a core feature without unnecessary bloat or missing essentials.

Completeness3/5

The set covers create, read, search, comment, assign, and transition, but lacks an update operation (e.g., jira_update_issue), which is a core part of issue lifecycle management. This is a notable gap that agents may need to work around.

Maintenance

ActivitySlowing
ResponsivenessNo issues