A
licenseA
qualityD
maintenanceMCP server for Velog blog platform enabling reading, searching, and writing articles via AI assistants.
12
21 npm
MIT
velog-mcp
by milcho0604
Related Servers
Alternatives to velog-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceAn MCP server that automatically generates technical blog posts using AI (Gemini and Claude), supporting various input types, styles, and collaborative workflow.10-
- FlicenseBqualityDmaintenanceMCP server that exposes Tistory blog posting functionality, enabling AI agents to write, upload, and publish posts (public/private) via Playwright and Tistory API.9-
- FlicenseAqualityDmaintenanceA custom MCP server for interacting with Google Blogger blogs. It provides tools to list, create, edit, delete, and publish blog posts through Claude Code or Claude Desktop.9-
- AlicenseAqualityBmaintenanceMCP server for Hashnode GraphQL API to create drafts, publish posts, and manage your blog via Claude.1119 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables Claude Desktop to read and write an Obsidian vault hosted on a VPS, using SSH or HTTP transport with OAuth authentication.15 npm62MIT
TDQS
A4/5.0
Scored across 23 tools
Disambiguation4/5
Most tools are clearly distinct (e.g., publish vs. draft, render vs. upload). However, velog_publish_post and velog_publish_draft overlap in purpose (both publish), and velog_update_draft vs. velog_update_post have different behaviors but similar names. The render tools are well-separated by diagram type.
Naming Consistency5/5
All tools follow a consistent 'velog_' prefix with verb_noun pattern (e.g., velog_create_draft, velog_list_posts, velog_publish_draft). There are no mixed conventions or vague verbs, making the set highly predictable.
Tool Count4/5
At 25 tools, the set is slightly above the ideal range but justified for a comprehensive Velog client. Each tool serves a distinct domain function (read, write, publish, render, stats), and none feel redundant. A few could be merged (e.g., publish_post/publish_draft) but overall scoped well.
Completeness4/5
The set covers a full lifecycle: read (list/get/search), write (create/update draft, publish, unpublish), modify (update_post), and utilities (stats, export, render). Minor gaps include lack of direct post deletion (only unpublish) and no tag management, but agents can work around these.
Maintenance
ActivityActive
ResponsivenessNo issues