Docsmcp

Jira MCP Server

Connect FlowTrux workflows to Jira Cloud issues, projects, sprints, and transitions

The Jira MCP server provides 10 tools for managing Jira Cloud issues, projects, sprints, and workflow transitions.

Setup

Go to Atlassian API Tokens and create a token.
In FlowTrux, go to Settings > MCP Servers > Add > Jira Cloud.
Enter your Jira site URL (e.g., https://yoursite.atlassian.net), email, and API token.

Tools

Issues

Tool	Description	Required Params
`search_issues`	Search with JQL query	`jql`
`get_issue`	Get issue by key (e.g., PROJ-123)	`issue_key`
`create_issue`	Create an issue	`project_key`, `summary`, `issue_type`
`update_issue`	Update issue fields	`issue_key`
`transition_issue`	Move issue to new status	`issue_key`, `transition_name`
`add_comment`	Add comment to issue	`issue_key`, `body`

The transition_issue tool automatically finds the transition by name (e.g., "In Progress", "Done") from the available transitions for that issue.

Projects

Tool	Description	Required Params
`list_projects`	List accessible projects	(none)
`get_project`	Get project details	`project_key`

Sprints (Agile)

Tool	Description	Required Params
`list_sprints`	List sprints for a board	`board_id`
`get_sprint_issues`	Get issues in a sprint	`sprint_id`

Examples

AI triages incoming bug reports:

Webhook (bug report) → Agent (classify severity, extract details) → Action:MCP(jira, create_issue, {project_key: "BUG", summary: "{{steps.agent-1.output.response.title}}", issue_type: "Bug", priority: "{{steps.agent-1.output.response.severity}}", description: "{{steps.agent-1.output.response.details}}"})

Auto-transition issue on deploy:

Webhook (deploy success) → Transform (extract ticket keys) → Loop → Action:MCP(jira, transition_issue, {issue_key: "{{item}}", transition_name: "Done"}) → Slack (notify team)

Daily sprint summary:

Cron → Action:MCP(jira, search_issues, {jql: "sprint in openSprints() AND status != Done"}) → Agent (summarize progress) → Slack (post to #standup)

← GitHub Wialon→