Doc To Markdown

io.github.pavel-tashevPublished by GitHub account pavel-tashevv1.1.0Updated Oct 25, 2026

PDF, Word, PowerPoint, Excel, HTML, EPUB to Markdown: OCR, page ranges, tables, RAG chunking

VerifiedStreamable HTTPWeb executableFiles & StorageData & Analytics

Overview

AI-generated overview

A remote MCP server that converts PDF, Word, PowerPoint, Excel, HTML and EPUB files into Markdown, with OCR, page ranges, tables and RAG chunking.

What you can do
Convert PDF, Word, PowerPoint, Excel, HTML and EPUB documents into Markdown text, optionally using OCR for scanned content and selecting page ranges. Extract tables during conversion and split output into chunks suited to retrieval-augmented generation pipelines.
When to use it
Useful when an assistant needs to turn office documents or PDFs into clean Markdown for reading, summarization, search or RAG ingestion, especially when OCR or page selection is needed.
Requirements
A remote endpoint at mcp.apify.com reached over streamable HTTP, with OAuth authentication required. No local package, environment variables or headers are declared.
Before you install
Access requires OAuth sign-in, so the server is tied to an account. Uploaded documents are sent to a third-party service (Apify) for conversion, so avoid confidential or regulated files unless that is acceptable.

Installation

In SourceWeft

  1. Open Doc To Markdown in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.pavel-tashev%2Fdoc-to-markdown/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "doc-to-markdown": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=pavel.tashev/doc-to-markdown"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.1.0LatestSep 21, 2026
  2. v1.0.0Sep 20, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.