PDF to Markdown — MCP setup
MCP serverDocs & knowledgeHosted MCP front door to the pdf2md API: checked PDF-to-Markdown requests, short-lived credential.
Available today. Use it from your connected AI after setup.
Needs your own PDF to Markdown — MCP setup account. You sign in to it and approve access when you connect.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use PDF to Markdown — MCP setup
Install PDF to Markdown — MCP setup
The server’s own address, for the clients that take one directly. Or connect ahel onceand every client you use reads it from one address, with the account kept on ahel rather than in each client’s config.
Claude Code
claude mcp add --transport http --scope user pdf-to-markdown-mcp-setup 'https://pdf2md.dudko.dev/mcp'Run it once in your project, then open /mcp to approve any sign-in the server asks for.
Claude Desktop
https://pdf2md.dudko.dev/mcpAdd a custom connector in Settings, paste this address, and approve the sign-in.
Cursor
cursor://anysphere.cursor-deeplink/mcp/install?name=pdf-to-markdown-mcp-setup&config=eyJ1cmwiOiJodHRwczovL3BkZjJtZC5kdWRrby5kZXYvbWNwIn0=Open the link and Cursor adds the server at that address.
ChatGPT
https://pdf2md.dudko.dev/mcpIn Settings, enable Developer mode, create an MCP app, and paste this address. Your plan and workspace must allow custom apps.
Codex
codex mcp add pdf-to-markdown-mcp-setup --url 'https://pdf2md.dudko.dev/mcp'Run it once, then sign in with codex mcp login pdf-to-markdown-mcp-setup if the server asks for an account.
From the project's README
As published by dudko-dev/pdf-to-md-mcp-setup in README.md.
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
Then run /mcp and complete the sign-in when prompted.
Prefer not to use the marketplace? Add the server directly:
claude mcp add --transport http pdf-to-md https://pdf2md.dudko.dev/mcp
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):
{
"mcpServers": {
"pdf-to-md": {
"url": "https://pdf2md.dudko.dev/mcp"
}
}
}
VS Code (GitHub Copilot / MCP) and other clients
{
"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. 422from/convert— the PDF is a scan with no text layer. pdf2md does no OCR;detecttells you this before you spend a conversion.- Tools don't appear — check the client finished the sign-in (
/mcpin Claude Code shows connected).
Support
- Website: https://pdf2md.dudko.dev
- API docs: https://pdf2md.dudko.dev/api
- For agents: https://pdf2md.dudko.dev/llms.txt
- Contact: sergey@dudko.dev
Signals
- Last commit
- Sep 2026
Advanced
- Delivery
- pdf-to-md MCP server → your ahel connector (mcp.ahel.ai) → your AI.
- Item type
- mcp-server
- Key
dev-dudko-pdf-to-md- Source
- github.com/dudko-dev/pdf-to-md-mcp-setup
- Hosted endpoint
https://pdf2md.dudko.dev/mcp