Skip to main content
Glama
lfern

jira-gateway

by lfern
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JIRA_EMAILYesYour email address for Jira authentication.
JIRA_CLOUD_IDYesCloud ID of your Jira instance. Obtain via GET https://yourdomain.atlassian.net/_edge/tenant_info.
JIRA_SITE_URLYesURL of your Jira site, e.g., https://yourdomain.atlassian.net.
JIRA_API_TOKENYesAPI token with scope write:jira-work and read:jira-work.
JIRA_PROJECT_KEYYesKey of the Jira project (e.g., PROJ).
JIRA_SELECTED_STATUSNoName of the status for issues after creation (optional).Selected for Development
JIRA_GATEWAY_ENV_FILENoPath to the environment file (optional). Default is ~/.jira-gateway.env.
JIRA_DEFAULT_ISSUE_TYPENoDefault issue type name (optional).Task
JIRA_IN_PROGRESS_STATUSNoName of the 'In Progress' status in your workflow (optional).In Progress

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_my_tasksA

Lista tus tareas asignadas y no cerradas en el proyecto configurado. Solo lectura. No acepta JQL ni parámetros: el filtro está fijado.

create_taskA

Crea una tarea nueva en Jira en el proyecto configurado. Tras crearla la mueve automáticamente al estado JIRA_SELECTED_STATUS (por defecto 'Selected for Development'), así no se queda parada en Backlog.

IMPORTANTE: llama primero SIN confirm (o con confirm=False). Eso no crea nada, solo devuelve una vista previa de lo que se enviaría — muéstrasela al usuario tal cual. Solo si el usuario la aprueba, vuelve a llamar con confirm=True para crearla de verdad.

start_taskA

Transiciona el issue indicado en Jira. Sin status, lo pasa al estado de 'en progreso' configurado (JIRA_IN_PROGRESS_STATUS). Con status, transiciona a ese estado en su lugar (debe coincidir, sin distinguir mayúsculas, con el nombre exacto de una transición disponible en el workflow del issue, ej. 'Selected for Development') — útil para pasos previos a empezar a desarrollar. Solo funciona si el issue está asignado a ti; si no, devuelve error sin tocar nada. No toca git: la rama, el desarrollo, el commit y el push los gestiona Claude Code directamente con sus herramientas de siempre.

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

A4.4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: creating tasks, listing assigned tasks, and transitioning task status. No overlap exists.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: create_task, list_my_tasks, start_task.

Tool Count4/5

Three tools is a minimal but reasonable set for a Jira gateway focusing on task creation, listing, and status transitions.

Completeness3/5

Core create, read, and transition operations are covered, but missing update, delete, and advanced querying limit completeness for typical Jira workflows.

Resources