velog-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VELOG_ACCESS_TOKEN | No | Velog access token for authentication. | |
| VELOG_REFRESH_TOKEN | No | Velog refresh token 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_postA | Create a new post on Velog (requires authentication) |
| edit_postB | Edit an existing post on Velog (requires authentication) |
| delete_postB | Delete a post on Velog (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 10 tools
Each tool serves a distinct purpose: authentication, listing user posts, reading a single post, trending, profile, series, search, and post CRUD operations. No two tools have overlapping responsibilities.
All tool names use consistent snake_case with a verb-first pattern (get_*, read_*, write_*, edit_*, delete_*, login, search_*). This creates a predictable and uniform naming convention.
With 10 tools, the set is well-scoped for a blogging platform API. Each tool covers a core action, and the count is neither too sparse nor overwhelming.
The tool set covers the full lifecycle of posts (create, read, update, delete), user and series listing, search, and trending. Minor gaps like commenting or series management exist, but they are not essential to the primary use case.