JIRA MCP Server
by JasserAmri
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_PORT | No | The port to use for HTTP transport mode (defaults to 3000). | 3000 |
| JIRA_TYPE | No | The type of Jira instance: 'cloud' (Atlassian-hosted, default) or 'server' (self-hosted). | cloud |
| JIRA_BASE_URL | Yes | The base URL of your Jira instance (e.g., https://your-domain.atlassian.net). | |
| JIRA_API_TOKEN | Yes | API token for Jira Cloud, or Personal Access Token (PAT) / password for Jira Server/Data Center. | |
| JIRA_AUTH_TYPE | No | Authentication method: 'basic' (default) or 'bearer'. Use 'bearer' for Personal Access Tokens on Jira Server/Data Center. | basic |
| TRANSPORT_MODE | No | The transport mode for the MCP server: 'stdio' (default for Claude Desktop/Cline) or 'http' (for Postman/Inspector). | stdio |
| JIRA_USER_EMAIL | Yes | Your Jira account email address. |
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
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 | |
This server cannot be deployed
Maintenance
ActivityStale
ResponsivenessNo issues