Skip to main content
Glama
leejersey

Hexo Blog MCP Server

by leejersey

deploy_blog

Build and publish your Hexo blog to GitHub Pages by executing clean, generate, and deploy commands to make your content live.

Instructions

构建并发布博客到 GitHub Pages(执行 hexo clean && hexo generate && hexo deploy)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The "deploy_blog" tool is registered and implemented directly in src/tools/hexo-tools.ts using the MCP server.tool method. It executes 'hexo clean', 'hexo generate', and 'hexo deploy' via the 'hexoCommand' utility.
    server.tool(
        "deploy_blog",
        "构建并发布博客到 GitHub Pages(执行 hexo clean && hexo generate && hexo deploy)",
        {},
        async () => {
            try {
                await hexoCommand("clean");
                const genOutput = await hexoCommand("generate");
                const deployOutput = await hexoCommand("deploy");
                return {
                    content: [
                        {
                            type: "text" as const,
                            text: `🎉 博客已成功发布到 GitHub Pages!\n\n网址: https://leejersey.github.io\n\n⚠️ GitHub Pages 需要 1~3 分钟刷新缓存。\n\n建议接下来执行 backup_source 备份源码。`,
                        },
                    ],
                };
            } catch (e: any) {
                return { content: [{ type: "text" as const, text: `部署失败: ${e.message}` }], isError: true };
            }
        }
    );
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. While it mentions the three hexo commands that will be executed, it doesn't disclose important behavioral traits like whether this is a destructive operation (likely yes, as it deploys to GitHub Pages), what prerequisites are needed (hexo setup, git configuration), or potential side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose ('构建并发布博客到 GitHub Pages') and provides essential technical detail in parentheses. Every element earns its place with zero wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given this is a deployment tool with no annotations and no output schema, the description provides adequate basic information about what the tool does but lacks important context about behavioral characteristics, prerequisites, and what happens after deployment. For a tool that likely modifies production content, more disclosure would be helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, focusing instead on the action being performed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('构建并发布博客' - build and publish blog) and the target resource ('到 GitHub Pages' - to GitHub Pages). It distinguishes from siblings like preview_blog, create_post, and quick_publish by specifying the full deployment pipeline with hexo commands.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by mentioning the specific hexo commands (clean, generate, deploy), suggesting this is for final deployment rather than testing. However, it doesn't explicitly state when NOT to use it or name alternatives like preview_blog for testing or quick_publish for simpler publishing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/leejersey/hexo-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server