Skip to main content
Glama
deenesjakoruzh
FradSer

MCP Markdown Conversion Server

by FradSer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Servidor MCP a Markdown

Seguir en Twitter insignia de herrería

Inglés | Chino tradicional

Un potente servidor de Protocolo de Contexto de Modelo (MCP) que aprovecha los servicios de IA de Cloudflare para convertir diversos formatos de archivo en descripciones Markdown. Este servidor proporciona una interfaz estandarizada para una conversión de archivos fluida y la generación de descripciones.

Características principales

  • Integración perfecta con los servicios de inteligencia artificial de Cloudflare

  • Generación eficiente de descripciones de Markdown

  • Compatibilidad completa con formatos de archivo

  • Integración nativa de la API de Markdown de Cloudflare

  • Interfaz MCP fácil de usar

  • Compatibilidad entre plataformas

Related MCP server: Textin MCP Server

Formatos de archivo compatibles

Categoría

Extensiones de archivo

Documentos

.pdf

Imágenes

.jpeg, .jpg, .png, .webp, .svg

Contenido web

.html

Datos

.xml, .csv

Hojas de cálculo

.xlsx, .xlsm, .xlsb, .xls, .et, .ods, .numbers

Requisitos del sistema

  • Node.js 18 o posterior

  • Token de API de Cloudflare válido

  • ID de cuenta activa de Cloudflare

Instalación

Instalación mediante herrería

Para instalar Markdown转换服务器 para Claude Desktop automáticamente a través de Smithery :

npx -y @smithery/cli install @FradSer/mcp-server-to-markdown --client claude

Instalación manual

Instalar globalmente usando npm:

npm install -g mcp-server-to-markdown

Configuración del cliente MCP

Integración del cursor

  1. Vaya a la configuración del cursor

  2. Seleccione "MCP" en la barra lateral

  3. Seleccione "Agregar nuevo servidor MCP global".

  4. Aplicar la siguiente configuración:

    {
  "mcpServers": {
    "to-markdown": {
      "command": "mcp-server-to-markdown",
      "args": [
        "CLOUDFLARE_API_TOKEN": "your_api_token"
        "CLOUDFLARE_ACCOUNT_ID": "your_account_id"
      ]
    }
  }
}

Configuración del escritorio de Claude

Agregue lo siguiente a su claude_desktop_config.json :

{
  "mcpServers": {
    "to-markdown": {
      "command": "mcp-server-to-markdown",
      "args": [
            "CLOUDFLARE_API_TOKEN": "your_api_token"
            "CLOUDFLARE_ACCOUNT_ID": "your_account_id"
          ]
    }
  }
}

Configuración de ChatWise

  1. Lanzar ChatWise

  2. Configuración de acceso

  3. Seleccionar sección Herramientas

  4. Haga clic en "+" para agregar una nueva herramienta

  5. Configurar con estos parámetros:

    • Tipo: stdio

    • ID: to-markdown

    • Comando: mcp-server-to-markdown

    • Argumentos:

      CLOUDFLARE_API_TOKEN=your_api_token
CLOUDFLARE_ACCOUNT_ID=your_account_id

Referencia de API

Herramienta de rebajas

Convierte varios formatos de archivos a descripciones Markdown.

Parámetros de entrada:

  • filePaths : Matriz (obligatorio) - Lista de rutas de archivos a procesar

Estructura de respuesta:

[
  {
    "filename": "example.pdf",
    "mimeType": "application/pdf",
    "description": "Generated Markdown description",
    "tokens": 123
  }
]

Guía de desarrollo

Empezando

  1. Clonar y configurar el entorno:

git clone <repository-url>
cd mcp-server-to-markdown
cp .env.example .env

  1. Configurar las credenciales de Cloudflare:

CLOUDFLARE_API_TOKEN=your_api_token
CLOUDFLARE_ACCOUNT_ID=your_account_id

  1. Instalar dependencias y compilar:

npm install
npm run build

Estructura del proyecto

.
├── src/             # Source code
├── dist/            # Compiled output
├── types.ts         # Type definitions
└── .env             # Environment configuration

Scripts disponibles

  • npm run build - Generar código TypeScript

  • npm run inspect - Ejecutar con el inspector MCP

Ejemplo de uso

const result = await toMarkdown({
  filePaths: [
    "/path/to/document.pdf",
    "/path/to/image.jpg"
  ]
});

Licencia

Licencia MIT

Este proyecto es mantenido por Frad LEE

Available Tools

1 tool
to-markdownC

Generate markdown description for files including PDF (.pdf), Images (.jpeg, .jpg, .png, .webp, .svg), HTML (.html), XML (.xml), Microsoft Office (.xlsx, .xlsm, .xlsb, .xls, .et), Open Document Format (.ods), CSV (.csv), and Apple Documents (.numbers)

ParametersJSON Schema
NameRequiredDescriptionDefault
filePathsYesArray of absolute file paths to generate descriptions for

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 full burden. It mentions what the tool does but lacks behavioral details like whether it processes files locally or remotely, error handling for unsupported formats, performance characteristics, or output format specifics. The description is functional but minimal.

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 purpose and lists supported file types without unnecessary elaboration. Every word contributes to understanding the tool's scope, making it appropriately 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 no annotations and no output schema, the description is incomplete. It doesn't explain what the generated markdown includes, how errors are handled, or any behavioral traits. For a tool with one parameter but significant implicit complexity (file processing), more context is needed.

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 already documents the 'filePaths' parameter. The description adds no additional parameter semantics beyond implying file type support, which is partially covered by the schema's lack of constraints. Baseline 3 is appropriate as the schema does the heavy lifting.

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: 'Generate markdown description for files' and lists specific file types it supports. It uses a specific verb ('Generate') and identifies the resource ('files'), but since there are no sibling tools, it doesn't need to differentiate from alternatives.

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 or any contextual prerequisites. It simply lists supported file types without indicating scenarios where this tool is appropriate or any limitations.

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.

  1. 1 tool updatev1.0.0
    • First observedto-markdown
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The single tool 'to-markdown' has a clearly defined and distinct purpose: converting various file formats to markdown descriptions.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'to-markdown' follows a clear verb-object pattern that is appropriate for its function.

Tool Count2/5

A single tool is too few for a server with a broad scope like 'Markdown Conversion Server' that handles multiple file types. This thin surface may force agents to rely on this one tool for all conversion tasks, lacking specialized operations for different formats or scenarios.

Completeness2/5

The tool set is severely incomplete for the server's purpose. While 'to-markdown' covers conversion, there are obvious gaps such as no tools for validating markdown, handling conversion errors, or providing metadata about supported formats, which limits agent workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches