Document to Markdown

io.github.catalyst-labs-devPublished by GitHub account catalyst-labs-devv1.0.0Updated Oct 25, 2026

PDF/DOCX/XLSX to markdown + RAG chunks, $0.001/page; failed files never charged.

VerifiedStreamable HTTPWeb executableFiles & StorageAI & ML

Overview

AI-generated overview

A hosted Apify MCP server that converts PDF, DOCX and XLSX files into markdown with RAG-ready chunks, billed per page.

What you can do
Convert PDF, DOCX and XLSX documents into markdown text an assistant can read and reuse. Produce chunked output suited to retrieval-augmented generation pipelines. Process files through a hosted Apify endpoint rather than a local install. Failed conversions are not charged, per the description.
When to use it
Useful when an assistant needs to turn office documents or PDFs into markdown or retrieval chunks without running conversion software locally, and when a paid per-page hosted service is acceptable.
Requirements
A remote MCP endpoint at mcp.apify.com over streamable HTTP. An Apify account and either an Apify API token sent as an Authorization bearer header or OAuth sign-in with Apify if the client supports it. Network access.
Before you install
Usage is billed at the stated per-page rate, so conversions spend money on your Apify account. The Authorization header carries an Apify API token, a credential that should be scoped and kept private. Uploaded documents are sent to Apify's hosted service for processing.

Installation

In SourceWeft

  1. Open Document 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.catalyst-labs-dev%2Fdocument-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": {
    "document-to-markdown": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=catalyst-labs/document-to-markdown"
    }
  }
}

README

This repository has no README.

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

1
  1. v1.0.0LatestOct 25, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.