jira-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_URL | Yes | Atlassian site URL, e.g. https://myteam.atlassian.net | |
| JIRA_EMAIL | Yes | Atlassian account email (basic-auth pair with token) | |
| JIRA_TOKEN | Yes | API token from id.atlassian.com | |
| MCP_JIRA_BRIEF_MAX | No | Max length of <brief> summary on issue descriptions. 0 disables enforcement | 100 |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jira_versionA | Get the Jira MCP server version and service status. |
| jira_writeA | Create or update Jira resources (non-destructive). Call with operation="help" to list all available write operations. Otherwise pass the operation name and a JSON object with parameters. Example: jira_write(operation="CreateIssue", params={"project_key": "PROJ", "issue_type": "Task", "summary": "Fix login bug"}) |
| jira_executeA | Trigger Jira state changes (transition, assign, unassign). Distinct from write because these are side-effects on existing issues rather than resource creation. Call with operation="help" to list all available execute operations. Example: jira_execute(operation="TransitionIssue", params={"issue_key": "PROJ-1", "transition_id": "31"}) |
| jira_deleteA | Delete Jira resources (destructive, irreversible). Call with operation="help" to list all available delete operations. Otherwise pass the operation name and a JSON object with parameters. Example: jira_delete(operation="DeleteIssue", params={"issue_key": "PROJ-123"}) |
| jira_readA | Query Jira data (safe, read-only). Call with operation="help" to list all available read operations. Otherwise pass the operation name and a JSON object with parameters. Example: jira_read(operation="SearchIssues", params={"jql": "project = PROJ AND status = Open"}) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct operation category: status, write/update, state transitions, delete, and read. There is no overlap in purpose, making it easy for an agent to select the correct tool.
All tools follow a consistent 'jira_' prefix with a clear verb (version, write, execute, delete, read). The pattern is uniform and predictable.
Five tools is an appropriate scope for a Jira integration, covering all major actions without unnecessary granularity or fragmentation.
The tool set covers CRUD operations (write, read, delete), state transitions (execute), and service info. The reliance on 'help' sub-operations limits immediate discoverability but the surface is otherwise complete.