DocPurify MCP Server

Use DocPurify from any MCP client that supports stdio servers.

What you need

• Node.js 18 or newer.
• A DocPurify account.
• A DocPurify MCP key from the MCP page in the web app.

MCP client config

Copy this into your MCP client config and replace only DOCPURIFY_MCP_KEY.

{
  "mcpServers": {
    "docpurify": {
      "command": "npx",
      "args": ["-y", "@docpurify/mcp-server"],
      "env": {
        "DOCPURIFY_MCP_KEY": "dp_your_mcp_key"
      }
    }
  }
}

Restart the client after saving the config. The server uses https://api.docpurify.com by default.

First request to try

Ask your AI client:

Check my DocPurify workspace status.

If the key is correct, the client should call get_workspace_overview.

Available tools

• get_workspace_overview: Read credits, storage usage, recent jobs, alerts, and suggested next actions.
• submit_document_for_processing: Submit an already uploaded file by file_id.
• list_document_jobs: List recent document jobs.
• get_document_job: Check one job's status and progress.
• get_document_result: Fetch Markdown results and download links for a completed job.
• cancel_document_job: Cancel a non-terminal job.
• delete_document_job: Delete a terminal job and reclaim storage.

MCP does not upload local files directly yet. Upload the file in DocPurify first, then use the returned file_id.

Environment variables

• DOCPURIFY_MCP_KEY: MCP API key created from the DocPurify MCP page. Required.
• DOCPURIFY_API_BASE: Optional DocPurify API base URL override for staging, private deployment, or enterprise domains. Defaults to https://api.docpurify.com.
• DOCPURIFY_MCP_TIMEOUT_SECONDS: Optional request timeout. Defaults to 30.