Skip to main content
CapOut MCP is a hosted remote MCP server. Use the Streamable HTTP endpoint below, not the bare domain root:

​
Copy to Codex

Run this in your terminal to add CapOut MCP to Codex:
Codex starts the login flow automatically when the server needs authentication. Use /mcp inside Codex to confirm the server is connected.

​
Install with add-mcp

For clients supported by the add-mcp installer, this command can detect installed coding agents and configure CapOut MCP for them:
Use --all to install to all detected agents, -g for a global install across projects, or -y to skip the confirmation prompt:

​
Claude Code

Anthropic documents remote HTTP MCP servers with claude mcp add --transport http <name> <url>.
If Claude Code asks you to authenticate the server, use /mcp inside the session and complete the sign-in flow there.

​
Gemini CLI

Gemini CLI documents remote HTTP MCP servers with gemini mcp add --transport http <name> <url>.
If Gemini marks the server as needing authentication, run this inside Gemini CLI:

​
OpenCode

OpenCode documents remote MCP servers in opencode.json or opencode.jsonc. For a user-wide setup, put this in ~/.config/opencode/opencode.json. For a project-only setup, put it in opencode.json at your project root.
If OpenCode needs authentication, or if you want to trigger it manually:

​
GitHub Copilot CLI

GitHub documents both interactive /mcp add setup and a non-interactive copilot mcp add command. The CLI reference also documents --tools for enabling all tools from the remote server.
If Copilot CLI shows needs-auth, run this inside an interactive Copilot CLI session:
If you prefer config instead of a command, GitHub documents ~/.copilot/mcp-config.json:

​
What the agent can do after install

  • Process PDFs into Xactimate exports
  • Poll export status until completion
  • Check remaining CapOut claims
  • List, save, assign profile codes, and delete XactNet recipient addresses
  • Inspect and switch between live and test API keys

​
How CapOut chooses the upload path

CapOut MCP is hosted remotely. That means it cannot read your local /Users/... paths, workspace paths, or other files from your machine directly. The MCP uses different tools depending on where the PDF lives.

​
Attachment, HTTPS URL, or inline bytes

When the client can provide a PDF attachment, a public https:// PDF URL, or inline base64 bytes, the agent uses capout_process_pdf.

​
Local CLI or workspace PDF

When the PDF lives on the local machine or workspace, the agent should not send a local path like /Users/... to the hosted server. Instead it should:
  1. Call capout_create_upload_url
  2. Run the returned curl_command locally
  3. Call capout_process_staged_upload with xn_address and profile_code

​
API key examples

Use capout_api_keys to see the current key and any other available live or test keys. Use capout_select_api_key to switch when needed. Selecting a key updates which stored key is marked mcp=true for MCP-authenticated requests. The model does not receive raw API key values. If no CapOut API key exists yet, create one in the CapOut app:

​
Starter prompts