0xPdf MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PDF_PARSING_API_KEY | Yes | Required for authenticated tools | |
| PDF_PARSING_API_BASE_URL | No | Production API | https://api.0xpdf.io |
| PDF_PARSING_REQUIRE_HTTPS | No | Set true for production | false |
| PDF_PARSING_ALLOWED_API_HOSTS | No | Required in production (api.0xpdf.io) | |
| PDF_PARSING_ALLOWED_FILE_ROOTS | No | Colon-separated absolute paths for pdf_path | CWD |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Health check for backend connectivity. Useful before running parse tools. |
| get_pricing_currentC | Get current billing/pricing status for the authenticated user. |
| get_mcp_runtime_metricsA | Get MCP runtime transport metrics for optimization/debugging. |
| reset_mcp_runtime_metricsA | Reset MCP runtime transport metrics counters. |
| parse_pdf_syncC | Parse one PDF synchronously through /api/v1/pdf/parse. |
| parse_pdf_streamC | Parse one PDF as SSE stream through /api/v1/pdf/parse-stream. |
| submit_parse_jobC | Submit one PDF for async processing via /api/v1/pdf/upload. |
| get_parse_job_statusC | Get status for an async parse job created by submit_parse_job. |
| wait_for_job_completionA | Poll job status with exponential backoff and jitter until it is completed/failed or times out. |
| submit_parse_batchC | Submit multiple PDFs for async batch parsing via /api/v1/pdf/batch. |
| get_parse_batch_statusC | Get status for an async parse batch created by submit_parse_batch. |
| wait_for_batch_completionA | Poll batch status with exponential backoff and jitter until it is completed/failed/partial or times out. |
| list_schemasC | List user schemas from /api/v1/schemas. |
| create_schemaA | Save a JSON schema to your account (POST /api/v1/schemas). Requires API key. No wallet charge per save; subject to max saved schemas limit. Use after generate_schema_from_description or for hand-written schemas. |
| generate_schema_from_descriptionA | AI-generate a JSON schema from a description (POST /api/v1/schemas/generate). Requires API key, payment method, and prepaid wallet balance. Debits the same wallet ledger as PDF/OCR parsing on each successful generation. Pair with create_schema to persist. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/risha-max/0xpdf-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server