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 credits, or switch between live and test API keys without hand-writing REST calls.Documentation Index
Fetch the complete documentation index at: https://docs.capout.ai/llms.txt
Use this file to discover all available pages before exploring further.
Install
CapOut MCP is exposed as a hosted Streamable HTTP endpoint:Tool map
capout_process_pdf: process one PDF frompdf,url,file_base64, orfile_pathcapout_create_upload_url: create a short-lived staged upload link for local CLI or workspace PDFscapout_process_staged_upload: submit a staged local upload for processingcapout_document_status: get a one-shot status check for a documentcapout_wait_for_document: wait for progress and completion inside the agent UIcapout_credits: inspect remaining creditscapout_xactnet_addresses: list saved recipient addressescapout_create_xactnet_address: save a new recipient addresscapout_delete_xactnet_address: remove a saved recipient addresscapout_api_keys: list available live and test API keyscapout_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.
- Use Status and Waiting after every accepted upload until the document reaches a terminal state.