Skip to main content
Glama
enesjakozh
2b3pro

markdown2pdf-mcp

by 2b3pro
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

Markdown2PDF MCP 서버(markdown2pdf-mcp)

마크다운 문서를 PDF 파일로 변환하는 MCP 서버입니다. 이 서버는 구문 강조 및 사용자 지정 스타일을 지원하여 마크다운 콘텐츠에서 PDF를 생성하는 간단하고 효율적인 방법을 제공합니다. 또한 1페이지에 워터마크를 삽입할 수 있습니다.

Alan Shaw의 마크다운-pdf 에서 영감을 얻었습니다.

특징

  • 단일 명령으로 Markdown을 PDF로 변환

  • 코드 블록에 대한 구문 강조 표시

  • PDF 출력을 위한 사용자 정의 CSS 스타일

  • 표준 마크다운 형식 지원

  • Chrome의 렌더링 엔진을 사용한 최신 PDF 생성

  • 최신 웹 기능 및 글꼴에 대한 탁월한 지원

  • 안정적인 리소스 로딩 및 렌더링

Related MCP server: MD-PDF MCP Server

제한 사항

다음 마크다운 요소는 지원되지 않습니다.

  • LaTeX 수학 방정식(예: $x^2$ 또는 $$\sum_{i=1}^n x_i$$ )

  • 복잡한 수학 공식이나 과학적 표기법

지원되는 마크다운 요소를 사용하세요.

  • 헤더(모든 레벨)

  • 텍스트 서식(굵게, 기울임꼴, 취소선)

  • 목록(순서가 있는 목록과 순서가 없는 목록)

  • 구문 강조가 있는 코드 블록

  • 테이블

  • 인용구

  • 모래밭

  • 이미지(로컬 파일과 외부 URL 모두)

  • 작업 목록

설치

지엑스피1

용법

서버 시작

npm start

MCP 도구 사용

서버는 다음 매개변수를 포함하는 단일 도구 create_pdf_from_markdown 제공합니다.

{
  // Required parameters
  markdown: string;    // Markdown content to convert

  // Optional parameters with defaults
  outputFilename?: string;  // Filename for the PDF (e.g., "output.pdf")
  paperFormat?: string;     // 'letter' (default), 'a4', 'a3', 'a5', 'legal', 'tabloid'
  paperOrientation?: string; // 'portrait' (default), 'landscape'
  paperBorder?: string;     // '2cm' (default), accepts decimal values with CSS units (e.g., '1.5cm', '2.5mm', '0.5in', '10.5px')
  watermark?: string;       // Optional watermark text (max 15 characters, uppercase)
}

옵션이 있는 예:

await use_mcp_tool({
  server_name: "markdown2pdf",
  tool_name: "create_pdf_from_markdown",
  arguments: {
    markdown: "# Hello World\n\nThis is a test document.",
    outputFilename: "output.pdf",
    paperFormat: "a4",
    paperOrientation: "landscape",
    paperBorder: "1.5cm",
    watermark: "DRAFT",
  },
});

최소 사용 예시:

await use_mcp_tool({
  server_name: "markdown2pdf",
  tool_name: "create_pdf_from_markdown",
  arguments: {
    markdown: "# Hello World\n\nThis is a test document.",
    outputFilename: "output.pdf",
  },
});

구성

출력 디렉토리

Cline이나 Claude처럼 MCP를 사용하는 앱의 경우, MCP 설정 파일에서 출력 디렉터리를 구성할 수 있습니다. 구성하지 않으면 $HOME에 파일이 저장됩니다.

{
  "mcpServers": {
    "markdown2pdf": {
      "command": "node",
      "args": ["path/to/markdown2pdf-mcp/build/index.js"],
      "env": {
        "M2P_OUTPUT_DIR": "/path/to/output/directory"
      }
    }
  }
}

이 도구는 증분 숫자를 추가하여 파일 이름 충돌을 자동으로 처리합니다(예: output.pdf, output-1.pdf, output-2.pdf).

