Skip to main content
CapOut MCP exposes the CapOut document-processing workflow as agent tools. The CapOut MCP is hosted remotely, so local machine and workspace PDFs use the staged upload flow rather than direct filesystem reads. Use it when you want an agent to process PDFs, manage saved XactNet delivery addresses, inspect claims, or switch between live and test API keys without hand-writing REST calls.

​
Install

CapOut MCP is exposed as a hosted Streamable HTTP endpoint. For Codex, install it with:
The endpoint is:
For copyable setup examples in Codex, npx add-mcp, Claude Code, Gemini CLI, OpenCode, and GitHub Copilot CLI, see MCP Installation.

​
Tool map

  • capout_process_pdf: process one PDF from pdf, url, file_base64, or file_path
  • capout_create_upload_url: create a short-lived staged upload link for local CLI or workspace PDFs
  • capout_process_staged_upload: submit a staged local upload for processing
  • capout_document_status: get a one-shot status check for a document
  • capout_wait_for_document: wait for progress and completion inside the agent UI
  • capout_claims: inspect remaining claims
  • capout_xactnet_addresses: list saved recipient addresses
  • capout_create_xactnet_address: save a new recipient address
  • capout_update_xactnet_address_profile: assign profile_code on a saved address
  • capout_delete_xactnet_address: remove a saved recipient address
  • capout_api_keys: list available live and test API keys
  • capout_select_api_key: switch the active API key

​
Choose the right workflow

  • Use Process PDFs when the agent has an attachment, a public HTTPS PDF URL, or inline base64.
  • Use Staged Uploads when the PDF lives on the local machine or workspace.
  • Process tools require both xn_address and profile_code.
  • Use Status and Waiting after every accepted upload until the document reaches a terminal state.

​
Common prompts

​
Next steps