Skip to main content
Glama
redhat-community-ai-tools

Jira MCP Server

by redhat-community-ai-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
METRICS_PORTNoPort for metrics HTTP server.8000
MCP_TRANSPORTNoTransport protocol for MCP communication.stdio
ENABLE_METRICSNoEnable Prometheus metrics collection.false
SNOWFLAKE_ROLENoSnowflake role to use (optional).
SNOWFLAKE_USERNoSnowflake username for private key or password authentication.
SNOWFLAKE_TOKENNoSnowflake authentication token (Bearer token) for API method or OAuth token for connector OAuth method.
SNOWFLAKE_SCHEMANoSnowflake schema name containing JIRA tables.
SNOWFLAKE_ACCOUNTNoSnowflake account identifier (e.g., your-account.snowflakecomputing.com) for connector method.
SNOWFLAKE_BASE_URLNoSnowflake API base URL (e.g., https://your-account.snowflakecomputing.com/api/v2) for REST API method.
SNOWFLAKE_DATABASENoSnowflake database name containing JIRA data.
SNOWFLAKE_PASSWORDNoSnowflake password for password authentication.
SNOWFLAKE_WAREHOUSENoSnowflake warehouse name for connector method.
SNOWFLAKE_AUTHENTICATORNoAuthentication method for connector: 'snowflake_jwt', 'snowflake', 'oauth_client_credentials', or 'oauth'.snowflake
SNOWFLAKE_OAUTH_CLIENT_IDNoOAuth client ID for client credentials flow.
SNOWFLAKE_OAUTH_TOKEN_URLNoOAuth token URL (optional) for client credentials flow.
SNOWFLAKE_PRIVATE_KEY_FILENoPath to private key file (PKCS#8 format) for JWT authentication.
SNOWFLAKE_CONNECTION_METHODNoConnection method: 'api' for REST API (default) or 'connector' for snowflake-connector-python.api
SNOWFLAKE_OAUTH_CLIENT_SECRETNoOAuth client secret for client credentials flow.
SNOWFLAKE_PRIVATE_KEY_FILE_PWDNoPrivate key password (optional) for encrypted key.

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
list_jira_issuesC
    Args:
        project: Filter by project key (e.g., 'SMQE', 'OSIM')
        issue_keys: List of JIRA issue keys (e.g., ['SMQE-1280', 'SMQE-1281'])
        issue_type: Filter by issue type ID
        status: Filter by issue status ID
        priority: Filter by priority ID
        limit: Maximum number of issues to return (default: 50)
        search_text: Search in summary and description fields
        timeframe: Filter issues where ANY date (created, updated, or resolved) is within last N days (default: 0 = disabled)
        components: Comma-separated list; match ANY in component name
        created_days: Filter by creation date within last N days (overrides timeframe if > 0, default: 0 = disabled)
        updated_days: Filter by update date within last N days (default: 0 = disabled)
        resolved_days: Filter by resolution date within last N days (default: 0 = disabled)
        fixed_version: Filter by fixed/target version name
        affected_version: Filter by affected version name

    Returns:
        Dictionary containing issues list and metadata
get_jira_issue_detailsB
    Get detailed information for multiple JIRA issues by their keys from Snowflake.

    Args:
        issue_keys: List of JIRA issue keys (e.g., ['SMQE-1280', 'SMQE-1281'])

    Returns:
        Dictionary containing detailed issue information including comments for all found issues
get_jira_project_summaryA
    Get a summary of all projects in the JIRA data from Snowflake.

    Returns:
        Dictionary containing project statistics
get_jira_issue_linksA
    Get issue links for a specific JIRA issue by its key from Snowflake.

    Args:
        issue_key: The JIRA issue key (e.g., 'SMQE-1280')

    Returns:
        Dictionary containing issue links information
get_jira_issues_by_sprintA
    Get all JIRA issues in a specific sprint by sprint name from Snowflake.

    Args:
        sprint_name: The name of the sprint (e.g., 'Sprint 256')
        limit: Maximum number of issues to return (default: 50)
        project: Filter by project key (e.g., 'SMQE', 'OSIM')

    Returns:
        Dictionary containing issues in the sprint and metadata

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

B3.4/5.0

Scored across 5 tools

Disambiguation3/5

Tools are mostly distinct but there is functional overlap between 'get_jira_issue_details' and 'list_jira_issues', both accepting issue keys and returning issue information (though with different detail levels). Additionally, 'get_jira_issues_by_sprint' could be considered a filtered variant of 'list_jira_issues', causing potential confusion for an agent.

Naming Consistency4/5

All tool names follow snake_case and use a verb-noun pattern. However, there is a mix of 'get_' and 'list_' prefixes (e.g., 'list_jira_issues' vs. 'get_jira_issue_details'), which is a minor inconsistency but not chaotic.

Tool Count5/5

With 5 tools, the server is well-scoped for a read-only Jira query interface. The tools cover essential retrieval needs (issue details, links, sprint issues, project summary, and filtered list) without being excessive or overly sparse.

Completeness4/5

The tool surface covers the main read operations for Jira issues from Snowflake, but is limited to querying. Missing operations like creating, updating, or transitioning issues are not expected given the read-only nature, so there are only minor gaps such as lacking a direct single-issue getter (though details and list can serve that role).

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources