Velog MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VELOG_ALLOW_PUBLIC | No | Set to 1 to enable public publishing. Public publishing is disabled by default unless this environment variable is explicitly set. | 0 |
| VELOG_REFRESH_TOKEN | No | Refresh token for automation environments. This takes precedence over the encrypted local token store, but the server does not save it locally. |
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 |
|---|---|
| velog_list_postsC | List public posts for one Velog username. |
| velog_get_postB | Read one public Velog post, including its Markdown body. |
| velog_search_postsB | Search public Velog posts by keyword, optionally within one username. |
| velog_sync_local_indexA | Sync all public posts for one Velog username into the local keyword index. |
| velog_search_local_indexC | Search posts previously synced into the local keyword index. |
| velog_export_local_postsB | Export posts already synced into the local index as Markdown files without making a network request. |
| velog_format_markdownC | Audit Velog Markdown for structure, accessibility, and secret-like content before saving. |
| velog_create_draftB | Preview or create a private Velog draft. Writing requires confirm=true. |
| velog_publish_postB | Preview or publish a private Velog post. Writing requires confirm=true. |
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 9 tools
Most tools have clearly distinct purposes: public retrieval, local-index operations, markdown auditing, and draft/publish actions are separated. The closest overlaps are velog_search_posts vs. velog_search_local_index and velog_list_posts vs. velog_sync_local_index, but descriptions make the network/local distinction clear.
All tools use a consistent velog_ prefix followed by snake_case verb_noun naming. The pattern is predictable throughout the set, including read, search, sync, export, create, and publish operations.
Nine tools is well-scoped for a Velog MCP server covering public reading, local indexing, markdown validation, and draft/publish workflows. Each tool appears to earn its place without excessive fragmentation.
The set covers the core lifecycle: listing/reading/searching public posts, syncing and searching a local index, exporting synced posts, validating markdown, and creating/publishing drafts. Minor gaps remain around editing or deleting existing posts and managing private/draft listings, but the main workflows are supported.