doc-template-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOC_TEMPLATE_PAGES_REPO | No | GitHub repository in owner/repo format for publishing rendered documents to GitHub Pages (optional). |
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 |
|---|---|
| list_themesB | 쓸 수 있는 테마와 대표 색. id를 render_document의 theme에 넣는다. 'mono'는 흑백, 'one:#HEX' 또는 'one:t3'는 한 가지 색 모드. |
| get_starterB | 시작 문서(Markdown)와 문법. kind: plan(기획) | research(리서치). 머리말의 theme 한 줄로 색을 고른다. |
| render_documentB | 옵시디언 Markdown을 문서 템플릿 HTML(한 파일)로 만든다. theme을 비우면 머리말의 theme(없으면 t1). output_path를 비우면 ~/Documents/doc-template/<제목>-<날짜>.html 에 저장한다. 결과에 파일 경로와 대비 검사 결과가 있다. |
| render_fileB | Markdown(.md) 파일을 읽어 같은 폴더에 같은 이름의 .html로 렌더한다. 같은 이름의 HTML이 있으면 overwrite=True일 때만 덮어쓴다. |
| publish_documentA | 렌더한 HTML을 GitHub Pages 저장소(환경변수 DOC_TEMPLATE_PAGES_REPO)에 올리고 공개 URL을 돌려준다. 외부 공개이므로 사용자 확인 뒤에만 부른다. |
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 5 tools
Each tool maps to a distinct stage in the template workflow: theme discovery, starter retrieval, rendering from Markdown text, rendering from a file, and publishing. Despite render_document and render_file both producing HTML, their input modes are clearly separated and the names reinforce the difference.
All five tool names follow the same snake_case verb_noun pattern: list_themes, get_starter, render_document, render_file, publish_document. The verbs match their actions consistently and no mixed naming conventions appear.
Five tools is a well-scoped size for this server's purpose. Each tool covers a necessary step without redundancy, and there is no bloat from dozens of near-duplicate operations.
The tool surface covers the full workflow: discovering themes, obtaining a starter template, rendering Markdown from text or a file, and publishing to GitHub Pages. There are no obvious dead ends or missing core operations within the stated domain.