MCP.so
ログイン

Jira Prompts MCP Server

@ceshine

基本情報

カテゴリ

バージョン管理

ライセンス

MIT license

トランスポート

stdio

作者

ceshine

Jira Prompts MCP Server について

An MCP server that offers several commands for generating prompts or contexts from Jira content

Jira Prompts MCP Server の設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

Jira Prompts MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Jira Prompts MCP Server?

Jira Prompts MCP Server is a Model Context Protocol (MCP) server that provides prompts for retrieving context from Jira content. It focuses on generating prompts rather than tools, making it especially useful for AI assistants like Zed that support only MCP prompts.

How to use Jira Prompts MCP Server?

Install by cloning the repository and running uv sync --frozen. Configure it as an MCP server in your editor (e.g., Zed) by adding a context server definition to settings.json that runs jira-prompts-mcp-server with three arguments: your Jira base URL, your Jira username, and a Jira API token. Once configured, use commands like /jira-issue-brief <issue-key> or /jira-issue-full <issue-key> to retrieve issue information.

Key features of Jira Prompts MCP Server

  • Uses the pycontribs/jira library for Jira API interactions
  • Provides two prompt commands: jira-issue-brief and jira-issue-full
  • Returns core fields, comments, linked issues, and subtasks
  • Designed to work with editors that only support MCP prompts
  • Different from mcp-atlassian: focuses on prompts, not tools

Use cases of Jira Prompts MCP Server

  • Quickly retrieve a Jira issue's key details in an AI assistant
  • Get a full context including comments and linked issues
  • Integrate Jira issue data into an editing workflow that supports MCP prompts

よくある質問

1

What are the runtime dependencies?

Python with the project’s dependencies installed via `uv sync`.

2

Where does the issue data come from?

From your Jira instance, accessed via the Jira API using the provided base URL, username, and API token.

3

What transports or authentication does it support?

Authentication uses a Jira API token passed as a command-line argument. The server listens as an MCP server over stdio.

コメント

「バージョン管理」の他のコンテンツ