velog-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VELOG_ACCESS_TOKEN | No | Your Velog access token (optional, used for authentication) | |
| VELOG_REFRESH_TOKEN | No | Your Velog refresh token (optional, used for authentication) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| loginB | Open a browser to log in to Velog and save authentication tokens |
| get_user_postsA | Get a list of posts by a Velog user |
| read_postA | Read a specific Velog post with full content, comments, and metadata |
| get_trending_postsC | Get trending posts from Velog |
| get_user_profileA | Get a Velog user's profile information |
| get_series_listB | Get a user's series list on Velog |
| search_postsA | Search for posts on Velog by keyword |
| write_postB | Create a new post on Velog (requires authentication) |
| edit_postC | Edit an existing post on Velog (requires authentication) |
| delete_postB | Delete a post on Velog (requires authentication) |
| update_profileA | Update the current user's profile (requires authentication) |
| publish_local_markdownC | Publish a local markdown file as a Velog post (requires authentication) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
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).
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.
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.
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.