Jira Context

Provides Jira data access, sprint analysis, and vulnerability checks through MCP integration with Cursor IDE.
  • typescript

0

GitHub Stars

typescript

Language

3 months ago

First Indexed

3 weeks ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

You install and run an MCP server that connects Jira with Cursor IDE to manage issues, track sprints, and analyze library vulnerabilities. It exposes practical integration points you can use directly from Cursor to fetch Jira data, monitor progress, and perform vulnerability checks within your development workflow.

How to use

Connect from Cursor IDE to the Jira Context MCP Server to start querying Jira data and running analysis. You can use the HTTP connection for quick integration or run the local MCP server as a stdio process and connect via the MCP URL. After connecting, you will access a suite of tools to manage issues, analyze sprints, and inspect dependencies directly from chat or commands.

How to install

Prerequisites you need before installation are Node.js 20.17.0 or higher and a Jira account with API access. Prepare a Jira API token and your Jira instance URL for authentication.

Step-by-step setup commands you will run:

Additional setup notes

Configure your environment and start the MCP server to enable Cursor integration. The process includes cloning the project, installing dependencies, creating a local environment file, building the project, and running or wiring it up for Cursor access.

Configuration and access

Two primary ways to connect from Cursor exist: a local stdio configuration and a direct HTTP URL. The local setup runs a Node process that hosts the MCP server, while the HTTP method connects to a running MCP endpoint.

Security and troubleshooting

Guard sensitive information such as Jira API tokens and database credentials. Use absolute paths for local MCP configurations, keep tokens secret, and ensure your environment variables are correctly set. If you run into issues, verify Node.js version, port availability, and that the build artifacts exist in dist.

Examples and tooling

Once connected, you can leverage tools for Jira issue management, sprint analytics, library vulnerability checks, and database queries. See each tool under Available Tools for the full capabilities.

Troubleshooting

Common issues include server startup failures due to missing dependencies or misconfigured environment variables, connection problems in Cursor, and Jira API errors stemming from invalid tokens or incorrect base URLs. Ensure you followed the installation steps exactly and restarted Cursor after configuration changes.

Available tools

get_issue

Fetch detailed information for a Jira issue including fields, status, and history.

get_assigned_issues

List issues assigned to your Jira user, with optional filters by project or type.

get_issues_by_type

Filter issues by type such as Bug, Story, Epic, Task, etc.

get_projects

List all Jira projects available to your account.

get_issue_types

List all Jira issue types available for your projects.

analyze_jira_url

Parse and extract insights from any Jira URL such as boards, sprints, or issues.

get_boards

List all Agile boards in your Jira instance.

get_sprints

Retrieve sprints for a selected board.

get_sprint_issues

Get all issues contained in a specific sprint.

get_backlog

Retrieve backlog issues for a board or project.

get_sprint_report

Generate a comprehensive sprint report with metrics and insights.

check_maven_library

Check a Maven library for known vulnerabilities and upgrade guidance.

check_npm_library

Check an NPM package for vulnerabilities and upgrade recommendations.

analyze_dependencies

Analyze project dependencies for risks and outdated versions.

recommend_upgrade

Provide smart upgrade recommendations based on dependency analysis.

get_github_release_notes

Fetch release notes for library upgrades from GitHub.

find_library_usage

Identify where a library is used within a codebase.

list_databases

List all MySQL databases accessible from the configured host.

list_db_tables

List tables within a selected database.

get_table_schema

Retrieve the schema of a specified table.

query_database

Execute SQL queries against the connected MySQL database.

search_table

Search across table columns to find relevant data.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational