hugo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_system_infoC | Get system information |
| check_hugo_installationA | Check if Hugo is installed and get its version |
| check_go_installationA | Check if Go is installed and get its version |
| check_git_installationA | Check if Git is installed and get its configuration |
| create_siteC | Create a new Hugo site |
| create_postC | Create a new Hugo post |
| list_contentC | List content in the Hugo site |
| start_previewC | Start Hugo local server for preview |
| stop_previewB | Stop a running Hugo preview server |
| build_siteC | Build the Hugo site for production |
| list_themesA | List available Hugo themes from the official Hugo themes website |
| install_themeD | Install a Hugo theme |
| update_themeC | Update an installed Hugo theme |
| get_theme_detailsC | Get detailed information about a specific Hugo theme |
| deploy_siteC | Deploy a Hugo site to various platforms |
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 15 tools
Each tool has a clearly distinct purpose: installation checks, site/content creation, preview management, building, theme operations, and deployment. No two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., install_theme, create_site, list_themes). No mixing of conventions or vague verbs.
15 tools cover the core Hugo workflow—setup, content creation, preview, build, theme management, and deploy—without being excessive. Each tool earns its place.
The tool surface covers the main lifecycle, but lacks update/delete operations for content and themes. A minor gap given typical agent needs.