Jira MCP Server

Created By
jitendrajawarea year ago
A Model Context Protocol (MCP) server that allows Claude and other AI assistants to create and manage Jira issues.
Overview

What is Jira MCP Server?

Jira MCP Server is a Model Context Protocol (MCP) server that enables AI assistants like Claude to create and manage Jira issues seamlessly.

How to use Jira MCP Server?

To use the Jira MCP Server, clone the repository, install the dependencies, configure the necessary environment variables, and run the server. Once set up, AI assistants can interact with Jira through the MCP.

Key features of Jira MCP Server?

  • Allows AI assistants to create and manage Jira issues.
  • Supports configuration of allowed Jira projects for issue creation.
  • Provides tools for creating Jira issues and retrieving project information.

Use cases of Jira MCP Server?

  1. Automating issue creation in Jira through AI commands.
  2. Integrating Jira with AI assistants for project management.
  3. Streamlining workflows by allowing AI to manage Jira tasks.

FAQ from Jira MCP Server?

  • Can I use this server with any AI assistant?

Yes! The server is designed to work with any AI assistant that supports the Model Context Protocol.

  • What permissions do I need for the Jira API token?

The user associated with the API token must have read access to the projects and create issue permissions for the projects specified in the configuration.

  • How do I troubleshoot permission errors?

Ensure your Jira user has the necessary permissions and that the project keys in your configuration are correct.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jitendrajaware
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago