Skip to main content
Glama
markdown-new-mcp

markdown-new-mcp

by takltc

markdown-new-mcp

MCP (Model Context Protocol) server for markdown.new file conversion API. Convert PDF, DOCX, XLSX, images and 20+ formats to Markdown.

Installation

npm install markdown-new-mcp

Related MCP server: MarkItDown MCP

Usage

With Claude Desktop or Claude Code

For stdio MCP clients, use npx -y so the server starts under Node.js and preserves the JSON-RPC stdio stream. Add this to your Claude config:

{
  "mcpServers": {
    "markdown-new": {
      "command": "npx",
      "args": ["-y", "markdown-new-mcp@latest"]
    }
  }
}

With opencode

Add this to the mcp section of ~/.config/opencode/opencode.json:

{
  "mcp": {
    "markdown-new": {
      "type": "local",
      "command": ["npx", "-y", "markdown-new-mcp@latest"]
    }
  }
}

With API Key (Optional)

For higher rate limits, you can provide an API key via environment variable:

{
  "mcpServers": {
    "markdown-new": {
      "command": "npx",
      "args": ["-y", "markdown-new-mcp@latest"],
      "env": {
        "MARKDOWN_NEW_API_KEY": "mk_your_api_key_here"
      }
    }
  }
}

Optional:

  • MARKDOWN_NEW_TIMEOUT_MS: request timeout in milliseconds for upstream API calls (default: 30000)

Available Tools

convert_url_to_markdown

Convert a remote file URL to clean Markdown text. Supports PDF, DOCX, XLSX, images, and 20+ formats.

Parameters:

  • url (string, required): HTTP or HTTPS URL of the remote file

  • api_key (string, optional): API key for higher rate limits; the server also reads MARKDOWN_NEW_API_KEY

Example:

Convert this PDF to markdown: https://example.com/document.pdf

convert_file_to_markdown

Convert a local file to clean Markdown text. The path must be absolute and visible to the server process. Supports PDF, DOCX, XLSX, images, and 20+ formats.

Parameters:

  • file_path (string, required): The absolute path to the local file

  • api_key (string, optional): API key for higher rate limits; the server also reads MARKDOWN_NEW_API_KEY

Example:

Convert /path/to/document.pdf to markdown

convert_url_to_json

Convert a remote file URL to structured JSON, including metadata such as title, tokens, and duration. Supports PDF, DOCX, XLSX, images, and 20+ formats.

Parameters:

  • url (string, required): The URL of the remote file

  • api_key (string, optional): API key for higher rate limits; the server also reads MARKDOWN_NEW_API_KEY

Supported Formats

  • Documents: PDF, DOCX, ODT

  • Spreadsheets: XLSX, XLS, XLSM, XLSB, ET, ODS, Numbers

  • Images: JPG, JPEG, PNG, WebP, SVG

  • Text/Data: TXT, MD, CSV, JSON, XML, HTML, HTM

Limits

  • Without API Key: 500 requests/day per IP

  • With API Key: Higher limits available

  • Maximum File Size: 10MB

Development

# Install dependencies
npm install

# Build
npm run build

# Run locally
npm run dev

# Smoke test the stdio MCP server
npm run build
npm run smoke:stdio -- node dist/index.js

License

MIT

Available Tools

3 tools
convert_file_to_markdownA
Read-only

Convert a local file to clean Markdown text. The path must be absolute and visible to the server process. Supports PDF, DOCX, XLSX, images, and 20+ formats.

Inputs: file_path (required), api_key.

convert_url_to_jsonB
Read-only

Convert a remote file URL to structured JSON, including metadata such as title, tokens, and duration. Supports PDF, DOCX, XLSX, images, and 20+ formats.

Inputs: url (required), api_key.

convert_url_to_markdownA
Read-only

Convert a remote file URL to clean Markdown text. Supports PDF, DOCX, XLSX, images, and 20+ formats.

Inputs: url (required), api_key.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct combination of input source (URL vs local file) and output format (Markdown vs JSON), and the descriptions clearly state these differences, leaving no ambiguity in selection.

    Naming Consistency5/5

    All three tools follow the identical pattern convert_{source}_to_{format}, using snake_case consistently and predictable verb-noun structure throughout.

    Tool Count5/5

    Three tools is well-scoped for a focused file-conversion server, covering the primary source-output combinations without unnecessary bloat or glaring thinness.

    Completeness3/5

    The surface covers URL→Markdown, file→Markdown, and URL→JSON, but omits file→JSON conversion, which is an obvious companion operation given the existing URL→JSON tool. This gap may force workarounds for local files needing structured output.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers