Jira Product Discovery MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/aavaz-ai/jira-product-discovery-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server