blog-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BLOG_FEED_URL | No | Override the feed URL for development. HTTPS is required, except for HTTP on localhost. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_articlesA | List published articles from Rasmus Olsson’s blog, newest first. Returns metadata and links; use get_article to read a post. Optional case-insensitive exact tag filter. |
| search_articlesA | Search published blog articles by keywords in titles, tags and content. All words must match; title and tag matches rank higher. Returns summaries and links, not full articles. |
| get_articleA | Read the full Markdown content and canonical link for an article. Supply the slug returned by list_articles or search_articles. |
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 3 tools
Each tool serves a distinct purpose: listing all articles, searching by keywords, and retrieving full content by slug. The descriptions clearly differentiate list from search, and both reference get_article for full reading, so an agent should not confuse them.
All tool names follow a consistent verb_noun pattern: list_articles, search_articles, get_article. The pattern is predictable and makes the action and resource clear for each tool.
Three tools is well-scoped for a read-only blog server. List, search, and get cover the essential discovery and retrieval workflow without unnecessary bloat or missing core functionality.
For a blog reading domain, the lifecycle is complete: discover articles via list or search, then read full content via get. There are no obvious gaps like missing tag browsing or full-text retrieval, as the existing tools handle these through filters and links.