An astronaut overseeing a futuristic data hub

Connect Jira Software Cloud to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Run your entire Agile workflow from your AI client.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 31 capabilities

We ship only the actions that matter.

Capability set01 / 08

01-04

4 capabilities in this set.

Part of 31 available through Jira Software Cloud.

  1. 01

    Get deployment gating status

    Checks the current deployment gating status for your releases.

  2. 02

    Get epic

    Retrieves the specific details of a Jira epic.

  3. 03

    Get issue estimation

    Fetches the current story point or time estimation for an issue.

  4. 04

    Get repository dev info

    Gets development-related information from your connected repository.

Capability set02 / 08

05-08

4 capabilities in this set.

Part of 31 available through Jira Software Cloud.

  1. 05

    Get sprint

    Returns the details for a specific Jira sprint.

  2. 06

    Link security workspaces

    Connects security workspaces to your Jira environment.

  3. 07

    Move issues to backlog

    Moves selected issues directly into the project backlog.

  4. 08

    Set issue estimation

    Updates the story point estimation for a specific issue.

Capability set03 / 08

09-12

4 capabilities in this set.

Part of 31 available through Jira Software Cloud.

  1. 09

    Submit builds

    Sends build data to Jira to track development progress.

  2. 10

    Submit feature flags

    Submits feature flag information to your Jira records.

  3. 11

    Get board sprints

    Lists all sprints associated with a specific board.

  4. 12

    Get build

    Retrieves data regarding a specific build.

Capability set04 / 08

13-16

4 capabilities in this set.

Part of 31 available through Jira Software Cloud.

  1. 13

    Get sprint issues

    Fetches all issues contained within a specific sprint.

  2. 14

    Move issues to epic

    Assigns issues to a specific epic.

  3. 15

    Rank epics

    Changes the priority ranking of your epics.

  4. 16

    Rank issues

    Adjusts the order and priority of issues within a board or backlog.

Capability set05 / 08

17-20

4 capabilities in this set.

Part of 31 available through Jira Software Cloud.

  1. 17

    Store dev info

    Saves development-related information to your Jira instance.

  2. 18

    Submit deployments

    Sends deployment data to Jira for tracking.

  3. 19

    Submit vulnerabilities

    Logs vulnerability data into your Jira records.

  4. 20

    Create board

    Creates a new Scrum or Kanban board using a filter ID.

Capability set06 / 08

21-24

4 capabilities in this set.

Part of 31 available through Jira Software Cloud.

  1. 21

    Get epic issues

    Lists all issues tied to a specific epic.

  2. 22

    Get board configuration

    Retrieves the setup and configuration of a Jira board.

  3. 23

    Move issues to sprint

    Moves issues from the backlog into an active or planned sprint.

  4. 24

    Create sprint

    Generates a new sprint for your project.

Capability set07 / 08

25-28

4 capabilities in this set.

Part of 31 available through Jira Software Cloud.

  1. 25

    Get agile issue

    Fetches an issue including all its specific Agile fields.

  2. 26

    Get board backlog

    Retrieves the list of issues currently in a board's backlog.

  3. 27

    Get board epics

    Lists all epics associated with a specific board.

  4. 28

    List boards

    Returns a list of all boards in your Jira Software instance.

Capability set08 / 08

29-31

3 capabilities in this set.

Part of 31 available through Jira Software Cloud.

  1. 29

    Submit incidents

    Logs incidents or reviews into Jira.

  2. 30

    Submit remote links

    Submits data for remote links in Jira.

  3. 31

    Update sprint

    Changes a sprint state to active or closed.

Real work

What teams actually run

01

Sprint Planning

Ask your agent to create a new sprint and move specific issues from the backlog into it.

02

Real-time Estimation

Update story points for a task immediately after a grooming session via your AI agent.

03

Deployment Tracking

Check if a deployment is gated or view recent build data associated with a ticket.

04

Backlog Grooming

Rank issues or move them to different epics to keep the project organized.

Automate a task

Put Jira Software Cloud to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Jira Software Cloud works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Jira Software Cloud to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

1253ms average. Fast in production.

Jira Software Cloud is checked daily against the live service.

Daily averagePeak 1624ms
Oct 3Today
Fastest day
847ms
Slowest day
1624ms
14-day trend
Improving-13%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 31 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Jira Software Cloud, so you can see the experience inside your AI.

It does not authenticate your account with Jira Software Cloud. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Jira Software Cloud Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_pIquAtHFeHLdgJuJVu2P6nteoAaXYoCxQuZ7gqmD/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Jira Software Cloud capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "jira-software-cloud-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_pIquAtHFeHLdgJuJVu2P6nteoAaXYoCxQuZ7gqmD/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Jira Software Cloud in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Jira Software Cloud owners hand off.

This MCP is built for teams running Agile workflows who want to manage project data without leaving their primary workspace.

  • 01

    Scrum Masters & PMs

    Use it to check sprint progress and update statuses without the Jira UI.

  • 02

    Developers

    Use it to check backlog priorities and update estimations from your IDE.

  • 03

    Release Managers

    Use it to track builds and deployments tied to specific Jira issues.

FAQ

Questions Jira Software Cloud owners ask.

  • 01

    How do I connect my Jira instance?

    You provide your Jira Domain, Email, and an API Token through the Vinkius interface. Once connected, the MCP is ready to use in your AI client.

  • 02

    Which AI clients can I use with this MCP?

    You can use this MCP with any compatible client, including Claude, Cursor, Windsurf, and VS Code.

  • 03

    Can I actually start and stop sprints?

    Yes, you can use the update sprint capability to change a sprint state to active or closed.

  • 04

    Does this work with Kanban boards?

    Yes, the MCP supports both Scrum and Kanban board management.

  • 05

    Can I update story points through my AI agent?

    Yes, you can use the set issue estimation capability to update story points for any issue.

  • 06

    How do I view the backlog for a specific board?

    Use the get_board_backlog capability with the target boardId. It will return all issues currently in the backlog for that Scrum or Kanban board.

  • 07

    Can I change a sprint's status to active or closed?

    Yes, use the update_sprint capability and provide the sprintId along with the desired state ('active' or 'closed').

  • 08

    Is it possible to check the story point estimation for an issue?

    Yes! The get_issue_estimation capability allows you to retrieve the estimation value for any specific agile issue using its ID.

Connect Jira Software Cloud to Claude, Cursor, ChatGPT & more