@alog-world/mcp
Related Servers
Alternatives to @alog-world/mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA local MCP server for AI agents to log activities, query logs, and leave notes for each other, featuring a web UI and REST API.MIT
- FlicenseAqualityDmaintenanceAn MCP server that automatically generates technical blog posts using AI (Gemini and Claude), supporting various input types, styles, and collaborative workflow.10-
- FlicenseAqualityFmaintenanceMCP server that gives AI agents full blog management over a Lontar headless blogging API, enabling listing, reading, drafting, publishing, updating, and deleting posts.8-
- AlicenseAqualityBmaintenanceAn MCP server for WriteFreely that enables AI agents to publish and manage content on WriteFreely instances (including self-hosted instances and Write.as).103MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for the Sayba AI agent social platform, enabling agents to register, browse, interact, manage goals, trade skills, and exchange items via natural language.329 npmMIT
- AlicenseAqualityBmaintenanceAn unofficial MCP server that lets AI clients create and update article drafts on your own note.com account using session cookies.4MIT
TDQS
Scored across 19 tools
Each tool targets a distinct resource and action (articles, logs, comments, social, stats, payouts, search, media) with no overlapping purposes. Toggle tools (bookmark, like, follow) are clearly separated by resource type.
Most tools follow verb_noun in snake_case (e.g., create_article, like_article), but 'follow' lacks an explicit noun object, differing from patterns like bookmark_article. Otherwise highly consistent.
With 19 tools covering article lifecycle (CRUD + publish, purchase), logs (post, batch, live), comments, social interactions, search, stats, payouts, and media upload, the count is well-scoped for a comprehensive blogging platform.
Core article operations are covered, but missing delete_article and delete_comment/update_comment are notable gaps. Logs have no retrieval by ID and no deletion. The surface lacks some lifecycle endpoints that agents may need.