Pinned copy of Atlassian’s agent plugin. It connects agents to Jira and Confluence through the Atlassian MCP server at https://mcp.atlassian.com/v2/mcp, and installs five of Atlassian’s skills:
capture-tasks-from-meeting-notes turns action items in meeting notes into Jira tasks.
jira-sprint-dashboard summarizes a sprint, board or filter as a dashboard. Its Cursor Canvas renderer applies only in Cursor; in Flexkit it answers with a report or Markdown.
search-company-knowledge finds and explains answers across Confluence and Jira.
spec-to-backlog turns a Confluence spec into epics and tickets.
triage-issue checks a bug report for duplicates before filing it.
The other upstream skills are not included. They depend on a skill that is longer than Flexkit accepts, on a bundled script, or on a local code workspace. Connections are labelled with the plugin name, because Atlassian’s MCP authorization server returns no identity token.
Connecting
Flexkit connects with OAuth through Atlassian’s authorization server. It asks for read, write and search access to Jira and Confluence, Rovo search, and offline_access so the connection stays signed in. It does not ask to delete content or manage projects, workflows and screens; those tools are also off by default in Atlassian. The agent acts as the person who connected Atlassian, with their permissions. A project connection is shared by everyone’s agent in the project. Creating or changing anything follows your project’s approval rules.
An organization admin must allow Flexkit first. Atlassian only accepts OAuth connections from domains on its supported list, and Flexkit is not on it yet. In Atlassian Administration, open your organization, go to Connectors → Atlassian MCP server, choose Add domain and add https://flexkit.io/plugins/oauth/mcp/callback. Until then, connecting fails on Atlassian’s side.
If your organization uses an IP allowlist for Atlassian Cloud, calls from Flexkit are blocked: Flexkit does not send requests from fixed IP addresses.
Jira Service Management tools need an Atlassian API token, so this plugin does not include them. Rovo search uses your organization’s Rovo credits.
Upstream: https://github.com/atlassian/atlassian-mcp-server
Docs: https://support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/
Included skills
capture-tasks-from-meeting-notes
Analyze meeting notes to find action items and create Jira tasks for assigned work. When an agent needs to: (1) Create Jira tasks or tickets from meeting notes, (2) Extract or find action items from notes or Confluence pages, (3) Parse meeting notes for assigned tasks, or (4) Analyze notes and generate tasks for team members. Identifies assignees, looks up account IDs, and creates tasks with proper context.
jira-sprint-dashboard
Create a visual Jira sprint dashboard from Jira project, space, sprint, board, filter, JQL, work item keys, or Jira URL data. Use when the user asks for a Jira sprint dashboard, standup dashboard, sprint review, delivery review, engineering manager dashboard, WIP review, planning view, closeout view, or a visual snapshot of Jira work that is more useful than a flat report. Use the richest dashboard format supported by the current agent, such as Cursor Canvas, an interactive artifact, HTML, or Markdown.
search-company-knowledge
Search across company knowledge bases (Confluence, Jira, internal docs) to find and explain internal concepts, processes, and technical details. When an agent needs to: (1) Find or search for information about systems, terminology, processes, deployment, authentication, infrastructure, architecture, or technical concepts, (2) Search internal documentation, knowledge base, company docs, or our docs, (3) Explain what something is, how it works, or look up information, or (4) Synthesize information from multiple sources. Searches in parallel and provides cited answers.
spec-to-backlog
Automatically convert Confluence specification documents into structured Jira backlogs with Epics and implementation tickets. When an agent needs to: (1) Create Jira tickets from a Confluence page, (2) Generate a backlog from a specification, (3) Break down a spec into implementation tasks, or (4) Convert requirements into Jira issues. Handles reading Confluence pages, analyzing specifications, creating Epics with proper structure, and generating detailed implementation tickets linked to the Epic.
triage-issue
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket with proper context, or (5) Add information to an existing ticket. Searches Jira for similar issues, identifies duplicates, checks fix history, and helps create well-structured bug reports.