release-announcer-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@release-announcer-mcpBuild the announcement kit for h-kazuki-pixel/jp-dates-mcp-server"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
release-announcer-mcp
An MCP server that turns a GitHub repository into ready-to-review release announcements — and checks that the repo is actually ready to ship.
Point it at any public repo and ask Claude for an "announcement kit". You get drafts for:
X/Twitter post (short, link included, in two languages)
Reddit post (understated "I built a thing" tone — draft only, never auto-posted)
GitHub profile README table row
awesome-list entry + pull request text
MCP directory listing (short/long description + tags)
Plus a publish-readiness checklist: LICENSE, README quality, Release, Topics, About description, .gitignore — each with a concrete fix suggestion when missing.
No API key required. Works with any public GitHub repository.
Why
If you ship open-source tools on a regular cadence, the release itself is the easy part. The repetitive part is everything after: writing the announcement, adapting it per platform, updating your profile, submitting to directories. This server gathers the facts (README, release notes, metadata) and hands your LLM a strict writing brief, so every announcement is accurate, consistent, and takes minutes instead of an hour.
By design, this tool generates drafts only. It never posts anywhere. You review, then you post.
Related MCP server: GitHub PR Issue Analyser
Tools
Tool | What it does |
| Fetch repo metadata, latest release, README, and root files |
| Run the pre-publication checklist (pass/warn/fail with fixes) |
| Build a complete writing brief for any subset of announcement targets |
Setup
Requires Node.js 18+.
git clone https://github.com/h-kazuki-pixel/release-announcer-mcp.git
cd release-announcer-mcp
npm install
npm run buildAdd to your Claude Desktop config (claude_desktop_config.json):
{
"mcpServers": {
"release-announcer": {
"command": "node",
"args": ["/absolute/path/to/release-announcer-mcp/dist/index.js"]
}
}
}Optional: set a GITHUB_TOKEN environment variable to raise GitHub's API rate limit (not required for normal use).
Usage
Just ask Claude, for example:
"Build the announcement kit for h-kazuki-pixel/jp-dates-mcp-server"
"Is my-org/my-repo ready to publish? Run the checklist."
"Draft only the X post and the awesome-list entry for owner/repo."
Example output (checklist)
# Publish readiness: owner/repo
**6/8 checks passed**
- ✅ LICENSE file — MIT License detected.
- ✅ README — README found.
- ⚠️ README: setup instructions — No obvious setup section. Add installation steps.
- ✅ README: usage examples — Usage/example content detected.
- ❌ GitHub Release — No release found. Create one: Releases → 'Draft a new release' → tag v1.0.0.
- ✅ Topics (discovery tags) — 4 topics set.
- ✅ About description — Description set.
- ✅ .gitignore — .gitignore found.Development
npm run build # compile TypeScript
npm test # run integration tests (uses a local mock of the GitHub API)License
MIT
日本語
GitHubリポジトリを指定するだけで、リリース告知に必要な文章一式のドラフトと、公開前チェックリストを生成するMCPサーバーです。
できること
X(Twitter)告知文(2言語・リンク付き・短文)
Reddit投稿の下書き(宣伝色を抑えた文体。自動投稿は一切しません)
GitHubプロフィールREADMEの作品表の行
awesomeリスト登録用のエントリ+PR文
MCPディレクトリ(mcp.so等)登録用の説明文+タグ案
公開前チェックリスト: LICENSE / READMEの充実度 / Release作成 / Topics / About欄 / .gitignore を自動判定し、不足があれば直し方を提示
APIキー不要。公開リポジトリならどれでも使えます。
セットアップ
Node.js 18以上が必要です。
git clone https://github.com/h-kazuki-pixel/release-announcer-mcp.git
cd release-announcer-mcp
npm install
npm run buildClaude Desktopの設定ファイル(claude_desktop_config.json)に追加:
{
"mcpServers": {
"release-announcer": {
"command": "node",
"args": ["/absolute/path/to/release-announcer-mcp/dist/index.js"]
}
}
}使い方
Claudeにこう頼むだけです:
「h-kazuki-pixel/jp-dates-mcp-server の告知セットを作って」
「owner/repo は公開準備できてる?チェックリストを実行して」
設計方針
このツールが生成するのは下書きのみです。SNSへの自動投稿機能は意図的に持たせていません。最終確認と投稿は必ず人間が行います。
ライセンス
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/h-kazuki-pixel/release-announcer-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server