velog-mcp

An MCP server for Velog, the Korean developer blogging platform. Read your blog, draft posts, publish them, and back everything up — from Claude or any MCP client.

한국어 문서 →

---

Why another one?

Two Velog MCP servers already exist. This one differs in three ways.

1. Publishing is a permission, not a default. Out of the box the server can create drafts and publish privately. Public publishing requires you to set an environment variable. The model cannot flip that switch — only you can, in your MCP config.

2. Every quirk is measured, not assumed. Velog's GraphQL API is undocumented. This repo records what it actually does, verified against velog-io/velog source and live calls. Six server-side quirks are written up in docs/api-reference.md — including one that silently returns an empty list, and one that can turn your published posts private.

3. Two runtime dependencies. @modelcontextprotocol/sdk and zod. HTTP, test runner, and TypeScript execution all come from Node 24 itself.

---

Install

Requires Node.js 24 or newer.

As a Claude Code plugin (recommended)

/plugin marketplace add milcho0604/velog-mcp
/plugin install velog@milcho

Installation asks for four values. Leave them all blank and it still installs, running read-only.

Prompt	If left blank
Velog refresh token	Read-only (browse, search, stats still work)
Allow public publishing	Drafts and private publishing only
Allow profile edits	Profile tools stay off
Chrome path	Found automatically in standard locations

The token goes into the macOS Keychain, not into a settings file in plaintext. Only values declared sensitive: true reach the Keychain, and a test enforces that declaration (P7).

Change values later with /plugin manage.

As a plain MCP server

Published on npm, so nothing to clone — your MCP client runs it via npx. See Configure for the config block and the client-support note.

claude mcp add velog -e VELOG_REFRESH_TOKEN=your_refresh_token \
  -- npx -y @milcho0604/[email protected]

The token stays in your client's config file here. The plugin route above puts it in the Keychain instead.

From source

git clone https://github.com/milcho0604/velog-mcp.git
cd velog-mcp
npm install && npm run build

Configure

Add this to your MCP client config (claude_desktop_config.json, .mcp.json, …):

{
  "mcpServers": {
    "velog": {
      "command": "npx",
      "args": ["-y", "@milcho0604/[email protected]"],
      "env": {
        "VELOG_REFRESH_TOKEN": "your_refresh_token"
      }
    }
  }
}

With the Claude Code CLI:

claude mcp add velog -e VELOG_REFRESH_TOKEN=your_refresh_token \
  -- npx -y @milcho0604/[email protected]

To run a local checkout instead, swap the command for node /absolute/path/to/velog-mcp/dist/index.js.

Which clients can run this? This is a stdio server: the client starts it as a local process. That works in Claude Code, Claude Desktop, Cursor, and other clients that run MCP servers locally. It does not work in the claude.ai or ChatGPT web apps — both accept only remote MCP servers reachable over HTTP, since the connection originates from their servers rather than your machine. Using it there would mean hosting it publicly and handing your Velog token to that deployment, which defeats the point of keeping the token on your own machine.

Getting your token