A
licenseA
qualityA
maintenanceAn MCP server for Velog, enabling reading, drafting, publishing, and backing up blog posts from Claude or any MCP client with permission controls.
23
492 npm
3
MIT
velog-mcp
Related Servers
Alternatives to velog-mcp
No user-submitted related servers found.
Related Servers
- 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-
- AlicenseAqualityDmaintenanceMCP server for Alog, an AI × Human blog platform. Enables AI agents to post logs, create and publish articles, search content, and interact socially on alog.world.194 npm1MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to read, search, and write Velog blog posts. Supports post management, trending, and series/profile retrieval.107 npm7MIT
- FlicenseAqualityDmaintenanceAn MCP server that automatically generates technical blog posts using AI (Gemini and Claude), supporting various input types, styles, and collaborative workflow.10-
- AlicenseBqualityCmaintenanceAutomates writing and publishing posts to velog.io via MCP, including login and session management.57 npmMIT
TDQS
A3.6/5.0
Scored across 12 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: authentication, reading posts (list vs. individual vs. trending vs. search), user profile vs. series, and CRUD operations for posts and profile. Even write_post and publish_local_markdown differ in input method (manual vs. file-based).
Naming Consistency4/5
Tool names generally follow a verb_noun pattern in snake_case, but there is a mix of 'get_' and direct verbs like 'read' and 'search'. 'login' lacks an object, and 'publish_local_markdown' is a compound phrase, yet the pattern is still predictable and readable.
Tool Count5/5
With 12 tools, the set is well-scoped for a blogging platform. It covers authentication, public browsing (posts, profiles, series, search, trending), and authenticated content management (write, edit, delete, profile update, markdown publishing) without unnecessary bloat.
Completeness4/5
Core CRUD lifecycle for posts is fully covered, and user/profile/series retrieval is present. Minor gaps include no series management (create/update/delete), no comment interaction, and no explicit logout, but these are not essential for the main blogging workflow.
Maintenance
ActivityInactive
ResponsivenessNo issues