Skip to content

Doc2X MCP: Claude Code

Back: Doc2X MCP Guide

What You Need

  • Node.js (LTS recommended) and npx
  • DOC2X_API_KEY (looks like YOUR_DOC2X_API_KEY)
  • (Optional) other Doc2X MCP config (for example DOC2X_BASE_URL / timeouts / polling): see “Environment Variables” in the Doc2X MCP Guide
  • (Optional) proxy env (HTTPS_PROXY / HTTP_PROXY)

Add MCP Configuration

Run in your terminal:

shell
claude mcp add --transport stdio doc2x -e DOC2X_API_KEY=YOUR_DOC2X_API_KEY -- npx -y @noedgeai-org/doc2x-mcp@0.1.5

Check MCP

Open the MCP list and confirm the doc2x server is loaded and available (you can expand it to see the tool list).

Check MCP

Use doc2x-mcp

Start with a small PDF to validate the end-to-end flow:

  • Ensure the file is in the current directory (or provide an accessible path)
  • In chat, explicitly ask the model to call the doc2x MCP server to parse/export

Example prompts:

  • Use doc2x-mcp to parse ./paper.pdf and export the result.
  • Use doc2x-mcp to parse ./paper.pdf, and paste the exported file path when done.

Use doc2x-mcp

Exported Result

Troubleshooting

  • If the server fails to start, try running npx -y @noedgeai-org/doc2x-mcp@0.1.5 directly in your terminal to isolate network/registry issues.
  • If the API key doesn’t take effect, double-check DOC2X_API_KEY injection and client logs.

Version, paths, and completion checks

This page configures MCP 0.1.5. Existing screenshots illustrate client steps; labels may change with client versions. Use Node.js 18+ and obtain an API Key from the Open Platform. YOUR_DOC2X_API_KEY is a placeholder: keep the real value in private local configuration, not chat or version control.

After connection, confirm the tool list includes doc2x_parse_pdf_submit and export/download tools. Supply an absolute input path and output directory, authorize one submission, retain uid, and wait for parsing success before export. Follow the complete tool sequence and prompt.

Ask for actual saved paths, then open the result and check images, formulas, and page order. A progress screenshot is not export-success evidence. On timeout query the original uid. Input paths must be readable on the MCP host and the output directory writable. Real parsing consumes platform quota; a connected server alone is not task authorization.