Jira Communication Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_URL | Yes | The URL of your Jira instance (e.g., https://XXXXXXXX.atlassian.net) | |
| JIRA_API_KEY | Yes | API token from https://id.atlassian.com/manage-profile/security/api-tokens | |
| JIRA_API_MAIL | Yes | Your email address for Jira API authentication |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_jqlC | Execute a JQL query on Jira on the api /rest/api/3/search. Do not use markdown in your query. |
| get_only_ticket_name_and_descriptionB | Get the name and description of the requested tickets on the api /rest/api/3/search. Do not use markdown in your query. |
| create_ticketC | Create a ticket on Jira on the api /rest/api/3/issue. Do not use markdown in any field. |
| list_projectsC | List all the projects on Jira on the api /rest/api/3/project. Do not use markdown in your query. |
| delete_ticketC | Delete a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}. Do not use markdown in your query. |
| edit_ticketC | Edit a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}. Do not use markdown in any field. |
| get_all_statusesC | Get all the status on Jira on the api /rest/api/3/status. Do not use markdown in your query. |
| assign_ticketB | Assign a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}/assignee. Do not use markdown in your query. |
| query_assignableC | Query assignables to a ticket on Jira on the api /rest/api/3/user/assignable/search?project={project-name}. Do not use markdown in your query. |
| add_attachment_from_public_urlA | Add an attachment from a public url to a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}/attachments. Do not use markdown in your query. |
| add_attachment_from_confluenceC | Add an attachment to a ticket on Jira from a Confluence page by its name on the api /rest/api/3/issue/{issueIdOrKey}/attachments. Do not use markdown in your query. |
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 11 tools
All tools have clearly distinct purposes: CRUD tickets, two attachment sources, project/status listing, JQL search, ticket retrieval by name&desc, assignee query, and assignment. No overlap.
All tool names follow a consistent verb_noun pattern in snake_case, with verbs like add, assign, create, delete, edit, execute, get, list, query. No mixing of styles.
11 tools is well-scoped for a Jira server, covering essential operations without being bloated or insufficient.
Covers major CRUD for tickets, search, projects, statuses, assignments, and attachments. Missing a generic 'get_ticket' for full details and some lifecycle features like transitions or comment management, but still quite complete.