Skip to main content
Glama
deenesjakoruzh
FradSer

MCP Markdown Conversion Server

by FradSer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

MCP 服务器到 Markdown

Twitter 关注 铁匠徽章

English |简体中文

强大的模型上下文协议 (MCP) 服务器，利用 Cloudflare AI 服务将各种文件格式转换为 Markdown 描述。该服务器提供标准化接口，可实现无缝的文件转换和描述生成。

主要特点

  • 与 Cloudflare AI 服务无缝集成

  • 高效的 Markdown 描述生成

  • 全面的文件格式支持

  • 原生 Cloudflare tomarkdown API 集成

  • 用户友好的 MCP 界面

  • 跨平台兼容性

Related MCP server: Textin MCP Server

支持的文件格式

类别

文件扩展名

文件

.pdf

图片

.jpeg、.jpg、.png、.webp、.svg

网页内容

.html

数据

.xml、.csv

电子表格

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

系统要求

  • Node.js 18 或更高版本

  • 有效的 Cloudflare API 令牌

  • 有效的 Cloudflare 帐户 ID

安装

通过 Smithery 安装

要通过Smithery自动为 Claude Desktop 安装 Markdown 转换服务器：

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

手动安装

使用 npm 全局安装：

npm install -g mcp-server-to-markdown

MCP 客户端配置

光标集成

  1. 导航至光标设置

  2. 从侧边栏中选择“MCP”

  3. 选择“添加新的全局 MCP 服务器”

  4. 应用以下配置：

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

Claude 桌面设置

将以下内容添加到您的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"
          ]
    }
  }
}

ChatWise 配置

  1. 启动 ChatWise

  2. 访问设置

  3. 选择“工具”部分

  4. 点击“+”添加新工具

  5. 使用以下参数进行配置：

    • 类型： stdio

    • ID： to-markdown

    • 命令： mcp-server-to-markdown

    • 参数：

      CLOUDFLARE_API_TOKEN=your_api_token
CLOUDFLARE_ACCOUNT_ID=your_account_id

API 参考

to-markdown 工具

将各种文件格式转换为Markdown描述。

输入参数：

  • filePaths ：Array（必需） - 要处理的文件路径列表

响应结构：

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

开发指南

入门

  1. 克隆和设置环境：

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

  1. 配置 Cloudflare 凭据：

CLOUDFLARE_API_TOKEN=your_api_token
CLOUDFLARE_ACCOUNT_ID=your_account_id

  1. 安装依赖项并构建：

npm install
npm run build

项目结构

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

可用脚本

  • npm run build - 构建 TypeScript 代码

  • npm run inspect - 使用 MCP 检查器运行

使用示例

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

执照

MIT 许可证

该项目由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