Contextual Jira Tracking — Daily Summaries in Slack with Runbear and MCP

Track Jira Progress—Where Your Team Already Works

Jira is powerful, but it’s easy to get buried in tickets, tabs, and tool-switching.

With Runbear and the Model Context Protocol (MCP), you can build a smart AI assistant that delivers focused Jira summaries—right where your team already works: Slack, Teams or Discord.

No more daily check-ins or status report pings. Just actionable context, delivered automatically.

Meet Your Jira Summary Assistant

Runbear’s Jira integration helps you keep tabs on issue status across projects and teams—without opening Jira at all.

This AI assistant uses MCP to fetch recently updated tickets, group them by status (To Do, In Progress, Done), and surface blockers or priority items.

Daily summaries appear in your Slack or Teams channel, keeping your team informed without interrupting the flow.

How to Set It Up

1. Sign Up for Runbear : Go to runbear.io and create an account.

2. Create your assistant (Claude model) Add an instruction prompt like:

## Description

This bot summarizes recent Jira activity to help teams stay aligned—without digging through dashboards.  
It uses Model Context Protocol (MCP) to fetch issues from the last 24 hours and delivers a clean, contextual update directly in Slack or Teams.

---

## How it Works

1. A user asks the bot for a Jira summary (e.g., “What changed in the last 24 hours?”).
2. The bot calls `jira.searchIssues` with a time range scoped to recent updates.
3. Retrieved issues are grouped and summarized:
   - Grouped by status (To Do, In Progress, Done)
   - Each ticket includes:
   - Ticket ID and title
   - Last updated timestamp
   - (Optional) Priority and assignee
4. The bot also provides a quick stats section:
   - Total tickets updated
   - Priority breakdown
   - Number of unassigned issues
5. If no tickets were found, the bot replies with a polite message (e.g., “No major updates in the last 24 hours.”)

---

## What the Bot Should Do

- Always use `jira.*` tools to retrieve real data.
- Never invent or assume missing information.
- Group and format output clearly so teams can scan it at a glance.
- Ignore ticket comments or closed/archived issues.
- Decline non-Jira or out-of-scope queries.

3. Choose the “Jira” MCP server

4. Connect assistant to your channel-Slack, Teams or Discord

Why It Matters

Not every update needs a meeting.

• 🗂️ Stay informed without navigating Jira
• 🧠 Understand what’s moving—and what’s blocked
• 🕘 Get updates on your schedule (e.g., every morning)
• 🛠 Works across teams, regions, and roles
• 🚫 Skip noisy ticket comments and closed work

Get Started in Minutes

You can build this summary assistant in under 15 minutes.

All you need is:

• A Runbear account
• Access to your Jira workspace
• A team that prefers context over clutter