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 |
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/Hopcos/jira-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server