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).