Skip to main content
Glama
jondoesflow

Jira MCP Server

by jondoesflow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JIRA_EMAILYesYour Jira account email
JIRA_BASE_URLYesYour Jira Cloud instance URL (without trailing slash), e.g., https://yourcompany.atlassian.net
JIRA_API_TOKENYesYour Jira API 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_issuesA

Search for Jira issues using JQL or simple filters.

Args:
    jql: JQL (Jira Query Language) string for advanced searches
    project: Project key or name to filter by
    assignee: Assignee username, email, or 'currentUser()' for yourself
    status: Status name (e.g., 'To Do', 'In Progress', 'Done')
    issue_type: Issue type (e.g., 'Story', 'Bug', 'Task')
    priority: Priority level (e.g., 'High', 'Medium', 'Low')
    max_results: Maximum number of results to return (default: 20)
get_issueA

Get detailed information about a specific Jira issue.

Args:
    issue_key: The issue key (e.g., 'PROJ-123')
get_my_issuesB

Get issues assigned to the current user.

Args:
    status: Filter by status (e.g., 'To Do', 'In Progress', 'Done')
    max_results: Maximum number of results to return (default: 10)
create_issueB

Create a new Jira issue.

Args:
    project_key: The project key (e.g., 'PROJ')
    summary: Brief description of the issue
    issue_type: Type of issue ('Story', 'Bug', 'Task', etc.)
    description: Detailed description of the issue
    priority: Priority level ('Highest', 'High', 'Medium', 'Low', 'Lowest')
    assignee: Username or email of assignee (leave empty for unassigned)
update_issueB

Update an existing Jira issue.

Args:
    issue_key: The issue key (e.g., 'PROJ-123')
    status: New status (e.g., 'In Progress', 'Done')
    assignee: New assignee username/email, or 'unassigned' to remove assignee
    priority: New priority ('Highest', 'High', 'Medium', 'Low', 'Lowest')
    summary: New summary/title for the issue
add_commentB

Add a comment to a Jira issue.

Args:
    issue_key: The issue key (e.g., 'PROJ-123')
    comment: The comment text to add
list_projectsB

List all accessible Jira projects.

get_project_infoB

Get detailed information about a specific project.

Args:
    project_key: The project key (e.g., 'PROJ')

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 8 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap. For example, create_issue, get_issue, and update_issue handle different lifecycle stages, while get_my_issues and search_issues serve different query needs. The descriptions reinforce these distinctions, making tool selection unambiguous.

Naming Consistency5/5

All tools follow a consistent verb_noun naming pattern (e.g., add_comment, create_issue, get_issue). There are no deviations in style or convention, making the set predictable and easy to parse for an agent.

Tool Count5/5

With 8 tools, this server is well-scoped for Jira operations, covering core workflows like issue management and project queries. Each tool serves a clear purpose without bloat, aligning with typical server sizes of 3-15 tools.

Completeness4/5

The toolset provides strong coverage for Jira's core domain, including CRUD operations for issues and basic project management. A minor gap exists in missing tools for deleting issues or managing comments beyond addition, but agents can work around this with available tools.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources