Jira MCP
by cfollette18
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Host to bind for HTTP transport, e.g. 127.0.0.1 | |
| MCP_PORT | No | Port to bind for HTTP transport, e.g. 8003 | |
| JIRA_EMAIL | Yes | Jira Cloud account email used for Basic auth | |
| MCP_JWKS_URI | No | JWKS URI for inbound JWT authentication (required for HTTP without MCP_JWT_SECRET) | |
| JIRA_API_PATH | No | Jira API path, defaults to /rest/api/3 | /rest/api/3 |
| JIRA_BASE_URL | Yes | Jira site origin, e.g. https://your-site.atlassian.net | |
| MCP_READ_ONLY | No | Set to 'true' to hide the create_issue tool | |
| MCP_TRANSPORT | No | Transport mode, e.g. 'http' for remote HTTP server (default is stdio) | |
| JIRA_API_TOKEN | Yes | Jira API token used for Basic auth | |
| MCP_JWT_ISSUER | No | Expected JWT issuer for inbound authentication | |
| MCP_JWT_SECRET | No | JWT secret for inbound authentication (alternative to MCP_JWKS_URI) | |
| JIRA_ISSUE_TYPE | No | Default issue type, defaults to 'Task' | Task |
| MCP_JWT_AUDIENCE | No | Expected JWT audience for inbound authentication | |
| JIRA_DESCRIPTION_FORMAT | No | Description format: 'adf' (Cloud v3) or 'plain' (Data Center v2) | |
| JIRA_SOURCE_TICKET_FIELD | No | Custom field id for Source Ticket #, e.g. customfield_10001 | |
| JIRA_CUSTOMER_ORDER_FIELD | No | Custom field id for Customer Order #, e.g. customfield_10002 |
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/cfollette18/mcp-jira'
If you have feedback or need assistance with the MCP directory API, please join our Discord server