com.clauxel.kirowebreleasebinder/kirowebreleasebinder-mcp
Remote MCP for Kiro release readiness, evidence binders, signoff, and CI approval receipts.
What can you do with com.clauxel.kirowebreleasebinder/kirowebreleasebinder-mcp?
- release policy rules
- Kiro project intake
- evidence checklist
- owner signoff
- tool-call receipts
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http kirowebreleasebinder-mcp 'https://kirowebreleasebinder.clauxel.com/mcp' --header 'Authorization: <Bearer token from the product website.>'{
"mcpServers": {
"kirowebreleasebinder-mcp": {
"type": "http",
"url": "https://kirowebreleasebinder.clauxel.com/mcp",
"headers": {
"Authorization": "<Bearer token from the product website.>"
}
}
}
}Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
Kiro Web Release Binder MCP
Turn Kiro-generated work into release evidence agents can trust.
Kiro Web Release Binder is a paid remote MCP release gate for Kiro projects, release goals, acceptance criteria, owner signoff, evidence binders, and CI-friendly approval receipts.
This is a public documentation project for Kiro Web Release Binder MCP. The structure is modeled after the public documentation pattern used by MiroFish: a short front door, a clear reading order, practical guides, reference pages, and public-safe architecture notes.
Start Here
- Website: https://kirowebreleasebinder.clauxel.com/?utm_source=github&utm_medium=documentation&utm_campaign=kirowebreleasebinder_public_docs&utm_content=readme_primary_home
- Pricing: https://kirowebreleasebinder.clauxel.com/pricing/?utm_source=github&utm_medium=documentation&utm_campaign=kirowebreleasebinder_public_docs&utm_content=readme_pricing
- Checkout: https://kirowebreleasebinder.clauxel.com/checkout/?utm_source=github&utm_medium=documentation&utm_campaign=kirowebreleasebinder_public_docs&utm_content=readme_checkout
- Support: support@aigeamy.com
Remote MCP
- Endpoint: https://kirowebreleasebinder.clauxel.com/mcp
- Server card: https://kirowebreleasebinder.clauxel.com/server-card.json
- Registry name:
com.clauxel.kirowebreleasebinder/kirowebreleasebinder-mcp - Tools:
check_kiro_release_readiness,collect_release_evidence,request_owner_signoff,issue_release_receipt,export_release_binder
Reading Order
Audience
AI IDE teams, delivery leads, release managers, and client-service studios.
Capabilities
- release policy rules
- Kiro project intake
- evidence checklist
- owner signoff
- tool-call receipts
Public-Safe Boundary
This repository does not contain production source code, credentials, payment configuration, Cloudflare configuration, customer records, private analytics, or local machine paths.
Frequently asked questions
What is com.clauxel.kirowebreleasebinder/kirowebreleasebinder-mcp?
Remote MCP for Kiro release readiness, evidence binders, signoff, and CI approval receipts.
How do I install com.clauxel.kirowebreleasebinder/kirowebreleasebinder-mcp?
It runs as a remote server. In Claude Code: claude mcp add --transport http kirowebreleasebinder-mcp 'https://kirowebreleasebinder.clauxel.com/mcp' --header 'Authorization: <Bearer token from the product website.>'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does com.clauxel.kirowebreleasebinder/kirowebreleasebinder-mcp need an API key?
Yes. It expects Authorization, which you set in its configuration.
Is com.clauxel.kirowebreleasebinder/kirowebreleasebinder-mcp open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains com.clauxel.kirowebreleasebinder/kirowebreleasebinder-mcp?
It is published by clauxel. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.