jira-mcp-scoped
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the HTTP transport (default: 3456) | |
| JIRA_BASE_URL | Yes | Your Jira instance URL, e.g. https://yourcompany.atlassian.net | |
| JIRA_BOARD_ID | No | Board ID used when placing issues in the current sprint | |
| JIRA_API_TOKEN | Yes | Jira API token — generate one at id.atlassian.com/manage-profile/security/api-tokens | |
| JIRA_LOG_LEVEL | No | Log verbosity: error, info (default), or debug. See Logging. | info |
| JIRA_USER_EMAIL | Yes | The email address of your Jira account | |
| JIRA_PROJECT_KEY | Yes | The project key, e.g. PROJ | |
| JIRA_ATTACHMENTS_DIR | No | Directory to save downloaded attachments (default: ./jira-attachments) | ./jira-attachments |
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
- 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/MichalOsadowski/jira-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server