Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JIRA_EMAILYesEmail for the API token
JIRA_DOMAINYesAtlassian domain (e.g., acme for acme.atlassian.net)
JIRA_API_TOKENYesAtlassian API token
JIRA_TOKEN_TYPENoclassic or scoped (auto-detected if omitted)
JIRA_DISABLED_TOOLSNoComma-separated tool names to hide

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
}
logging
{}
prompts
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
manage_attachmentsB

Manage Jira issue attachments (list, download, upload, delete). Actions: 'list', 'download', 'upload', 'delete'

manage_boardsB

Manage Jira agile boards and sprints. Actions: 'list_boards', 'get_board', 'list_sprints', 'get_sprint_issues', 'get_backlog', 'get_active_sprint', 'search_sprints', 'create_sprint', 'move_to_sprint'

manage_devinfoC

Get development information (branches, PRs, commits) linked to a Jira issue. Actions: 'get_dev_info'

manage_issuesC

Unified tool for Jira issue operations. Actions: 'get', 'list_types', 'get_links', 'get_history', 'create', 'update', 'assign', 'transition', 'add_comment', 'edit_comment', 'list_comments', 'delete', 'link', 'list_link_types', 'get_watchers', 'add_watcher', 'remove_watcher', 'move'

manage_metricsA

Get issue lifecycle metrics for dashboards and visualizations. Actions: 'get_dates' (raw date info, status transitions, time-in-status), 'get_metrics' (computed cycle time, lead time, time in current status, status breakdown)

manage_projectsB

List and get Jira project details and statuses. Actions: 'list', 'get', 'list_statuses', 'create'

manage_searchA

Search Jira issues using JQL or quick text search. Actions: 'jql', 'quick'

manage_usersC

Search and get Jira users. Actions: 'get_current', 'search', 'get'

manage_versionsC

List and get project versions (releases/fixVersions). Actions: 'list', 'get'

manage_worklogsB

Manage time tracking worklogs on Jira issues. Actions: 'list', 'add'

Prompts

Interactive templates invoked by user choice

NameDescription
dev_treeAnalyze development work (branches, PRs, commits) for an issue and its subtasks
release_notesGenerate release notes from a Jira version/release
sprint_statusGet current sprint status and progress
standup_reportGenerate a standup report from recent Jira activity

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 10 tools

Disambiguation5/5

Each tool is scoped to a distinct Jira domain (issues, projects, users, boards, worklogs, attachments, etc.), so the boundaries are clear. The only potential overlap is between searching within manage_search and listing within other tools, but the resource-specific naming prevents real ambiguity.

Naming Consistency5/5

All tools follow a consistent manage_<plural_noun> convention, and each tool exposes lowercase verb-style actions. This creates a predictable pattern that makes it easy to infer what each tool does.

Tool Count5/5

Ten tools is well-scoped for a Jira server. The count is large enough to cover distinct functional areas without becoming unwieldy, and the grouping of many actions under manage_issues keeps the surface organized.

Completeness4/5

Core Jira workflows are well covered: issues, projects, search, comments, attachments, worklogs, users, boards, sprints, and dev info. Minor gaps exist in version and worklog management (no create/update/delete for versions, no edit/delete for worklogs), but these are edge operations rather than critical missing workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues