Emlog 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_articleC | Create a new blog article |
| update_articleB | Update an existing blog article. If the article is currently a draft and no draft parameter is specified, it will remain as a draft. |
| get_articleC | Get a specific article by ID |
| search_articlesC | Search articles by keyword, tag, or category |
| like_articleC | Like an article |
| add_commentC | Add a comment to an article |
| get_commentsC | Get comments for an article (with pagination support) |
| create_noteC | Create a new micro-note |
| upload_fileC | Upload a file (image, document, etc.) |
| get_user_infoB | Get current user information |
| get_draft_listC | Get list of draft articles |
| get_draft_detailC | Get details of a specific draft |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| articles | All articles from the Emlog blog |
| categories | All categories from the Emlog blog |
| comments | Comments for a specific article. Use emlog://comments/{article_id} to get comments for a specific article. |
| notes | All notes from the Emlog blog |
| users | All users from the Emlog blog |
| drafts | All drafts from the Emlog blog |
TDQS
Scored across 12 tools
Most tools have clearly distinct purposes targeting specific resources like articles, comments, drafts, and files, with minimal overlap. However, 'create_article' and 'create_note' might cause slight confusion if notes are a type of article, but their descriptions help differentiate them as separate entities.
All tools follow a consistent verb_noun naming pattern (e.g., add_comment, create_article, get_draft_list), using snake_case throughout. This predictability makes it easy for agents to understand and select tools based on their actions and targets.
With 12 tools, this server is well-scoped for a blog management system, covering core operations like article CRUD, commenting, drafts, and file uploads. Each tool serves a distinct function without unnecessary bloat, fitting typical workflows for content creation and management.
The toolset provides strong coverage for blog management, including CRUD for articles, comments, drafts, and user info, with search and like functionality. Minor gaps include no update/delete for comments or notes, and no direct management of tags/categories, but agents can work around these with available tools.