GitHub-Jira MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_URL | Yes | Your Jira instance URL (e.g., https://your-domain.atlassian.net) | |
| LOG_LEVEL | No | Optional: Logging level | INFO |
| GITHUB_TOKEN | Yes | Your GitHub Personal Access Token | |
| JIRA_CLIENT_ID | Yes | Your Jira OAuth client ID | |
| JIRA_ACCESS_TOKEN | No | Optional: Jira access token (will be obtained automatically via OAuth) | |
| JIRA_CLIENT_SECRET | Yes | Your Jira OAuth client secret | |
| JIRA_REFRESH_TOKEN | No | Optional: Jira refresh token (will be obtained automatically via OAuth) |
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
ActivityInactive
ResponsivenessNo issues