de en es ja ko ru zh

UNO-MCP

Name: UNO-MCP
Author: MushroomFleet

by MushroomFleet

Overview Schema Source Related Servers Discussions Admin

TypeScript

🪄 UNO：统一叙事操作器 (Unified Narrative Operator)

✨ 概述

UNO (Unified Narrative Operator) 是一款神奇的文本增强工具，可将普通的叙事内容转化为丰富、详尽的叙事作品。利用先进的文学技巧和启发式分析，UNO 可以在保留原文语调和意图的同时，将文本长度增加一倍。

将 UNO 视为您的个人叙事助手，它能够：

📊 分析您的文本以了解其优缺点
🌱 扩展未充分发展的叙事元素
🎨 丰富环境描写
⚡ 加强动作场景
🌊 平滑文风与节奏
🔄 消除重复语言

Related MCP server: Clear Thought 1.5

🛠️ 功能

UNO 提供三个强大的 MCP 工具：

1. 🔍 `analyze_text`

对您的故事页面进行深度分析，并生成一份综合报告，包括：

📝 叙事位置评估（开头、中间、高潮、结局）
👤 角色焦点识别
🎭 场景类型分类
🌡️ 情绪与语调评估
📈 针对每种技巧的增强建议
🔄 重复模式检测

2. ✨ `enhance_text`

通过应用全部五种增强技巧来转换您的文本：

自动扩展文本以达到目标长度（默认：200%）
根据文本最迫切的需求智能应用技巧
在整个文本中平衡扩展内容

3. ⚙️ `custom_enhance_text`

让您完全掌控增强过程：

选择要应用的增强技巧
设置自定义扩展目标（100%-500%）
专注于叙事的特定方面

🌟 增强技巧

1. 👻 黄金阴影增强 (Golden Shadow Enhancement)

识别故事中未充分发展的元素并进行扩展：

发展提及但未展开的角色
探索暗示但未解释的情节元素
浮现潜台词和隐藏含义

2. 🏞️ 环境扩展 (Environmental Expansion)

用沉浸式细节丰富您的场景：

增加生动的感官体验（视觉、听觉、触觉、嗅觉）
创造对微小事物的难忘聚焦
加深氛围和情绪

3. ⚡ 动作场景增强 (Action Scene Enhancement)

将动作序列转化为动态、高强度的体验：

操纵感知时间（放慢关键时刻）
在动作中强化感官细节
在爆发性动作与瞬间静止之间创造节奏交替
使环境成为动作的积极参与者

4. 🌊 文风平滑 (Prose Smoothing)

改善写作的流畅度和节奏感：

增强段落之间的过渡
改变句子结构以提高可读性
创造自然的节奏，引导读者阅读全文

5. 🔄 重复消除 (Repetition Elimination)

在保持风格的同时减少无意识的重复：

识别并用有意义的替代词替换重复词汇
保持作者的语调和意图
区分有意重复与无意重复

📋 安装

通过 Smithery 安装

要通过 Smithery 自动为 Claude Desktop 安装统一叙事操作器：

npx -y @smithery/cli install @MushroomFleet/uno-mcp --client claude

先决条件

Node.js (v14 或更高版本)
NPM (v6 或更高版本)

分步安装

克隆或下载仓库

git clone https://github.com/your-username/uno-mcp.git
cd uno-mcp

安装依赖
```
npm install
```
构建 TypeScript 文件
```
npm run build
```
使服务器可执行（Windows 跳过此步）
```
chmod +x dist/index.js
```
测试服务器
```
node test-run.js
```
这将在一个示例故事上运行服务器并生成三个文件：
- test-analysis.md：示例分析报告
- test-enhanced.txt：示例增强文本 (200%)
- test-custom-enhanced.txt：示例自定义增强 (150%)

🔌 MCP 集成

Claude Desktop 集成

编辑 Claude 配置文件
- Windows: C:\Users\[用户名]\AppData\Roaming\Claude\claude_desktop_config.json
- macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

将 UNO 添加到 MCP 服务器部分

