A
licenseA
qualityD
maintenanceMCP server for Velog blog platform enabling reading, searching, and writing articles via AI assistants.
12
5 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.117 npmMIT
- AlicenseNot gradedqualityCmaintenanceAn 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.4 npm61MIT
TDQS
A3.8/5.0
Scored across 23 tools
Disambiguation4/5
The toolset clearly separates read, write, publish, and rendering concerns, and descriptions explicitly distinguish draft vs published operations and global vs user-scoped listings. A few adjacent tools—notably velog_blog_stats vs velog_user_tags and the three render tools—could be misselected if descriptions aren't read carefully, but they are ultimately distinct.
Naming Consistency4/5
Most tools follow a clean verb_noun pattern under the velog_ prefix (list_posts, create_draft, publish_post, render_diagram). The consistency is slightly weakened by noun-phrase exceptions like velog_recent_posts, velog_blog_stats, velog_user_tags, and the bare velog_diagnose, but the naming remains predictable and readable.
Tool Count3/5
At 23 tools, the server is at the high end where tool count starts to feel heavy. Many tools are domain-specific and arguably earn their place, but the large set plus several adjacent utilities (rendering trio, stats/tags) makes it harder to navigate than a more scoped server.
Completeness3/5
The lifecycle is well covered for reading, creating, editing, publishing, and unpublishing posts and drafts, with useful extras like stats, export, and image rendering. However, there is no delete operation for posts or drafts, and no series or comment management, so some common tasks hit dead ends and require workarounds.
Maintenance
ActivityActive
ResponsivenessNo issues