velog_mcp
Related Servers
Alternatives to velog_mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables creating draft posts and listing published posts on abelcastro.dev directly from Claude.-
- FlicenseNot gradedqualityDmaintenanceMulti-platform blog publishing tool that enables users to save, schedule, and publish SEO-optimized articles to platforms like websites, LinkedIn, Twitter, and Substack directly from Claude.-
- AlicenseAqualityCmaintenanceEnables AI assistants to read, search, and write Velog blog posts. Supports post management, trending, and series/profile retrieval.1014 npm7MIT
- AlicenseAqualityAmaintenanceEnables publishing local Markdown files to Velog with idempotent updates. Supports login, post management, and series operations through natural language.10MIT
- AlicenseBqualityCmaintenanceAutomates writing and publishing posts to velog.io via MCP, including login and session management.514 npmMIT
- AlicenseBqualityCmaintenanceConnects Claude to WordPress sites through the REST API, enabling AI-assisted content creation, publishing, media management, user administration, and site maintenance tasks through natural language.4722 npm23MIT
TDQS
Scored across 6 tools
Every tool has a clearly distinct purpose with no ambiguity: delete, draft, get, list, publish, and update are all specific actions targeting Velog posts. The descriptions reinforce this by specifying when to use each tool (e.g., velog_publish_post after velog_draft_post).
All tools follow a consistent verb_noun pattern with 'velog_' prefix and snake_case: velog_delete_post, velog_draft_post, velog_get_post, velog_list_posts, velog_publish_post, velog_update_post. There are no deviations in naming style.
With 6 tools, this server is well-scoped for managing Velog posts. Each tool earns its place by covering essential CRUD and lifecycle operations (drafting and publishing), avoiding both bloat and thin coverage.
The tool set provides complete CRUD and lifecycle coverage for Velog posts: create (via draft and publish), read (get and list), update, and delete. There are no obvious gaps, and the workflow from drafting to publishing is explicitly supported.