Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JIRA_HOSTYesJira Cloud: https://yourorg.atlassian.net / Server: https://jira.company.com
JIRA_EMAILNoAtlassian account email (Cloud only; leave empty for Server/DC)
JIRA_TOKENYesAPI token (Cloud) or Personal Access Token (Server/Data Center)
MCP_HTTP_HOSTNoHTTP server host (default: localhost)localhost
MCP_HTTP_PORTNoHTTP server port (default: 3002)3002
MCP_TRANSPORTNostdio (default) or httpstdio
MAX_TOKEN_CALLNoToken limit per tool response (default: 20000)20000
JIRA_VERIFY_SSLNotrue/false (default: true)true
JIRA_API_VERSIONNo3 for Cloud (default), 2 for Server/Data Center3

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
jira_health_checkA

Test the Jira connection. Returns authenticated account info (display name, email, account ID) and Jira server version/deployment type. Run first to verify credentials and connectivity.

search_issuesA

Search Jira issues using JQL (Jira Query Language). Returns key, summary, status, type, priority, assignee, reporter, created/updated dates and labels. Use for finding security incidents, open vulnerabilities, or tracking remediation tasks. Examples: project = SEC AND status != Done, assignee = currentUser() AND priority = High, labels = security-incident ORDER BY created DESC.

get_issueA

Get full details of a single Jira issue by key (e.g. SEC-123). Returns description, all comments, status, priority, assignee, reporter, labels, and timestamps. Use after search_issues to inspect a specific issue in depth.

create_issueA

Create a new Jira issue. Use to file security incidents, vulnerabilities, or remediation tasks. Returns the new issue key and URL. Common issue types: Task, Bug, Story, Incident, Security Incident (depends on project configuration).

update_issueA

Update fields of an existing Jira issue (summary, description, priority, labels). Use to enrich a security incident with investigation findings. To change status, use transition_issue instead.

add_commentA

Add a comment to a Jira issue. Use to record investigation steps, evidence, findings, or remediation actions directly on the ticket. Preserves the full audit trail of the security response.

list_transitionsA

List all available status transitions for a Jira issue. Returns transition IDs and target status names. Use before transition_issue to find the correct transition ID (e.g. "In Progress", "Resolved", "Closed").

transition_issueA

Move a Jira issue to a new status using a transition ID. Use list_transitions first to discover available transition IDs. Optionally attach a comment explaining the status change (e.g. "Closed: investigation complete, no compromise confirmed").

list_projectsA

List all accessible Jira projects with their keys, names, and types. Use to find the correct project key before creating issues or running JQL queries scoped to a specific project.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TocharianOU/jira-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server