Skip to main content
Glama

🌈 Iris MCP Server

📝 Overview

Iris MCP Server is a Model Context Protocol server for automatic generation of tag-based release notes for Git repositories. It parses diffs between tags and generates structured release notes in the .iris directory.

Related MCP server: MCP Server

✨ Features

  • 🏷️ Automatically detect differences between tags

  • 📊 Customizable release note templates

  • 🗂️ New features, improvements, bug fixes, etc.

  • 📄 Markdown format output

  • 📁 Auto-save to .iris folder

🚀 Installation

npm install iris-mcp-server

💡 How to use

Generate release notes

const result = await mcpClient.useTool('iris-mcp-server', 'generate_release_note', {
  startTag: 'v1.0.0',
  endTag: 'v1.1.0',
  title: 'Version 1.1.0 リリース',
  features: [
    '新しいダッシュボード機能の追加',
    'ユーザー管理システムの実装'
  ],
  improvements: [
    'パフォーマンスの最適化',
    'UIの改善'
  ],
  bugfixes: [
    'ログイン時のエラー修正',
    'データ同期の問題を解決'
  ],
  breaking: [
    'APIエンドポイントの変更',
    '設定ファイルのフォーマット更新'
  ]
});

📄 Output example

# Version 1.1.0 リリース

リリース日: 2024-01-20

## 💥 破壊的変更

- APIエンドポイントの変更
- 設定ファイルのフォーマット更新

## ✨ 新機能

- 新しいダッシュボード機能の追加
- ユーザー管理システムの実装

## 🔧 改善項目

- パフォーマンスの最適化
- UIの改善

## 🐛 バグ修正

- ログイン時のエラー修正
- データ同期の問題を解決

## 📝 変更されたファイル

- `src/dashboard/index.ts`
- `src/users/management.ts`
- `config/settings.json`

🛠️ Development

Build

npm run build

Development Mode

npm run watch

🤝 Contributions

Pull requests and issues are welcome! You can contribute by following these steps:

  1. Fork this repository

  2. Create a new branch ( git checkout -b feature/amazing-feature )

  3. Commit the changes ( git commit -m '✨ Add amazing feature' )

  4. Push the branch ( git push origin feature/amazing-feature )

  5. Create a pull request

📜 License

MIT

👥 Author

Available Tools

1 tool
generate_release_noteB

タグ間の差分からリリースノートを生成します

Inputs: endTag (required), startTag (required), breaking, bugfixes, +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as generating release notes from tag differences, making it impossible for an agent to confuse it with another tool.

    Naming Consistency5/5

    Since there is only a single tool, naming consistency is inherently perfect. The tool name 'generate_release_note' follows a clear verb_noun pattern, and there are no other tools to create inconsistency with.

    Tool Count2/5

    A single tool is too few for a server's purpose, as it severely limits functionality and suggests an incomplete or overly narrow scope. This makes the server feel thin and impractical for most agent workflows, as it lacks the breadth needed for typical operations in its domain.

    Completeness2/5

    The server is severely incomplete for any reasonable domain involving release notes. While the tool can generate notes, there are obvious gaps such as creating, updating, deleting, or listing release notes, and no coverage for related operations like managing tags or integrating with version control systems, which will cause agent failures in real-world scenarios.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A Node.js/TypeScript server implementing the Model Context Protocol that provides integrations with GitHub and Notion, allowing automated workflow between these platforms via API endpoints.
      ISC
    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that provides Git version control operations as structured tools for AI coding agents. It enables LLMs to programmatically manage repositories through actions like committing changes, rolling back code, and comparing diffs.
      10
      Apache 2.0