MCP Jira
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_URL | No | The URL of your Jira instance | |
| NO_PROXY | No | Comma-separated list of hosts to bypass proxy (e.g., localhost,.your-company.com) | |
| HTTP_PROXY | No | HTTP proxy URL (e.g., http://proxy.internal:8080) | |
| HTTPS_PROXY | No | HTTPS proxy URL (e.g., http://proxy.internal:8080) | |
| MCP_VERBOSE | No | Set to 'true' for more detailed logging | |
| SOCKS_PROXY | No | SOCKS proxy URL | |
| ENABLED_TOOLS | No | Comma-separated list of tool names to enable (e.g., 'jira_search,jira_get_issue') | |
| JIRA_USERNAME | No | Your email address for Jira Cloud authentication | |
| JIRA_API_TOKEN | No | Your Jira API token for Cloud authentication | |
| READ_ONLY_MODE | No | Set to 'true' to disable write operations | |
| JIRA_SSL_VERIFY | No | Set to 'false' to disable SSL verification for self-signed certificates | |
| MCP_VERY_VERBOSE | No | Set to 'true' for very detailed debug logging | |
| MCP_LOGGING_STDOUT | No | Set to 'true' to log to stdout instead of stderr | |
| JIRA_CUSTOM_HEADERS | No | Comma-separated key=value pairs of custom HTTP headers (e.g., X-Forwarded-User=service-account,X-Company-Service=mcp-atlassian) | |
| JIRA_PERSONAL_TOKEN | No | Your Personal Access Token for Server/Data Center authentication | |
| JIRA_PROJECTS_FILTER | No | Filter by project keys (e.g., 'PROJ,DEV,SUPPORT') | |
| ATLASSIAN_OAUTH_SCOPE | No | OAuth 2.0 scopes for Jira access (e.g., read:jira-work write:jira-work offline_access) | |
| ATLASSIAN_OAUTH_ENABLE | No | Set to 'true' to enable minimal OAuth mode for multi-cloud scenarios | |
| ATLASSIAN_OAUTH_CLOUD_ID | No | Atlassian Cloud ID for OAuth authentication | |
| ATLASSIAN_OAUTH_CLIENT_ID | No | OAuth 2.0 client ID from Atlassian Developer Console | |
| ATLASSIAN_OAUTH_ACCESS_TOKEN | No | Pre-existing OAuth 2.0 access token for BYOT method | |
| ATLASSIAN_OAUTH_REDIRECT_URI | No | OAuth 2.0 redirect URI (e.g., http://localhost:8080/callback) | |
| ATLASSIAN_OAUTH_CLIENT_SECRET | No | OAuth 2.0 client secret from Atlassian Developer Console |
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 | |
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/amruthabesto28/JIRA-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server