klauseduard vibe coded jira mcp

WHAT IT CONNECTS

What klauseduard vibe coded jira mcp gives an AI Agent

• Get JIRA issues by key
• Search issues using JQL (JIRA Query Language)
• Create and update issues (note: may have limitations with heavily customized JIRA projects)
• Add comments to issues
• Clone issues (useful for working around mandatory custom fields, but may have limitations with complex project configurations)
• Configurable field selection
• Pagination support
• Detailed error handling and logging
• Log work
• Create a virtual environment:
• Install dependencies:
• Configure environment variables:
• **Models** (`src/models/`)
• `IssueType`, `IssueArgs` - Issue creation/update models
• `IssueTransitionArgs` - Issue state transition model
• `CloneIssueArgs` - Issue cloning model
• `CommentArgs`, `GetCommentsArgs` - Comment models
• `LogWorkArgs` - Work logging model
• **Core** (`src/core/`)
• `JiraClient` - Main JIRA API client
• `JiraConfig` - Configuration management
• Error handling and logging
• **Operations** (`src/operations/`)
• Issue management (get, search, create, update, clone)
• Comment handling (add, get)
• Work logging
• Project listing
• ✅ Basic JIRA integration
• ✅ Search functionality with JQL support
• ✅ Issue management (create, update, clone) with limitations for heavily customized projects
• ✅ Comment functionality
• ✅ Work logging
• [Model Context Protocol](https://github.com/modelcontextprotocol) - The main MCP project
• [MCP Python SDK](https://github.com/modelcontextprotocol/python-sdk) - The SDK we use to implement this server
• [MCP Documentation](https://github.com/modelcontextprotocol/docs) - Protocol documentation and specifications
• **Personal/Development Use**: Ideal for individual developers managing their JIRA workflows
• **Small Team Use**: Suitable for trusted team environments with proper security measures
• **NOT Recommended For**:
• Production deployment in its current form
• Multi-tenant environments
• Public-facing services
• Processing sensitive/regulated data
• Your JIRA instance uses HTTPS
• You're using API tokens (not passwords) for authentication
• Your `.env` file is properly secured and not committed to version control
• You understand the risks of running third-party tools with JIRA access
• Regularly rotate your API tokens
• Monitor your JIRA audit logs for unexpected activity
• Use the most recent version of the tool
• Review the code before use in your environment
• Implementing additional security controls
• Conducting a security review
• Contributing security improvements back to the project
• Using official enterprise-grade alternatives