Jira Product Discovery MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jira_getA | Read any Jira data. Returns TOON format by default (30-60% fewer tokens than JSON). IMPORTANT - Cost Optimization:
Schema Discovery Pattern:
Output format: TOON (default, token-efficient) or JSON ( Common paths:
JQ examples: Example JQL queries: API reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/ |
| jira_postA | Create Jira resources. Returns TOON format by default (token-efficient). IMPORTANT - Cost Optimization:
Output format: TOON (default) or JSON ( Common operations:
API reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/ |
| jira_putA | Replace Jira resources (full update). Returns TOON format by default. IMPORTANT - Cost Optimization: Use Output format: TOON (default) or JSON ( Common operations:
Note: PUT replaces the entire resource. For partial updates, prefer PATCH. API reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/ |
| jira_patchA | Partially update Jira resources. Returns TOON format by default. IMPORTANT - Cost Optimization: Use Output format: TOON (default) or JSON ( Common operations:
Note: PATCH only updates the fields you specify, leaving others unchanged. API reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/ |
| jira_deleteA | Delete Jira resources. Returns TOON format by default. Output format: TOON (default) or JSON ( Common operations:
Note: Most DELETE endpoints return 204 No Content on success. API reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/ |
| jira_add_attachmentA | Upload one attachment to a Jira issue or Jira Product Discovery idea. The server converts UTF-8 or base64 content into Jira's required multipart request. Binary files must use encoding=base64. Uploading the same file twice creates two Jira attachments. |
| jira_list_jpd_insightsA | List native Jira Product Discovery Insights for an idea key. The server resolves the Jira site, project, issue IDs, and Polaris ARIs. It returns a normalized response and never exposes raw GraphQL or provider envelopes. |
| jira_create_jpd_insightA | Create a native Jira Product Discovery Insight with supporting evidence in its description. The server builds a fixed ADF description containing the summary, customer quote, and linked source. Creation uses the existing Jira OAuth bearer and does not create a structured snippet. |
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 8 tools
Each tool maps to a distinct HTTP method or unique action (get, post, put, patch, delete, add_attachment, list insights, create insight). Put vs patch could be confused, but descriptions clearly separate full replacement from partial updates, leaving no ambiguity.
All tool names follow a consistent jira_<verb>_<object> pattern in snake_case, using clear verbs (get, post, put, patch, delete, add, list, create). The naming is uniform and predictable with no mixed casing or vague terms.
With 8 tools, the set is well-scoped for a Jira/Product Discovery server, covering full CRUD, attachment upload, and Product Discovery insights. This falls comfortably in the ideal 3-15 range and each tool serves a distinct purpose.
Generic Jira operations are well covered via jira_get (search), post (create), put/patch (updates), and delete, including comments, worklogs, and attachments. The JPD insight tools add create and list, but lack update/delete for insights; however, generic verbs may cover some of that. The core surface is strong with minor gaps.