종속성

크롬 버전

이 패키지는 모든 설치 환경에서 일관된 PDF 생성을 위해 Chrome v131.0.6778.204를 사용합니다. 이 버전은 npm install 실행하면 자동으로 설치됩니다.

  • tmp - 임시 파일 처리

개발

# Build the project
npm run build

# Start the server
npm start

특허

MIT

기여하다

  1. 저장소를 포크하세요

  2. 기능 브랜치를 생성합니다( git checkout -b feature/amazing-feature )

  3. 변경 사항을 커밋하세요( git commit -m 'Add some amazing feature' )

  4. 브랜치에 푸시( git push origin feature/amazing-feature )

  5. 풀 리퀘스트 열기

Available Tools

1 tool
create_pdf_from_markdownA

Convert markdown content to PDF. Supports basic markdown elements like headers, lists, tables, code blocks, blockquotes, images (both local and external URLs), and Mermaid diagrams. Note: Cannot handle LaTeX math equations. Mermaid syntax errors will be displayed directly in the PDF output.

ParametersJSON Schema
NameRequiredDescriptionDefault
markdownYesMarkdown content to convert to PDF
outputFilenameNoCreate a filename for the PDF file to be saved (default: "final-output.pdf"). The environmental variable M2P_OUTPUT_DIR sets the output path directory. If directory is not provided, it will default to user's HOME directory.
paperBorderNoBorder margin for the PDF (default: 2cm). Use CSS units (cm, mm, in, px)20mm
paperFormatNoPaper format for the PDF (default: letter)letter
paperOrientationNoPaper orientation for the PDF (default: portrait)portrait
watermarkNoOptional watermark text (max 15 characters, uppercase), e.g. "DRAFT", "PRELIMINARY", "CONFIDENTIAL", "FOR REVIEW", etc

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden and does well by disclosing key behavioral traits: it describes the conversion process, notes limitations (cannot handle LaTeX math), and specifies how errors (Mermaid syntax errors) are handled in the output. It also hints at file-saving behavior via the outputFilename parameter context.

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 appropriately sized and front-loaded, starting with the core purpose, then listing supported elements, and ending with limitations. Every sentence adds value without redundancy, making it efficient and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (6 parameters, no output schema, no annotations), the description is quite complete: it covers purpose, supported features, limitations, and behavioral aspects. However, it could improve by mentioning the output format (PDF file) more explicitly or noting any side effects like file creation, though some of this is inferred from parameters.

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%, so the schema already documents all 6 parameters thoroughly. The description does not add any parameter-specific semantics beyond what the schema provides, such as explaining interactions between parameters or usage nuances. This meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 ('Convert') and resource ('markdown content to PDF'), and distinguishes it by listing supported elements (headers, lists, tables, etc.) and limitations (no LaTeX math, Mermaid errors displayed). With no sibling tools, this level of detail is excellent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by specifying what markdown elements are supported and what is not handled (LaTeX math), but it does not provide explicit guidance on when to use this tool versus alternatives (e.g., other PDF generators or markdown processors). With no sibling tools, this is adequate but lacks broader context.

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 observedcreate_pdf_from_markdown
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.9/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.

Naming Consistency5/5

A single tool inherently has consistent naming, as there are no other tools to compare against. The name 'create_pdf_from_markdown' follows a clear verb_noun pattern.

Tool Count2/5

One tool is too few for a server's purpose, as it severely limits functionality and flexibility. The server's scope (markdown to PDF conversion) could reasonably support additional tools for customization, validation, or batch processing.

Completeness2/5

The tool surface is severely incomplete for markdown-to-PDF conversion. While the core conversion is covered, there are obvious gaps such as no tools for configuring PDF settings (e.g., margins, page size), handling errors gracefully, or managing multiple conversions efficiently.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

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/2b3pro/markdown2pdf-mcp'

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