Blog Helper MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_notesA | Liste l'ensemble des notes Markdown disponibles. |
| read_noteA | Lit et renvoie le contenu complet d'une note Markdown par son nom de fichier. |
| search_notesA | Renvoie la liste des noms de notes dont le contenu contient le terme recherché. |
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, reading, and searching notes. There is no overlap or ambiguity in their functions.
All tools follow the verb_noun pattern, but list_notes and search_notes use plural nouns while read_note uses singular, causing minor inconsistency.
Three tools is on the low end, but for a simple read-only blog notes server, it is borderline acceptable. More tools might be expected for full blog management.
The server only covers reading and searching operations. It lacks create, update, and delete capabilities, which are significant gaps for a blog helper.