Jira MCP Server
by stolostron
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | Yes | Your email address associated with the Atlassian account (required for Cloud authentication) | |
| JIRA_TEAMS | No | JSON object mapping team names to arrays of usernames (e.g., {"frontend": ["alice", "bob"]}) | |
| JIRA_TIMEOUT | No | Timeout in seconds for Jira API requests (default: 30) | 30 |
| JIRA_SERVER_URL | Yes | The URL of the Jira server (e.g., https://your-company.atlassian.net) | |
| JIRA_VERIFY_SSL | No | Whether to verify SSL certificate (default: true) | true |
| JIRA_MAX_RESULTS | No | Maximum number of results to return from Jira (default: 100) | 100 |
| JIRA_ACCESS_TOKEN | Yes | Your personal access token for Jira authentication | |
| JIRA_COMPONENT_ALIASES | No | JSON object mapping aliases to actual component names (e.g., {"ui": "User Interface"}) |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
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
- 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/stolostron/jira-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server