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용 Unified Narrative Operator를 자동으로 설치하려면:

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
MCP 서버 섹션에 UNO 추가

{
  "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로 시작하여 텍스트에 무엇이 필요한지 파악하세요.
🎯 미묘한 강화를 원할 경우, custom_enhance_text를 낮은 확장 목표(120-150%)로 사용하세요.
🧩 긴 텍스트는 작은 섹션으로 나누어 처리한 후 결과를 합치세요.
🔄 긴 작품을 강화할 때는 마지막 단계로 '반복 제거'를 적용하세요.
⚡ 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`