Jira MCP server for Claude, ChatGPT, Claude Code and Cursor

How to connect Jira

1. 1
   Click Connect Jira free and sign in to Jira.
2. 2
   Add ContextGate to your AI app:

   ClaudeChatGPTClaude CodeCursorGitHub CopilotCodexGemini CLIOther

   1. 1

      In Claude, open Settings → Connectors and click Add custom connector.

   2. 2

      Name it ContextGate and paste this URL:

      https://api.contextgate.ai/mcp

   3. 3

      Click Add, then Connect, and sign in to ContextGate.

   4. 4

      In a chat, turn ContextGate on from the + menu → Connectors. Cowork and the desktop app use the same connectors.

   The full Claude guide

   1. 1

      In ChatGPT settings, open Apps & Connectors (or Connectors) → Advanced and turn on Developer mode.

   2. 2

      Create a connector, choose OAuth, and paste this URL:

      https://api.contextgate.ai/mcp

   3. 3

      Sign in to ContextGate when ChatGPT redirects you, then pick the connector in a chat.

   The full ChatGPT guide

   1. 1

      Run this in a terminal:

      claude mcp add --transport http contextgate https://api.contextgate.ai/mcp

   2. 2

      Start Claude Code, run /mcp, choose contextgate and sign in to ContextGate.

   The full Claude Code guide

   Add to Cursor

   1. 1

      Click Add to Cursor, or add this to ~/.cursor/mcp.json:

      {
        "mcpServers": {
          "contextgate": {
            "url": "https://api.contextgate.ai/mcp"
          }
        }
      }

   2. 2

      In Cursor Settings → MCP, sign in to ContextGate when Cursor asks.

   The full Cursor guide

   Add to VS Code

   1. 1

      Click Add to VS Code, or add this to .vscode/mcp.json:

      {
        "servers": {
          "contextgate": {
            "type": "http",
            "url": "https://api.contextgate.ai/mcp"
          }
        }
      }

   2. 2

      Start the server when VS Code asks, sign in to ContextGate, and use it from Copilot Chat in Agent mode.

   The full GitHub Copilot guide

   1. 1

      Run this in a terminal:

      codex mcp add contextgate --url https://api.contextgate.ai/mcp

   2. 2

      Then sign in to ContextGate:

      codex mcp login contextgate

   The full Codex guide

   1. 1

      Run this in a terminal:

      gemini mcp add --transport http contextgate https://api.contextgate.ai/mcp

   2. 2

      In Gemini CLI, run /mcp auth contextgate and sign in to ContextGate.

   The full Gemini CLI guide

   1. 1

      Add a remote (HTTP) MCP server with this URL:

      https://api.contextgate.ai/mcp

   2. 2

      Apps that support MCP sign-in ask you to sign in to ContextGate the first time they connect.

   3. 3

      An app that can't sign in can use a workspace API key instead: create one under API keys and add ?api_key=<your key> to the URL.

   More on adding it to any MCP app
3. 3
   Ask your AI app to use Jira, then open Activity to see the call.

Atlassian's own MCP server

• ContextGate now connects to Atlassian's own MCP server by default. One sign-in with your Atlassian account covers Jira and Confluence.
• ContextGate's app connector for Jira is still there, under Ways to connect on the same card.
• Whichever way you connect, your tool switches, policies and Activity work the same.

What you get with Jira and ContextGate

• Your AI apps can use JiraClaude, Cursor, ChatGPT and other AI apps reach Jira through the one ContextGate connection you add to them.
• You choose which tools they can useSwitch off any Jira tool you don't want used. It's hidden from your AI apps and refused if called.
• Every call is checked and recordedYour policies check each call (for example, personal data is hidden and secrets are blocked), and Activity keeps a record of it.

ContextGate sees only the tool calls that go through it, not your AI app's built-in tools or your chats.

Jira tools

Examples of what your AI apps can do in Jira. You'll see the exact list of tools after you connect it.

