mcp-blog
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BLOG_API_KEY | Yes | API key for HMAC authentication | |
| BLOG_API_ENDPOINT | Yes | Base URL of the blog API (e.g. https://dxbqlfvrescw1.cloudfront.net/api) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| blog_preview_postA | AI によるフロントマター補完・本文構造補正を実行してプレビュー結果を返す。publish 前に必ず呼ぶこと。 |
| blog_publish_postB | AI 補正済みの markdown と frontmatter を S3 に保存し、GitHub Actions ビルドを発火させて公開する。 |
| blog_list_postsB | ブログ記事の一覧を取得する。published フィルタと件数上限を指定可能。 |
| blog_get_postA | 指定したスラグの記事を S3 から読み出し、Markdown 本体と frontmatter を返す。編集ワークフロー (取得→修正→blog_publish_post で上書き) で使う。 |
| blog_delete_postA | 指定したスラグの記事を S3 から削除し、GitHub Actions ビルドを発火させる。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct action: delete, get, list, preview, and publish. No overlaps in purpose.
All tools follow the consistent blog_verb_noun pattern with snake_case (e.g., blog_delete_post, blog_list_posts).
Five tools are appropriately scoped for a blog server, covering essential operations without being too few or too many.
The set covers the full lifecycle: list, get, preview, publish, and delete. No obvious missing operations for a simple blog workflow.