museav-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MUSEAV_BIN | No | Path to the museav executable, required only when museav is not in the global PATH |
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 |
|---|---|
| writing_lintA | 静态扫描 Markdown 文本或文件,机械拦截假人过渡词(总的来说/毋庸置疑)、机械排比(不仅...更是...)、高中作文腔(犹如一幅画卷/宛如晨曦)与空洞正能量结尾。返回违规行号与修改建议。零外部依赖。 |
| writing_rubricA | 获取指定平台(小红书 / Twitter / Reddit / 掘金)的说说型发帖扣分清单(Rubric)与致命反模式。发布前逐条对照,每项扣 20 分,低于 80 分不得发布。 |
| writing_composeB | 基于 5D 原子表达组合矩阵(谁×在哪×为什么说×口吻),生成高信噪比、零 AI 假人味的提示词约束或内容骨架。 |
| groups_listA | 列出这个 MCP 的全部能力分组:哪些已启用(各几个工具)、哪些因为没装 CLI 而没启用、以及每个分组对应哪个开源项目和怎么装。工具列表里没有的能力,先查这里再让用户装。 |
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 4 tools
The three writing tools split along a clear workflow: lint detects mechanical violations, rubric is a static reference of platform scoring rules, and compose generates prompt constraints. Lint vs. rubric could be momentarily confused since both are 'check my text against rules', but the descriptions frame one as automated scanning with line numbers and the other as a manual checklist. groups_list is unmistakably a meta/introspection tool.
All lowercase snake_case with an action-oriented second token, so naming is readable and predictable. The three writing_* tools share a clean domain prefix, while groups_list is a noun_verb outlier that breaks the domain_action pattern.
Four tools is lean but defensible for a focused writing-quality server: one generates, one checks, one provides reference criteria, plus a discovery tool. Nothing is redundant, though the surface is thin enough that the single meta tool feels like it belongs to a larger, uninstalled product.
The compose → lint → rubric loop is covered, but rubric is a passive reference with no tool to actually score a draft against it, and there is no update/fix operation to apply the lint suggestions. The presence of groups_list implies additional capability groups exist outside this server, so the visible surface is intentionally partial.