Jira MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_HOST | Yes | Your Jira instance URL (e.g., https://yourcompany.atlassian.net) | |
| JIRA_EMAIL | Yes | Your Atlassian account email | |
| JIRA_API_TOKEN | Yes | API token from Atlassian Account Settings (https://id.atlassian.com/manage-profile/security/api-tokens) |
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
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jira_issueA | Manage Jira issues: get, create, update, delete, bulk-create, list/perform transitions, assign, and read changelog. Returns trimmed summaries with refs to full payloads on disk. |
| jira_searchA | Search Jira issues with JQL or fetch JQL autocomplete metadata. Issue results come back as a trimmed list with refs. |
| jira_commentA | List, add, update, and delete comments on a Jira issue. Bodies are ADF documents. |
| jira_userC | Look up Jira users: current authenticated user, search by query/accountId, list assignable users for a project or issue, or bulk-fetch by accountId. |
| jira_projectA | Manage Jira projects, their components, versions, and per-issue-type statuses. |
| jira_boardA | Manage Agile boards: list/get/create/delete, fetch configuration, list board issues, backlog, and epics. |
| jira_sprintA | Manage Jira sprints: list/get/create/update/delete, list sprint issues, and move issues in or out. |
| jira_epicA | Inspect epics, list issues under an epic, and move issues into or out of epics. |
| jira_worklogA | List, add, update, and delete worklogs on an issue. Supports remaining-estimate adjustment. |
| jira_attachmentA | Add, inspect, or delete attachments. |
| jira_filterA | Manage saved JQL filters: list/get/create/update/delete plus the current user's favourites. |
| jira_linkA | Create, fetch, delete issue links, and list available link types. |
| jira_watcherA | List, add, and remove watchers on an issue. Also: list votes and toggle the current user's vote. |
| jira_fieldA | List Jira metadata: fields, issue types, priorities, statuses, resolutions, and per-project createMeta. |
| jira_groupA | Search groups, list group members, and inspect the current user's permissions. |
| jira_serverA | Inspect the Jira server: version, build, deployment type. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Jira Projects | List of all accessible Jira projects |
| Jira Boards | List of all accessible Jira boards (Scrum and Kanban) |
| Current User | Information about the currently authenticated user |
TDQS
Scored across 16 tools
Each tool targets a distinct Jira resource (issue, project, board, sprint, etc.) with no functional overlap. Tool names clearly indicate the resource they operate on.
All tools follow the consistent pattern 'jira_<resource_noun>', making it easy to predict tool names. No mixing of conventions.
16 tools cover the major Jira entities comprehensively without being excessive. The scope matches typical Jira usage well.
The tool set covers CRUD operations for core entities (issues, projects, boards, sprints), plus search, user management, and metadata. No obvious gaps for standard workflows.