🌈 Iris MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Iris MCP Server?

Iris MCP Server is a Model Context Protocol server designed to automatically generate tag-based release notes from a Git repository. It analyzes the differences between tags and produces structured release notes in the .iris directory.

How to use Iris MCP Server?

To use Iris MCP Server, install it via npm and call the generate_release_note method with the required parameters such as start and end tags, title, features, improvements, bug fixes, and breaking changes.

Key features of Iris MCP Server?

  • Automatic detection of differences between tags
  • Customizable release note templates
  • Categorization of new features, improvements, and bug fixes
  • Output in Markdown format
  • Automatic saving to the .iris folder

Use cases of Iris MCP Server?

  1. Generating release notes for software projects.
  2. Keeping track of changes between different versions of a project.
  3. Automating the documentation process for development teams.

FAQ from Iris MCP Server?

  • Can Iris MCP Server generate release notes for any Git repository?

Yes! As long as the repository uses tags, Iris MCP Server can generate release notes.

  • Is Iris MCP Server free to use?

Yes! Iris MCP Server is open-source and free to use.

  • How can I contribute to Iris MCP Server?

You can contribute by forking the repository, making changes, and submitting a pull request.

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

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago