jira

This MCP server provides a JIRA integration that exposes MCP-compatible endpoints to interact with JIRA projects and issues. The server is implemented in Go and can run in standard stdio mode or in SSE mode for streaming events. Start the server with Go tooling and supply your JIRA credentials via environment variables. By default, the server starts on port 3000 in stdio mode and can be switched to SSE mode with a flag.

To connect, provide your JIRA API key and username in the environment variables described in the config. The server will handle authentication against the JIRA Cloud API and expose MCP-style endpoints for querying issues, creating and updating issues, and subscribing to updates via SSE when enabled. Use the --transport sse option to enable Server-Sent Events for real-time updates and the --port flag to customize the listening port.

Prerequisites:

• Go 1.16 or later installed on your system (https://golang.org/dl/)
• Access to a JIRA Cloud instance and a Jira API key with appropriate permissions

Installation steps:

1. Clone the repository: git clone https://github.com/your-org/tot-git27-jira-mcp-server.git
2. Navigate to the project directory: cd tot-git27-jira-mcp-server
3. Set up environment variables (example): export JIRA_USERNAME=your-jira-username export JIRA_API_KEY=your-jira-api-key export JIRA_BASE_URL=https://your-domain.atlassian.net
4. Run the server (stdios mode): go run main.go
5. Run the server in SSE mode (for real-time updates): go run main.go --transport sse
6. Optional: build a binary for production: go build -o jira-mcp-server main.go ./jira-mcp-server

Notes:

• Ensure your Go version is compatible with the project (Go 1.16+).
• The JIRA_BASE_URL should point to your Jira Cloud instance. For on-prem Jira Server, adjust accordingly.

Tips and considerations:

• The server relies on JIRA API authentication via username and API key; keep these credentials secure and consider using a secrets manager in production.
• If you encounter authentication errors, verify that the API key has the necessary scopes (e.g., read/write issues) and that the base URL is correct.
• When using SSE transport, ensure your network allows streaming connections and that clients subscribe to the SSE endpoint as documented by the server.
• If you need to customize ports or endpoints, use the --port flag and review any additional CLI options in the Go code or help output.
• Logging level and formats may be configurable; start with default settings and increase verbosity if debugging.