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: Operador Narrativo Unificado (Unified Narrative Operator)

✨ Descripción general

UNO (Operador Narrativo Unificado) es una herramienta mágica de mejora de texto que transforma contenido narrativo ordinario en narrativas ricas y detalladas. Utilizando técnicas literarias avanzadas y análisis heurístico, UNO puede duplicar la longitud de su texto mientras preserva la voz y la intención originales.

Piense en UNO como su asistente narrativo personal, capaz de:

📊 Analizar su texto para comprender sus fortalezas y debilidades
🌱 Desarrollar elementos narrativos poco trabajados
🎨 Enriquecer las descripciones ambientales
⚡ Intensificar las secuencias de acción
🌊 Suavizar el flujo y el ritmo de la prosa
🔄 Eliminar el lenguaje repetitivo

Related MCP server: Clear Thought 1.5

🛠️ Características

UNO proporciona tres potentes herramientas MCP:

1. 🔍 `analyze_text`

Realiza un análisis profundo de las páginas de su historia y genera un informe completo que incluye:

📝 Evaluación de la posición narrativa (inicio, nudo, clímax, desenlace)
👤 Identificación del enfoque de los personajes
🎭 Clasificación del tipo de escena
🌡️ Evaluación del estado de ánimo y el tono
📈 Recomendaciones de mejora para cada técnica
🔄 Detección de patrones de repetición

2. ✨ `enhance_text`

Transforma su texto aplicando las cinco técnicas de mejora:

Expande automáticamente el texto para alcanzar la longitud objetivo (predeterminado: 200%)
Aplica técnicas de forma inteligente según lo que más necesite su texto
Equilibra las expansiones a lo largo de todo el texto

3. ⚙️ `custom_enhance_text`

Le brinda un control total sobre el proceso de mejora:

Elija qué técnicas de mejora aplicar
Establezca objetivos de expansión personalizados (100%-500%)
Concéntrese en aspectos específicos de su narrativa

🌟 Técnicas de mejora

1. 👻 Mejora de la Sombra Dorada (Golden Shadow)

Identifica elementos poco desarrollados en su historia y los expande:

Desarrolla personajes mencionados pero no desarrollados
Explora elementos de la trama implícitos pero no explicados
Saca a la luz el subtexto y los significados ocultos

2. 🏞️ Expansión ambiental

Enriquece sus escenarios con detalles inmersivos:

Añade experiencias sensoriales vívidas (visuales, auditivas, táctiles, olfativas)
Crea un enfoque memorable en objetos insignificantes
Profundiza la atmósfera y el estado de ánimo

3. ⚡ Mejora de escenas de acción

Transforma las secuencias de acción en experiencias dinámicas y de alta intensidad:

Manipula el tiempo percibido (ralentizando momentos cruciales)
Intensifica los detalles sensoriales durante la acción
Crea una alternancia rítmica entre la acción explosiva y la quietud momentánea
Convierte los entornos en participantes activos de la acción

4. 🌊 Suavizado de prosa

Mejora el flujo y el ritmo de su escritura:

Mejora las transiciones entre párrafos
Varía la estructura de las oraciones para una mejor legibilidad
Crea un ritmo natural que guía a los lectores a través del texto

5. 🔄 Eliminación de repeticiones

Reduce la repetición involuntaria mientras preserva el estilo:

Identifica y reemplaza palabras repetidas con alternativas significativas
Mantiene la voz y la intención del autor
Distingue entre la repetición intencional y la involuntaria

📋 Instalación

Instalación a través de Smithery

Para instalar el Operador Narrativo Unificado para Claude Desktop automáticamente a través de Smithery:

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

Requisitos previos

Node.js (v14 o superior)
NPM (v6 o superior)

Instalación paso a paso

Clone o descargue el repositorio

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

