jira-mcp-server
by Hopcos
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | HTTP bind address | 127.0.0.1 |
| MCP_PORT | No | HTTP TCP port | 8080 |
| JIRA_TOOLS | No | Tool permission allowlist (read/create/update/delete/write or exact tool names). Empty means all tools are enabled. | |
| HTTPS_PROXY | No | Outbound proxy URL (honored by httpx trust_env) | |
| MCP_LOG_FILE | No | Log file path; empty means stderr | |
| JIRA_BASE_URL | Yes | Jira instance URL; must be https:// (e.g., https://acme.atlassian.net) | |
| MCP_AUTH_MODE | No | HTTP client authentication mode: 'none' or 'token' | none |
| MCP_LOG_LEVEL | No | Logging level: DEBUG, INFO, WARNING, ERROR | INFO |
| MCP_TRANSPORT | No | Transport mode: 'stdio', 'http' (SSE), or 'http-streamable' | stdio |
| JIRA_API_TOKEN | Yes | Jira API token (Cloud) or Personal Access Token (Server). Required. | |
| JIRA_RATE_LIMIT | No | Client-side requests per minute (token bucket) | 100 |
| JIRA_USER_EMAIL | No | Account email for Jira Cloud Basic auth. Required when JIRA_AUTH_METHOD is 'basic'. | |
| JIRA_AUTH_METHOD | No | Authentication method: 'basic' for Jira Cloud or 'bearer' for Data Center/Server | basic |
| MCP_CORS_ORIGINS | No | Comma-separated allowed CORS origins | * |
| MCP_SERVER_TOKEN | No | Bearer token clients must send. Required when MCP_AUTH_MODE is 'token'. | |
| JIRA_PROJECT_KEYS | No | Comma-separated allowlist of project keys; reads are scoped and writes are blocked outside this list (e.g., 'ENG,SALES') | |
| JIRA_CONNECT_TIMEOUT | No | Connection-establishment timeout in seconds | 10 |
| JIRA_REQUEST_TIMEOUT | No | Per-request timeout in seconds | 30 |
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 | |