better-jira-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_URL | Yes | The base URL of your Atlassian site, e.g. https://your.atlassian.net | |
| JIRA_USERNAME | Yes | Your Atlassian account email address | |
| JIRA_API_TOKEN | Yes | Your Atlassian API token |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| confluence_searchC | Search Confluence with CQL. |
| confluence_get_pageA | Get a Confluence page by id, or by space key + exact title. Body is returned as markdown. |
| confluence_get_page_childrenB | List the direct child pages of a page. |
| confluence_create_pageA | Create a Confluence page from markdown and return it re-read. |
| confluence_update_pageA | Update a page's body (markdown) and/or title. Handles versioning; returns the page re-read. The body replaces the whole page. Read it first with confluence_get_page if you want to edit rather than overwrite. |
| confluence_add_page_commentC | Add a footer comment (markdown) to a page. |
| atlassian_requestA | Raw pass-through to any Jira or Confluence REST endpoint. Use when no other tool fits. |
| jira_get_issueB | Get an issue. Description and comments are returned as markdown. |
| jira_search_issuesC | Search issues with JQL. |
| jira_create_issueA | Create an issue and return it re-read from Jira so you can verify it. |
| jira_update_issueB | Update an issue and return it re-read from Jira. |
| jira_add_commentA | Add a comment (markdown) to an issue. |
| jira_get_transitionsB | List the workflow transitions currently available for an issue. |
| jira_transition_issueA | Move an issue through a workflow transition (see jira_get_transitions). Comments are deliberately not accepted here; add one with jira_add_comment afterwards so its visibility is under your control. |
| jira_list_componentsA | List a project's components with their ids (names must match exactly when writing). |
| jira_find_userA | Find users by name or email. Returns accountIds, which is what assignee/reporter fields need: {"assignee": {"accountId": "..."}}. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |