PDFHQ logo

Documents

DocumentationAutomation & integrations

PDFHQ MCP integration

Delegated HQTools OAuth with account-owned resources, operation-specific read/write scopes and normal HQ-credit admission. Hosted OAuth and supported-client certification remain pending.

Server-side API keys Signed storage uploads

HQTools OAuth and delegated scopes#

PDFHQ MCP follows ConverterHQ's authorization model: connect using HQTools OAuth Authorization Code + PKCE, consent to named PDFHQ read/write scopes, and use an audience-verified access token for PDFHQ. PDFHQ verifies issuer, signature, audience, expiration, scope and account entitlements for every API operation. No separate PDFHQ human-approval console, grant ID or static backend project API key is involved.

The authenticated user's HQTools account owns the resources. Read-only OAuth grants cannot submit or cancel jobs; writes use the same idempotent PDFHQ job creation, quota checks and HQ Credit settlement as the normal API. AI operations use their unified HQ-credit accounting. No agent-controlled account or project selection is accepted.

Hosted MCP connection#

MCP server URL
https://mcp.pdfhq.io/mcp

Remote MCP is an opt-in source implementation pending full hosted OAuth PKCE, client protocol, revocation and billing integration tests. The URL is a deployment target, not a claim that the service is already live. The local stdio server is for development; use a delegated OAuth token, not a long-lived API key.

PDF tools include read-only discovery/status and allowlisted create-job operations. Ordinary authorized writes do not need another consent prompt. Signing dispatch, irreversible redaction and deletion remain outside this MCP tool catalogue; specialized API policies still apply. Raw PDF contents, signer identities and signed output URLs are not returned by status tools.

OAuth permissions →
PDFHQ logo

PDF tools and document intelligence. Prepare, understand and work with your documents.

© 2026 PDFHQ. All rights reserved.