Server detail
The jira-github-mcp server bridges the gap between project management and version control by exposing Jira and GitHub APIs directly to your LLM. Instead of manually switching tabs to sync tickets with code, developers can now automate the traceability chain within their IDE. The tool enables the AI to fetch Jira issue details, create corresponding GitHub branches, and track PR status based on ticket IDs. It is particularly useful for automating repetitive administrative tasks like updating ticket statuses upon commit or generating PR descriptions from issue requirements. By unifying these two ecosystems via the Model Context Protocol, it reduces context-switching overhead and ensures that the development lifecycle remains synchronized without manual data entry.
An MCP server that exposes TamarEngel/jira-github-mcp capabilities to MCP-compatible AI clients.
Collections featuring this MCP
Tool testing
tamarengel-jira-github-mcp
Call the MCP capabilities provided by TamarEngel/jira-github-mcp and return a structured result.
inputPass arguments according to the server tool schema.Connection modes
{
"mcpServers": {
"TamarEngel/jira-github-mcp": {
"url": "Generated by the provider after deployment"
}
}
}The Remote endpoint is generated by the provider after deployment; this page does not fabricate an unusable endpoint.
No npm package is recorded. Open the source repository to complete command and args.If no npm package is registered, follow the installation method in the source repository.
How to use
- 01Step 1
Review server capabilities and permission scope.
- 02Step 2
Copy the install command or JSON configuration.
- 03Step 3
Run a small connection test in your client.
- 04Step 4
Adopt it long term only after reviewing access and maintenance.
Discussions
Use this space to keep checking source information, usage experience and maintenance status.
Open source page