Atlassian Rovo MCP Server is a cloud-hosted bridge that lets compatible AI tools access Atlassian Cloud data and actions through the Model Context Protocol. Developers and project teams use it with Jira, Confluence, Jira Service Management, Bitbucket, Compass, Loom, and other Atlassian services, authenticated through OAuth 2.1 or API tokens. The catalogue entries provide skills, MCP connections, and a plugin for using the server.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add atlassian/atlassian-mcp-server --skill jira-sprint-dashboardgit clone --depth 1 https://github.com/atlassian/atlassian-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/atlassian/atlassian-mcp-server/jira-sprint-dashboard)<a href="https://agentmods.dev/skills/atlassian/atlassian-mcp-server/jira-sprint-dashboard"><img src="https://agentmods.dev/badge/skills/atlassian/atlassian-mcp-server/jira-sprint-dashboard/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/atlassian/atlassian-mcp-server/jira-sprint-dashboard"><img src="https://agentmods.dev/badge/skills/atlassian/atlassian-mcp-server/jira-sprint-dashboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 4 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00112 | $0.03533 |
| Opus 5 | $0.00056 | $0.01767 |
| Sonnet 5 | $0.00022 | $0.00707 |
| Haiku 4.5 | $0.00011 | $0.00353 |
Grade A, and why
jira-sprint-dashboard scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- jira-sprint-dashboard — 100% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 369 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Sprint Dashboard
Build a focused dashboard that helps an engineering manager, tech lead, or senior engineer see current Jira work quickly enough to decide what needs attention. The output is a dashboard, not a prose report and not a generic health score.
This skill is read-only by default. Do not create, update, transition, assign, or comment on Jira work items unless the user explicitly asks for a write action after reviewing the dashboard.
Output Mode
Use the richest dashboard renderer supported by the current environment. The dashboard content, claims, counts, and source appendix must stay consistent across renderers; only the presentation changes.
Choose the renderer in this order:
- Cursor Canvas, if running in Cursor with Canvas support.
- Interactive artifact, if the current agent supports HTML, React, or similar artifact output.
- Static HTML file, if file creation is available and useful.
- Markdown dashboard, if no richer visual renderer is available.
- Structured JSON plus concise summary, only if visual rendering is impossible.
Do not mention that Cursor Canvas is unavailable unless the user specifically asked for Cursor Canvas. If the user asked for a dashboard generally, use the best available renderer without apologizing for the environment.
Cursor Canvas Renderer
Use this section only when running in Cursor with Canvas support.
Read ~/.cursor/skills-cursor/canvas/SKILL.md before writing canvas code. If
you need exact exports or prop shapes, read the files in
~/.cursor/skills-cursor/canvas/sdk/.
Canvas constraints:
- Create one
.canvas.tsxfile in the Cursor canvases directory. - Import only from
cursor/canvas. Do not importreact,CSSProperties,JSX, Atlaskit, or other packages. - Embed Jira data inline in the canvas; do not fetch from the canvas.
- Prefer Canvas primitives such as
Stack,Grid,Card,Stat,Table,Pill,Callout,UsageBar,BarChart,LineChart,PieChart, andCodeover raw HTML. - Use
useHostTheme()for custom styles. Do not hardcode hex colors, gradients, box shadows, ADS variables, unsupported CSS frameworks, or@atlaskit/*. - Do not publish or share the canvas unless the user asks.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago Changed · +12 lines 0a812dc617d5
- 11d ago First seen · 357 lines · 112 tokens per session scan A 3e78ef20541e
jira-sprint-dashboard is a skill published in the GitHub repository atlassian/atlassian-mcp-server (1,032 stars, last pushed yesterday), licensed Apache-2.0. It adds 112 tokens to every session and 3,533 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
kanban-video-orchestrator
Plan and run multi-agent video production pipelines.
sdlc-review
Review Kanban handoffs and route verified outcomes.
teams-meeting-pipeline
Teams meeting summaries, job replay, Graph subscriptions.
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
meeting-action-items
Turn meeting notes into cited decisions, owners, tickets.
gh-issues
Use when creating, triaging, or commenting on GitHub issues for the Kilo VS Code extension or JetBrains plugin via gh. Covers issue templates, project board assignment, title conventions, and required gh scopes.