• create_issueCreates a new issue in a specified Jira project. This includes setting parameters such as the issue type, summary, and assignee details. Note: Some projects may have custom required fields - use JIRA_GET_FIELDS to discover them if needed.
• edit_issueUpdates a specified Jira issue by changing its fields or adding new information. This action allows users to modify attributes such as the summary, description, and assignee of the issue.
• delete_issueThis action deletes a specified Jira issue. It can also delete any associated subtasks if requested.
• create_projectThis action creates a new Jira project with the necessary configurations. It requires information such as the project key, name, type, and template to successfully set up a project in Jira.
• add_watcher_to_issueThis action adds a specified user as a watcher to a Jira issue. A watcher receives notifications about updates to the issue.
• delete_worklogThis action deletes a specific worklog entry from a Jira issue. It provides options to notify users and adjust the issue's remaining estimate as needed.
• add_commentThis action adds a rich comment to a specific Jira issue, allowing Markdown formatting. Users can specify visibility restrictions for the comment if needed.
• update_commentThis action updates an existing comment on a Jira issue. Users can modify the comment text and adjust visibility settings as needed.
• delete_commentThis action deletes a specified comment from a Jira issue. It requires the issue ID or key along with the comment ID to perform the delete operation.
• add_attachmentThis action allows users to upload a file and attach it to a specific Jira issue. It supports various file formats and ensures that the attachment is associated with the correct issue key.
• assign_issueThis action assigns a specified Jira issue to the designated user or the project's default assignee. It also allows for unassigning the issue by not providing an account ID and supports lookup by username or email.
• bulk_create_issueThis action creates multiple Jira issues in a single API call. It allows for bulk creation of issues with various attributes, such as assignee and priority, streamlining the issue management process.
• create_issue_linkThis action links two Jira issues based on the specified relationship type. It allows users to track dependencies and relationships between issues within their projects.
• create_sprintThis action allows the creation of a new sprint within a specified Jira board. Users can set optional start and end dates, as well as define a primary goal for the sprint.
• create_versionThis action creates a new version within a specified Jira project, allowing users to manage project milestones effectively. It includes attributes such as name, description, and release dates that provide context to the version being created.
• find_usersThis action allows you to search for Jira users using various parameters like email or display name. It returns a list of users that match the search criteria for further operations.
• get_all_projectsRetrieves a list of all projects that the user has visibility over. This action allows filtering, sorting, and pagination of project results based on specified criteria.
• get_all_usersThis action retrieves a list of all users from the Jira instance. If no pagination parameters are provided, the action automatically iterates through all pages to return all available users. It also supports manual pagination using the provided parameters.
• get_current_userThis action retrieves detailed information about the currently authenticated Jira user. It provides data such as the user's display name, email address, groups, and application roles.
• get_issueThis action retrieves a specific Jira issue using its ID or key. Users can customize the fields and additional data included in the response to suit their specific needs.
• get_issue_typesRetrieves a list of all available Jira issue types for the user. This action allows access to Jira's issue type details that can be utilized within the application.
• get_transitionsThis action retrieves the available workflow transitions for a specified Jira issue. It can return details about the transitions, including their IDs and names, as well as whether they are currently available for use.
• list_boardsRetrieves a list of Jira boards based on specified criteria. Supports pagination via start_at and max_results. The response also includes convenience fields nextStartAt, hasNextPage, and nextPageToken to help iterate through pages.
• list_issue_commentsThis action fetches paginated comments associated with a specific Jira issue. It allows users to retrieve details such as the comment content and the authorship information.
• list_sprintsRetrieves and lists sprints associated with a specified Jira board. Users can filter results based on the state of the sprints, allowing for better management and visibility.
• move_issue_to_sprintThis action takes multiple issues and moves them to a specified sprint in Jira. It ensures that the issues are successfully added to the targeted sprint based on the provided sprint ID.
• search_for_issues_using_jql_getThis action retrieves Jira issues based on a specified JQL query. It allows for pagination as well as selection of specific fields to include in the result.
• search_for_issues_using_jql_postThis action performs the enhanced JQL issue search that supports eventual consistency and token-based pagination. Use it when you need stable results immediately after creating or updating issues, or when paginating large result sets. IMPORTANT: This action only works with Jira Cloud. For Jira Server or Data Center instances, use JIRA_SEARCH_FOR_ISSUES_USING_JQL_GET instead.
• search_issuesThis action performs advanced searches for Jira issues using either structured filters or raw JQL queries. It supports various search criteria including project, assignee, status, priority, and date ranges.
• transition_issueThis action transitions a specified Jira issue to a different status based on the selected workflow transition. It supports optional comments and assignee information. Note: Only fields configured on the transition screen can be set during the transition.
• delete_versionThis action deletes a specified version in Jira. It can also optionally move issues associated with the deleted version to another specified version.
• get_all_issue_type_schemesThis action retrieves a list of all issue type schemes from Jira. It allows for optional filtering based on specific IDs and supports pagination for large sets of data.
• get_all_statusesThis action retrieves issue statuses that are associated with workflows in Jira. It provides detailed information about each status including name, description, and category. Note: This may not include statuses from team-managed (Next-Gen) projects or unused statuses.
• get_commentThis action fetches a specific comment from a Jira issue by its ID. You can specify optional parameters to expand additional information in the response.
• get_issue_link_typesThis action retrieves all issue link types configured in the Jira instance. It provides a comprehensive list of the relationships available for issues in your project.
• get_issue_propertyThis action retrieves a specific property associated with a Jira issue using its ID or key. It allows users to access custom information stored in Jira properties.
• get_issue_resolutionsThis action fetches all issue resolutions available in Jira. It retrieves resolution types such as 'Done' or 'Fixed' that can be applied to issues.
• get_issue_type_schemeThis action retrieves a specific Jira issue type scheme based on its unique ID and includes all related issue types. It helps users obtain details about the organization of issue types within a scheme.
• get_issue_watchersThis action retrieves the list of users watching a specific Jira issue. It allows clients to understand who is interested in updates for that issue.
• get_issue_worklogsRetrieves all worklogs associated with a specific Jira issue. This includes filtering options such as start dates and pagination for large sets of worklogs.
• get_project_versionsThis action retrieves all versions associated with a specific Jira project. It can include additional properties for each version based on the request parameters.
• get_remote_issue_linksThis action retrieves remote issue links associated with a specified Jira issue. You can filter the links by providing an optional global ID for a specific link retrieval.
• get_votesThis action retrieves the voting information associated with a specific Jira issue. It provides details such as the total number of votes and whether the user has voted on that issue.
• get_worklogRetrieves the worklog entries for a specified Jira issue. This action provides detailed information on time spent by users on the issue, allowing for effective tracking and reporting of work activity.
• remove_watcher_from_issueThis action allows you to remove a specified user from the watchers list of a given issue. You need to provide the issue identification and the user's account ID for the operation to succeed.
• send_notification_for_issueThis action sends a customized email notification related to a specific Jira issue. It includes customizable fields for the subject, message content, and recipients, ensuring tailored communication for issue updates.