{
  "mcpServers": {
    "uno": {
      "command": "node",
      "args": ["/absolute/path/to/uno-mcp/dist/index.js"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

请务必使用您 UNO 安装的绝对路径。

重启 Claude 保存配置后，重启 Claude 以激活 UNO MCP 服务器。

VS Code 集成

编辑 VS Code Claude 扩展配置
- Windows: c:\Users\[用户名]\AppData\Roaming\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.json
- macOS: ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
添加与上述 Claude Desktop 相同的配置。
重启 VS Code 或重新加载窗口。

🚀 使用示例

分析故事

<use_mcp_tool>
<server_name>uno</server_name>
<tool_name>analyze_text</tool_name>
<arguments>
{
  "text": "As Sarah walked into the garden, she noticed the old statue in the corner. It was covered in moss and vines, almost hidden from view. She felt drawn to it somehow."
}
</arguments>
</use_mcp_tool>

这将返回一份详细的分析报告，包含关于叙事位置、角色焦点、增强机会等的见解。

增强故事 (200% 扩展)

<use_mcp_tool>
<server_name>uno</server_name>
<tool_name>enhance_text</tool_name>
<arguments>
{
  "text": "As Sarah walked into the garden, she noticed the old statue in the corner. It was covered in moss and vines, almost hidden from view. She felt drawn to it somehow."
}
</arguments>
</use_mcp_tool>

这将返回一个大约是原文两倍长度的文本版本，并应用了所有五种增强技巧。

自定义增强

<use_mcp_tool>
<server_name>uno</server_name>
<tool_name>custom_enhance_text</tool_name>
<arguments>
{
  "text": "As Sarah walked into the garden, she noticed the old statue in the corner. It was covered in moss and vines, almost hidden from view. She felt drawn to it somehow.",
  "expansionTarget": 150,
  "enableGoldenShadow": true,
  "enableEnvironmental": true,
  "enableActionScene": false,
  "enableProseSmoother": true,
  "enableRepetitionElimination": false
}
</arguments>
</use_mcp_tool>

此示例仅应用黄金阴影增强、环境扩展和文风平滑，目标扩展率为 150%。

⚡ 集成用例

📝 创意写作助手

Can you enhance this scene with more environmental details?

<use_mcp_tool>
<server_name>uno</server_name>
<tool_name>custom_enhance_text</tool_name>
<arguments>
{
  "text": "Jack entered the abandoned warehouse, searching for clues.",
  "expansionTarget": 300,
  "enableEnvironmental": true,
  "enableGoldenShadow": false,
  "enableActionScene": false,
  "enableProseSmoother": false,
  "enableRepetitionElimination": false
}
</arguments>
</use_mcp_tool>

📚 写作教练

Let me analyze this paragraph to give you feedback:

<use_mcp_tool>
<server_name>uno</server_name>
<tool_name>analyze_text</tool_name>
<arguments>
{
  "text": "[student's writing sample]"
}
</arguments>
</use_mcp_tool>

Based on the analysis, I recommend focusing on developing your character motivations more clearly.

🎮 游戏叙事开发

Here's a more intense version of your action scene:

<use_mcp_tool>
<server_name>uno</server_name>
<tool_name>custom_enhance_text</tool_name>
<arguments>
{
  "text": "[original action scene]",
  "enableActionScene": true,
  "enableEnvironmental": true,
  "enableGoldenShadow": false,
  "enableProseSmoother": true,
  "enableRepetitionElimination": true
}
</arguments>
</use_mcp_tool>

📔 小说扩展

Let me help you expand this chapter:

<use_mcp_tool>
<server_name>uno</server_name>
<tool_name>enhance_text</tool_name>
<arguments>
{
  "text": "[chapter excerpt]",
  "expansionTarget": 180
}
</arguments>
</use_mcp_tool>

💡 提示与技巧

🔍 始终从 analyze_text 开始，以了解您的文本需求
🎯 对于细微的增强，请使用较低扩展目标 (120-150%) 的 custom_enhance_text
🧩 将较长的文本分成较小的部分进行处理，然后合并结果
🔄 在增强较长作品时，将“重复消除”作为最后一步
⚡ 仅对包含动作元素的场景使用 enableActionScene: true

📄 许可证

ISC

🙏 致谢

UNO 基于先进的文学增强技术和叙事理论。特别感谢那些启发了该项目的讲故事者、作家和叙事理论家。

⭐ 由 UNO 团队倾情打造 ⭐

另请参阅

TranscriptionTools-MCP — 转录处理
DeepLucid3D-MCP — 认知处理
UNO-MCP — 叙事增强
gitea-mcp — Gitea 集成
zero-vector-MCP — 程序化生成

Available Tools

3 tools

analyze_textC

Analyzes a story page and generates a report with insights

ParametersJSON Schema

Name	Required	Description	Default
`text`	Yes	The story page text to analyze or enhance

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions analysis and report generation but lacks details on what 'insights' entail, whether the operation is read-only or has side effects, performance characteristics, or error handling. This is a significant gap for a tool with no annotation coverage.

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 functionality ('Analyzes a story page') and adds the outcome ('generates a report with insights') without any wasted words. It is appropriately sized for the tool's apparent complexity.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the 'report' or 'insights' look like, potential limitations, or how it differs from sibling tools. For a tool with no structured behavioral or output information, more context is needed to guide effective use.

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

Parameters3/5

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

The schema description coverage is 100%, with the single parameter 'text' documented as 'The story page text to analyze or enhance'. The description adds no additional parameter semantics beyond what the schema provides, so the baseline score of 3 is appropriate as the schema handles the documentation adequately.

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

Purpose4/5

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

The description clearly states the tool's purpose with a specific verb ('analyzes') and resource ('a story page'), and specifies the output ('generates a report with insights'). However, it doesn't explicitly differentiate from sibling tools like 'custom_enhance_text' or 'enhance_text', which appear to have related but potentially different functions.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus its siblings ('custom_enhance_text' and 'enhance_text'), nor does it mention any prerequisites, alternatives, or exclusions. It only states what the tool does without contextual usage information.

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

custom_enhance_textC

Enhances a story page using selected techniques

ParametersJSON Schema

Name	Required	Description
`text`	Yes	The story page text to enhance
`expansionTarget`	No	Target expansion percentage (default: 200)
`enableGoldenShadow`	No	Enable Golden Shadow enhancement
`enableEnvironmental`	No	Enable Environmental expansion
`enableActionScene`	No	Enable Action Scene enhancement
`enableProseSmoother`	No	Enable Prose Smoothing
`enableRepetitionElimination`	No	Enable Repetition Elimination

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'enhances' text, implying a transformation, but doesn't describe the nature of the enhancement, potential side effects, rate limits, or output format. This is a significant gap for a tool with multiple parameters and no output schema.

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

Conciseness4/5

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

The description is a single, efficient sentence that front-loads the core action ('enhances a story page'). It avoids unnecessary words, but could be more informative given the tool's complexity, making it slightly under-specified rather than perfectly concise.

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

Completeness2/5

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

Given the tool's complexity (7 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain what 'enhance' entails, how techniques interact, or what the output looks like, leaving critical gaps for an agent to understand and use the tool effectively.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema fully documents all 7 parameters. The description mentions 'selected techniques' but doesn't add meaning beyond the schema, which already details each enhancement technique and parameter. The baseline score of 3 reflects adequate coverage by the schema alone.

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

Purpose3/5

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

The description states the tool 'enhances a story page using selected techniques,' which provides a general purpose but lacks specificity. It mentions the resource ('story page') and verb ('enhances'), but doesn't clarify what 'enhance' means or how it differs from sibling tools like 'enhance_text' and 'analyze_text', leaving the purpose somewhat vague.

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

Usage Guidelines2/5

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

The description offers no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'enhance_text' or 'analyze_text', nor does it specify prerequisites, contexts, or exclusions for usage, leaving the agent without clear direction on tool selection.

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

enhance_textC

Enhances a story page using all techniques to meet expansion target

ParametersJSON Schema

Name	Required	Description	Default
`text`	Yes	The story page text to enhance
`expansionTarget`	No	Target expansion percentage (default: 200)

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'using all techniques' but doesn't explain what these techniques are, whether the enhancement is reversible, what permissions or rate limits apply, or what the output looks like. For a tool with no annotations and an implied mutation ('enhances'), this leaves critical behavioral traits undisclosed.

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

Conciseness4/5

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

The description is a single, efficient sentence that front-loads the core action. It avoids unnecessary words and gets straight to the point. However, it could be slightly more structured by explicitly separating purpose from constraints, but overall it's appropriately concise for the tool's complexity.

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

Completeness2/5

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

Given the tool's implied complexity (enhancing text with multiple techniques) and lack of annotations and output schema, the description is incomplete. It doesn't explain what 'enhance' entails, what techniques are used, or what the result looks like. For a tool that likely modifies content, more context is needed to guide the agent effectively.

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

Parameters3/5

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

The schema description coverage is 100%, with clear descriptions for both parameters ('text' and 'expansionTarget'). The description adds no additional meaning beyond what the schema provides, such as examples or contextual usage. However, since the schema adequately documents the parameters, a baseline score of 3 is appropriate as the description doesn't detract from the schema's clarity.

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

Purpose3/5

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

The description states the tool 'enhances a story page using all techniques to meet expansion target', which provides a vague purpose. It specifies the resource ('story page') and goal ('meet expansion target'), but the verb 'enhances' is generic and doesn't clearly differentiate from sibling tools like 'analyze_text' or 'custom_enhance_text'. The description lacks specificity about what 'enhance' means operationally.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'analyze_text' or 'custom_enhance_text', nor does it specify contexts, prerequisites, or exclusions for usage. The agent must infer usage based on the tool name alone, which is insufficient for informed selection.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

3 tool updatesAug 15, 2025
- First observedanalyze_text
- First observedcustom_enhance_text
- First observedenhance_text

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.7/5.0

Scored 2026-04-18 11:00 across 3 tools

Disambiguation2/5

The tools 'custom_enhance_text' and 'enhance_text' have overlapping purposes, both focused on enhancing story pages, with only a vague distinction based on technique selection versus using all techniques. This creates ambiguity where an agent might struggle to choose between them for a given enhancement task. The 'analyze_text' tool is more distinct but the enhancement tools lack clear boundaries.

Naming Consistency4/5

All tools follow a consistent snake_case naming pattern with a verb_noun structure (e.g., analyze_text, enhance_text). The naming is predictable and readable, with only minor deviation in 'custom_enhance_text' where the adjective 'custom' adds some variation but maintains the overall convention.

Tool Count3/5

With only 3 tools, the server feels thin for a domain like story analysis and enhancement, potentially lacking coverage for broader operations. While it covers basic analyze and enhance functions, the low count may limit agent capabilities in handling more complex workflows or additional CRUD-like actions.

Completeness2/5

The tool set is severely incomplete for a story analysis and enhancement domain, as it only includes analysis and enhancement without any CRUD operations (e.g., create, update, delete story pages) or lifecycle management. This creates significant gaps that will likely cause agent failures when trying to perform full workflows beyond simple text processing.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

writerOAuth
org.swapp1990.writer
Generate full stories, chapters, characters & cover art from a premise (planner-writer pipeline).
AI & Machine Learning Image & Video Processing
2
ParallectOAuth
io.github.securecoders
Fan out deep research across multiple AI providers, synthesize into one unified report.
AI & Machine Learning Research & Data RAG Systems
2
FreeToolBoxes Agent Tools A
io.github.DAMediaCo
Exactly 50 data transformation and live web verification tools for AI agents.
Data Platforms Browser Automation
1
Clueso A
io.clueso
Make videos and docs with your AI agent — describe what you need, every output stays editable.
Multimedia Processing Content Management Systems AI & Machine Learning
4025

Related MCP Servers

Deep Research MCP Server
RAG Systems Web Scraping Search
teelaitila
A
license
Not graded
quality
D
maintenance
Enables iterative deep research by integrating AI agents with search engines, web scraping, and large language models for efficient data gathering and comprehensive reporting.
Updated 8 months ago (2026-01-28 10:48 UTC)
4 npm
323
MIT
Clear Thought 1.5
Developer Tools Autonomous Agents Code Analysis
waldzellai
A
license
Not graded
quality
F
maintenance
Provides 30+ unified reasoning operations including systematic thinking, mental models, debugging approaches, statistical analysis, interactive notebooks, and advanced problem-solving frameworks for enhanced decision-making and complex reasoning tasks.
Updated a year ago (2025-10-20 23:53 UTC)
96 npm
53
MIT
HNPX SDK
Developer Tools Content Management Systems
mozhaa
A
license
B
quality
D
maintenance
Enables AI-guided hierarchical fiction writing through structured XML documents. Supports step-by-step narrative expansion from book-level planning down to individual paragraphs, with custom Roo Code modes for collaborative story development.
Updated 9 months ago (2025-12-07 13:10 UTC)
19
MIT
Galaxy Brain
Autonomous Agents Developer Tools App Automation
For-Sunny
A
license
B
quality
D
maintenance
Combines structured sequential thinking with batch operation execution, enabling step-by-step reasoning with revision/branching capabilities and chained operations with variable piping between steps.
Updated 7 months ago (2026-02-19 04:43 UTC)
15
1
MIT

Appeared in Searches

A server for writing tips and creative writing resources

🪄 UNO：统一叙事操作器 (Unified Narrative Operator)

✨ 概述

🛠️ 功能

1. 🔍 analyze_text

2. ✨ enhance_text

3. ⚙️ custom_enhance_text

🌟 增强技巧

1. 👻 黄金阴影增强 (Golden Shadow Enhancement)

2. 🏞️ 环境扩展 (Environmental Expansion)

3. ⚡ 动作场景增强 (Action Scene Enhancement)

4. 🌊 文风平滑 (Prose Smoothing)

5. 🔄 重复消除 (Repetition Elimination)

📋 安装

通过 Smithery 安装

先决条件

分步安装

🔌 MCP 集成

Claude Desktop 集成

VS Code 集成

🚀 使用示例

分析故事

增强故事 (200% 扩展)

自定义增强

⚡ 集成用例

📝 创意写作助手

📚 写作教练

🎮 游戏叙事开发

📔 小说扩展

💡 提示与技巧

📄 许可证

🙏 致谢

另请参阅

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches

1. 🔍 `analyze_text`

2. ✨ `enhance_text`

3. ⚙️ `custom_enhance_text`