Document Parse

Parses documents into Markdown by path using MCP, exposing supported file types and a parse endpoint.

other

5

GitHub Stars

other

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "niutrans-mcp-documentparse": {
      "command": "uv",
      "args": [
        "tool",
        "run",
        "mcp-document-parse"
      ],
      "env": {
        "NIUTRANS_API_KEY": "${env.NIUTRANS_API_KEY}",
        "NIUTRANS_DOCUMENT_APPID": "${env.NIUTRANS_DOCUMENT_APPID}"
      }
    }
  }
}

You use the MCP Document Parse Server to convert documents into Markdown content through a controlled MCP client. It parses common document formats and exposes a simple tool surface so you can integrate document parsing into your workflows or other MCP-enabled applications.

How to use

You run the document parsing tool through an MCP client. After starting your MCP-enabled application, you can list available tools and begin parsing files by path. The primary tool converts a specified file into Markdown text, returning the content or an error if the operation fails. You can also query the system for the list of supported file types.

How to install

Prerequisites you need before installing this MCP server are a functioning MCP runtime, and a compatible environment for running MCP clients. Ensure your environment supports the UV-based tool runner used for MCP execution.

Install and start the MCP document parse server via the provided MCP runner configuration. The following configuration shows how to wire the local MCP server into your client setup.

Configuration and runtime details

Environment variables and runtime details are required to authenticate with the document parsing API. You will set these values in your MCP client configuration so the server can call the remote parsing service.

{
  "mcpServers": {
    "document_parse": {
      "type": "stdio",
      "command": "uv",
      "args": [
        "tool",
        "run",
        "mcp-document-parse"
      ],
      "env": {
        "NIUTRANS_API_KEY": "${env.NIUTRANS_API_KEY}",
        "NIUTRANS_DOCUMENT_APPID": "${env.NIUTRANS_DOCUMENT_APPID}"
      }
    }
  }
}

Tools and endpoints

Two tools are exposed by this MCP setup. The first converts a file at a given path into Markdown text. The second provides information about which file types are supported for parsing.

Troubleshooting and notes

Common issues include missing API keys, incorrect file paths, or unsupported file formats. Ensure your environment variables are correctly provided to the MCP server and that the target file path exists and is accessible by the host process.

Available tools

parse_document_by_path

Converts a file located at a given absolute path to Markdown text. Supports pdf, doc, docx, xls, xlsx, ppt, pptx.

document://supported-types

Returns a JSON object describing the supported file types and their descriptions.