4,000+ servers built on vurb.ts
Vinkius
VS Code CopilotIDE
Jira Software Cloud MCP Server

Bring Agile
to VS Code Copilot

Learn how to connect Jira Software Cloud to VS Code Copilot and start using 31 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Create BoardCreate SprintGet Agile IssueGet Board BacklogGet Board ConfigurationGet Board EpicsGet Board SprintsGet BuildGet Deployment Gating StatusGet EpicGet Epic IssuesGet Issue EstimationGet Repository Dev InfoGet SprintGet Sprint IssuesLink Security WorkspacesList BoardsMove Issues To BacklogMove Issues To EpicMove Issues To SprintRank EpicsRank IssuesSet Issue EstimationStore Dev InfoSubmit BuildsSubmit DeploymentsSubmit Feature FlagsSubmit IncidentsSubmit Remote LinksSubmit VulnerabilitiesUpdate Sprint

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Jira Software Cloud

What is the Jira Software Cloud MCP Server?

Connect your Jira Software Cloud instance to any AI agent to streamline your Agile project management. This server provides deep integration with Jira's Software-specific features like Boards, Sprints, and Epics.

What you can do

  • Board Management — List all Scrum and Kanban boards, fetch their configurations, and view associated Sprints or Epics.
  • Sprint Control — Create new sprints, retrieve sprint details, and update sprint states (start or complete) to keep your team moving.
  • Backlog & Issues — Query board backlogs, fetch issues within specific sprints or epics, and manage issue rankings.
  • Estimation Tracking — Retrieve and set story point estimations for agile issues to maintain velocity visibility.
  • DevOps Integration — Submit and query development information including builds, deployments, and feature flags.

How it works

  1. Subscribe to this server
  2. Provide your Jira Domain, Email, and API Token
  3. Start managing your sprints and boards from Claude, Cursor, or any MCP client

Who is this for?

  • Scrum Masters & PMs — Quickly check sprint progress, move issues, and update sprint statuses without the heavy Jira UI.
  • Developers — Check backlog priorities and update estimations directly from your coding environment.
  • Release Managers — Track builds and deployments associated with Jira issues in real-time.

Built-in capabilities (31)

create_board

Requires name, type (scrum or kanban), and filterId. Create a new board

create_sprint

Create a new sprint

get_agile_issue

Get issue with Agile fields

get_board_backlog

Get issues for backlog

get_board_configuration

Get board configuration

get_board_epics

Get all epics for board

get_board_sprints

Get all sprints for board

get_build

Get build data

get_deployment_gating_status

Get deployment gating status

get_epic

Get epic details

get_epic_issues

Get issues for epic

get_issue_estimation

Get issue estimation

get_repository_dev_info

Get repository development information

get_sprint

Get sprint details

get_sprint_issues

Get issues for sprint

link_security_workspaces

Link security workspaces

list_boards

Get all boards in Jira Software

move_issues_to_backlog

Move issues to backlog

move_issues_to_epic

Move issues to epic

move_issues_to_sprint

Move issues to sprint

rank_epics

Rank epics

rank_issues

Rank issues

set_issue_estimation

Set issue estimation

store_dev_info

Store development information

submit_builds

Submit build data

submit_deployments

Submit deployment data

submit_feature_flags

Submit feature flag data

submit_incidents

Submit incidents or reviews

submit_remote_links

Submit remote link data

submit_vulnerabilities

Submit vulnerabilities

update_sprint

Can be used to start or complete a sprint by changing state to active or closed. Update a sprint

Why VS Code Copilot?

GitHub Copilot Agent mode brings Jira Software Cloud data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 31 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

  • VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

  • Project-scoped MCP configs (.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

  • Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

  • GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

See it in action

Jira Software Cloud in VS Code Copilot

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Jira Software Cloud and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Jira Software Cloud to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Jira Software Cloud in VS Code Copilot

The Jira Software Cloud MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 31 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Jira Software Cloud
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Jira Software Cloud for VS Code Copilot

Every tool call from VS Code Copilot to the Jira Software Cloud MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

How do I view the backlog for a specific board?

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

02

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

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

03

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

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

04

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

05

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

06

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

07

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

08

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Explore More MCP Servers

View all →