Instale las dependencias
```
npm install
```
Compile los archivos TypeScript
```
npm run build
```
Haga que el servidor sea ejecutable (omita esto en Windows)
```
chmod +x dist/index.js
```
Pruebe el servidor
```
node test-run.js
```
Esto ejecutará el servidor en una historia de muestra y generará tres archivos:
- test-analysis.md: Informe de análisis de muestra
- test-enhanced.txt: Texto mejorado de muestra (200%)
- test-custom-enhanced.txt: Mejora personalizada de muestra (150%)

🔌 Integración MCP

Integración con Claude Desktop

Edite el archivo de configuración de Claude
- Windows: C:\Users\[nombre_de_usuario]\AppData\Roaming\Claude\claude_desktop_config.json
- macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Añada UNO a la sección de servidores MCP

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

Asegúrese de utilizar la ruta absoluta a su instalación de UNO.

Reinicie Claude Después de guardar la configuración, reinicie Claude para activar el servidor MCP de UNO.

Integración con VS Code

Edite la configuración de la extensión Claude de VS Code
- Windows: c:\Users\[nombre_de_usuario]\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
Añada la misma configuración que se muestra arriba para Claude Desktop.
Reinicie VS Code o recargue la ventana.

🚀 Ejemplos de uso

Análisis de una historia

<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>

Esto devolverá un informe de análisis detallado con información sobre la posición narrativa, el enfoque de los personajes, las oportunidades de mejora y más.

Mejora de una historia (expansión del 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>

Esto devolverá una versión de su texto que es aproximadamente el doble de la longitud original, con las cinco técnicas de mejora aplicadas.

Mejora personalizada

<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>

Este ejemplo aplica solo la Mejora de la Sombra Dorada, la Expansión Ambiental y el Suavizado de Prosa, apuntando a una expansión del 150%.

⚡ Casos de uso de integración

📝 Asistente de escritura creativa

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>

📚 Entrenador de escritura

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.

🎮 Desarrollo de narrativa de juegos

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>

📔 Expansión de novelas

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>

💡 Consejos y trucos

🔍 Comience siempre con analyze_text para entender lo que necesita su texto
🎯 Para mejoras sutiles, use custom_enhance_text con un objetivo de expansión más bajo (120-150%)
🧩 Divida los textos más largos en secciones más pequeñas para procesarlos y luego combine los resultados
🔄 Aplique la Eliminación de Repeticiones como paso final al mejorar trabajos más largos
⚡ Use enableActionScene: true solo para escenas que contengan elementos de acción

📄 Licencia

ISC

🙏 Agradecimientos

UNO se basa en técnicas avanzadas de mejora literaria y teoría narrativa. Un agradecimiento especial a los narradores, escritores y teóricos narrativos cuyo trabajo inspiró este proyecto.

⭐ Hecho con amor por el equipo de UNO ⭐

Ver también

TranscriptionTools-MCP — Procesamiento de transcripciones
DeepLucid3D-MCP — Procesamiento cognitivo
UNO-MCP — Mejora narrativa
gitea-mcp — Integración con Gitea
zero-vector-MCP — Generación procedimental

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: Operador Narrativo Unificado (Unified Narrative Operator)

✨ Descripción general

🛠️ Características

1. 🔍 analyze_text

2. ✨ enhance_text

3. ⚙️ custom_enhance_text

🌟 Técnicas de mejora

1. 👻 Mejora de la Sombra Dorada (Golden Shadow)

2. 🏞️ Expansión ambiental

3. ⚡ Mejora de escenas de acción

4. 🌊 Suavizado de prosa

5. 🔄 Eliminación de repeticiones

📋 Instalación

Instalación a través de Smithery

Requisitos previos

Instalación paso a paso

🔌 Integración MCP

Integración con Claude Desktop

Integración con VS Code

🚀 Ejemplos de uso

Análisis de una historia

Mejora de una historia (expansión del 200%)

Mejora personalizada

⚡ Casos de uso de integración

📝 Asistente de escritura creativa

📚 Entrenador de escritura

🎮 Desarrollo de narrativa de juegos

📔 Expansión de novelas

💡 Consejos y trucos

📄 Licencia

🙏 Agradecimientos

Ver también

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`