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 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| 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 | |
TDQS
Scored across 15 tools
Each tool has a clearly distinct purpose. PDF parsing tools differentiate by sync/stream/async modes, schema tools are separate from parsing, and status, metrics, health, and pricing tools are all unique with no overlap.
All tools follow a consistent verb_noun pattern in lowercase snake_case, e.g., create_schema, get_parse_job_status, wait_for_batch_completion. No mixed conventions or vague verbs.
15 tools is well-scoped for the domain of PDF parsing and schema management. Each tool serves a necessary role without bloat.
Covers core workflows: PDF parsing (sync, stream, async), schema generation/persistence, status polling, and administrative tools. Minor gap: no schema update or delete, and no cancel/retry for async jobs.