Dynamic Jira Software Cloud MCP Server
by ndigrazia
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | MCP Server Host | 0.0.0.0 |
| MCP_PORT | No | MCP Server Port | 8000 |
| JIRA_BASE_URL | Yes | Atlassian Jira Instance URL (e.g., https://your-domain.atlassian.net) | |
| JIRA_USERNAME | Yes | Atlassian Account Email | |
| MCP_TRANSPORT | No | MCP Server Transport (sse or stdio) | sse |
| JIRA_API_TOKEN | Yes | Atlassian Account API Token | |
| ALLOWED_METHODS | No | Allowed HTTP Methods (comma-separated, e.g. 'get' for read-only or 'get,post,put,delete' for full CRUD) | get,post,put,delete |
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
ActivityMaintained
ResponsivenessNo issues