Metalsmith Plugin MCP Server
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| plugin-scaffoldA | Scaffold a complete Metalsmith plugin (src/, test/, package.json, README.md, CLAUDE.md, GitHub workflows). Use only for NEW plugins in an empty directory — never against an existing project. Pass the user's exact plugin name (do not add a |
| validateB | Check an existing Metalsmith plugin against quality standards. |
| configsC | Generate configuration files following enhanced standards. |
| show-template | Display a recommended configuration template for Metalsmith plugins. |
| list-templatesA | List every template the server can hand back via get-template. Call this before guessing a template name. |
| get-template | Retrieve the exact content of a specific template file. Run list-templates first to see available names. Use these templates verbatim instead of improvising. |
| install-claude-mdA | Install a CLAUDE.md in an existing Metalsmith plugin. Smart-merges the MCP Server Integration section into any existing CLAUDE.md so user customizations survive. |
| diff-templateA | Diff a plugin against the current scaffold templates. Reports which files match, are missing, or have drifted (with unified diff snippets). Use to keep aging plugins in sync with the latest scaffold. |
| update-depsB | Update dependencies in Metalsmith plugin(s) using npm-check-updates. |
| audit-plugin | Run a comprehensive plugin audit (validation + lint + tests + coverage) and return a health report. |
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 7 tools
Each tool has a clearly distinct purpose: installing CLAUDE.md, scaffolding new plugins, listing templates, validating, generating configs, diffing against templates, and updating deps. No overlap or ambiguity.
All tool names follow a consistent hyphenated lowercase pattern (e.g., install-claude-md, plugin-scaffold). Verbs are clear and naming conventions are uniform throughout.
Seven tools is a well-scoped set for a plugin development server, covering scaffolding, validation, configuration, dependency updates, and template management without being overwhelming or sparse.
The tool set covers the main plugin creation and maintenance lifecycle: scaffold, validate, diff, update deps, install CLAUDE.md. A minor gap is the lack of a tool for running tests or building, but core workflows are well-supported.