Documents to Data (PDF to Markdown, document to JSON)

io.github.owlabeePublished by GitHub account owlabeev1.0.2Updated Nov 7, 2026

Turn PDFs, documents, podcasts and drone photos into Markdown, structured JSON, summaries, reports.

VerifiedStreamable HTTPWeb executableFiles & StorageData & Analytics

Overview

AI-generated overview

Remote Apify-hosted MCP server that turns PDFs, documents, podcasts and drone photos into Markdown, structured JSON, summaries and reports.

What you can do
  • Convert PDFs and other documents into Markdown or structured JSON
  • Extract content from audio such as podcasts and from drone photos
  • Generate summaries and reports from the converted material
  • No individual tools are listed, so exact operations are not documented
When to use it
Useful when an assistant needs to read or restructure document and media files that are not already in plain text, for example turning PDFs into Markdown or JSON for later analysis, or summarizing podcasts and reports.
Requirements
A remote streamable HTTP endpoint at mcp.apify.com, reachable over the network. OAuth authentication is required, with an Apify API token sent in the Authorization header as a Bearer token. An Apify account is needed.
Before you install
The Authorization header carries an Apify API token, so treat it as a secret. Runs are billed per result to your Apify account, so usage costs money. Uploaded documents, audio and photos are processed by Apify's hosted service, a third party.

Installation

In SourceWeft

  1. Open Documents to Data (PDF to Markdown, document to JSON) 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.owlabee%2Fdocuments-to-data/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": {
    "documents-to-data-pdf-to-markdown-docume": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=owlabee/pdf-to-markdown,owlabee/pdf-to-json,owlabee/podcast-summarizer,owlabee/drone-roof-inspection-report"
    }
  }
}

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.2LatestNov 7, 2026

Score

70% 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