PDF to Markdown

dev.dudko由 dudko.dev 發布官方發布者v1.0.0更新於 Oct 24, 2026

Hosted MCP front door to the pdf2md API: checked PDF-to-Markdown requests, short-lived credential.

已驗證Streamable HTTP可網頁執行檔案與儲存開發者工具

服務詳細資訊

識別碼: dev.dudko/pdf-to-md
傳輸: Streamable HTTP
執行環境: Web executable
信任: Verified
發布於: Sep 26, 2026

安全提示

MCP 服務會接收對話中的工具呼叫請求，並可能執行外部操作。啟用前請先了解該服務能做什麼，並只授予它所需的權限。

註冊中心已驗證此服務的命名空間屬於 dudko.dev，且該網域同時執行其端點。這可以確認發布者，但並不代表該服務的工具是安全的。

SourceWeft 的檢查只涵蓋條目是否完整、端點是否回應；不審查伺服器的程式碼，也不審查其工具的行為。

在 README 中新增徽章

向讀者展示該 MCP 服務已收錄於 SourceWeft，徽章連結到本頁。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/dev.dudko%2Fpdf-to-md.svg)](https://sourceweft.com/mcp/dev.dudko%2Fpdf-to-md?utm_source=readme&utm_medium=badge)

概覽

AI 產生的概覽

託管於 pdf2md API 前的 MCP 入口，讓助理查詢轉換選項並取得附短期憑證、可直接執行的請求。

可以做什麼: 透過 api_access 查詢 pdf2md API 的端點、選項、限制與錯誤。透過 api_request 驗證 convert、detect、text 的轉換選項，並回傳確切的請求，包含 URL、標頭與 curl 指令。助理在 PDF 所在位置自行執行該請求，API 直接回覆呼叫方。
適用情境: 當你希望助理透過 pdf2md 服務把 PDF 轉成 Markdown（含表格與圖片），又不想貼上 API 金鑰時使用。也適合在耗費一次轉換前先確認 PDF 是否含文字層。
執行需求: 透過 streamable HTTP 連線的遠端 MCP 端點，在相容用戶端中依 URL 加入。需以 dudko.dev 帳號經 auth.dudko.dev 的 OAuth 2.1 登入（scope 為 usage）；不需 API 金鑰或環境變數。需要能連線該端點與 pdf2md API 的網路。

安裝前請注意

工具會回傳短期憑證（15 分鐘，僅對該 API 有效），助理隨後用它呼叫 API，應視為機密。每次轉換都計入帳號方案，配額用盡會回傳 402。伺服器本身不保存檔案或內容，但 PDF 會由助理送往 pdf2md API。不支援 OCR，無文字層的掃描檔會失敗。

安裝

在 SourceWeft 中

開啟儀表板中的 PDF to Markdown，將其新增到工作區。
連接所需的憑證。它們會被私密儲存，絕不會在公開頁面上展示。
為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/dev.dudko%2Fpdf-to-md/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。客戶端會在首次連接時完成 OAuth 登入。

{
  "mcpServers": {
    "pdf-to-markdown": {
      "type": "http",
      "url": "https://pdf2md.dudko.dev/mcp"
    }
  }
}

README

PDF to Markdown — MCP setup

Connect your AI assistant to pdf2md — PDF to clean Markdown, tables and images included — through our hosted Model Context Protocol (MCP) server. Sign in once with your dudko.dev account; no API key to paste.

The server is the front door to the pdf2md HTTP API, not a converter: a document never travels through the model or through the server. The assistant asks for a request, and runs it wherever the PDF is.

Server: pdf-to-md
Transport: streamable HTTP
URL: https://pdf2md.dudko.dev/mcp
Auth: OAuth 2.1 via auth.dudko.dev — you'll be prompted to sign in.

What you can do

Two tools, both free:

Tool	What it does
`api_access`	How the pdf2md API works: endpoints, options, limits, errors.
`api_request`	Checks conversion options (`convert`, `detect`, `text`) and returns the exact request — URL, headers, a curl command — with a 15-minute credential for your account.

Install in Claude Code (plugin)

/plugin marketplace add dudko-dev/pdf-to-md-mcp-setup/plugin install pdf-to-md@pdf-to-md/reload-plugins

/plugin marketplace add dudko-dev/pdf-to-md-mcp-setup/plugin install pdf-to-md@pdf-to-md/reload-plugins

Then run /mcp and complete the sign-in when prompted.

Prefer not to use the marketplace? Add the server directly:

Connect from other clients

Same remote URL, same sign-in — only the config location differs.

Claude Desktop / claude.ai connectors

Open Settings → Connectors → Add custom connector.
Name: PDF to Markdown
URL: https://pdf2md.dudko.dev/mcp
Save, then connect and sign in when prompted.

Cursor

~/.cursor/mcp.json (global) or .cursor/mcp.json (per project):

VS Code (GitHub Copilot / MCP) and other clients

json

{  "servers": {    "pdf-to-md": {      "type": "http",      "url": "https://pdf2md.dudko.dev/mcp"    }  }}

{  "servers": {    "pdf-to-md": {      "type": "http",      "url": "https://pdf2md.dudko.dev/mcp"    }  }}

Authentication

The server is an OAuth 2.1 resource server. The first call answers 401 with a WWW-Authenticate header pointing at its protected-resource metadata:

https://pdf2md.dudko.dev/.well-known/oauth-protected-resource/mcp

which names https://auth.dudko.dev as the authorization server (scope usage). Compliant MCP clients discover this automatically — you only need the server URL, and you sign in with your dudko.dev account. Tokens are audience-bound to https://pdf2md.dudko.dev/mcp and are refused anywhere else.

The server itself carries no files and no content: its tools return a ready-to-run HTTP request with a short-lived credential (15 minutes, good for this API only) for the account you signed in as. Your assistant runs that request wherever the file is, and the API answers the caller directly. Each request counts against your account's plan like any other API call; the MCP tools themselves are free.

Troubleshooting

401 / asked to sign in again — the token expired; reconnect in the client.
"plan used up" / 402 — the conversion quota for your account is spent; retrying will not help. See https://auth.dudko.dev/account.
422 from /convert — the PDF is a scan with no text layer. pdf2md does no OCR; detect tells you this before you spend a conversion.
Tools don't appear — check the client finished the sign-in (/mcp in Claude Code shows connected).