JIRA MCP Server
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 | |
| JIRA_SCOPES | No | Comma-separated list of permission scopes to restrict available tools (e.g., boards:read,sprints:read,issues:read) | |
| JIRA_BASE_URL | Yes | The base URL of your JIRA instance (e.g., https://your-domain.atlassian.net) | |
| JIRA_API_TOKEN | Yes | Your JIRA API token | |
| JIRA_ALLOWED_BOARDS | No | Pipe-separated list of board IDs or names to restrict access (e.g., 123|My Board) | |
| JIRA_ALLOWED_PROJECTS | No | Pipe-separated list of project keys to restrict access (e.g., PROJ|DEV) | |
| JIRA_ALLOWED_ISSUE_TYPES | No | Pipe-separated list of issue types to restrict access (e.g., Bug|Task|Story) |
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
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/SuppleAardvark/jira-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server