Skip to main content
Glama
deenesjakoruzh
FradSer

MCP Markdown Conversion Server

by FradSer
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

MCP 서버에서 마크다운으로

트위터 팔로우대장간 배지

영어 | 간체 중국어

Cloudflare AI 서비스를 활용하여 다양한 파일 형식을 마크다운 설명으로 변환하는 강력한 모델 컨텍스트 프로토콜(MCP) 서버입니다. 이 서버는 원활한 파일 변환 및 설명 생성을 위한 표준화된 인터페이스를 제공합니다.

주요 특징

  • Cloudflare AI 서비스와의 원활한 통합

  • 효율적인 마크다운 설명 생성

  • 포괄적인 파일 형식 지원

  • 네이티브 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转换服务器를 자동으로 설치하려면 다음을 수행하세요.

지엑스피1

수동 설치

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_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 도구

다양한 파일 형식을 마크다운 설명으로 변환합니다.

입력 매개변수:

  • filePaths : 배열(필수) - 처리할 파일 경로 목록

응답 구조:

[
  {
    "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. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedto-markdown
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0
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

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/FradSer/mcp-server-to-markdown'

If you have feedback or need assistance with the MCP directory API, please join our Discord server