Skip to main content
capout_process_pdf is the primary MCP tool for single-document processing.

Required arguments

  • Always send xn_address
  • Always send profile_code: 5L for Carrier or 8D for Contractor
  • Send exactly one of:
    • pdf
    • url
    • file_base64
    • file_path
  • When using file_base64, also send file_name
When using file_base64, keep the PDF at or below 50 MiB. For local or workspace PDFs on a hosted MCP, use Staged Uploads, which supports PDFs up to 50 MiB. For the public CapOut MCP, the practical inputs are pdf, url, and file_base64. The MCP is hosted remotely and cannot read your local machine paths directly.

Use the right source type

  • Use pdf for ChatGPT-style file attachments that include download_url and file_id
  • Use url for a public https:// PDF URL
  • Use file_base64 when the client has bytes but not a URL and the inline payload stays within the 50 MiB limit
  • Use file_path only for a path that already exists on the CapOut MCP server itself. Do not send your local /Users/... or workspace path here.
CapOut MCP is hosted remotely and cannot read your local filesystem. For local workspace PDFs, use Staged Uploads.

Example: attached PDF

Example: HTTPS PDF URL

Example: inline base64

Successful response

The MCP intentionally returns only the handoff needed for the next step:

What to do next

After the document is accepted, keep polling until the export reaches a terminal state: