triage_pdf_contract — ClausePilot MCP Tool
triage_pdf_contract
(triage pdf contract) is one of 18 tools on the
ClausePilot
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call triage_pdf_contract from your client
- Claude Code ClausePilot triage_pdf_contract run in your project directory
- Claude Desktop ClausePilot triage_pdf_contract ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ClausePilot triage_pdf_contract ~/.cursor/mcp.json
- VS Code ClausePilot triage_pdf_contract .vscode/mcp.json
- Zed ClausePilot triage_pdf_contract ~/.config/zed/settings.json
- Windsurf ClausePilot triage_pdf_contract ~/.codeium/windsurf/mcp_config.json
- Cline ClausePilot triage_pdf_contract ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ClausePilot triage_pdf_contract ~/.gemini/settings.json
- Grok ClausePilot triage_pdf_contract .mcp.json (in your project root)
- ChatGPT ClausePilot triage_pdf_contract Settings → Connectors → Advanced → Developer mode
- Claude.ai ClausePilot triage_pdf_contract Settings → Connectors → Add custom connector
- LangChain ClausePilot triage_pdf_contract pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http clausepilot https://clausepilot-pearl.vercel.app/mcpOther tools on this server
- get_clausepilot_payment_info
- list_clausepilot_paid_tools
- analyze_contract_risk
- extract_renewal_deadline
- find_contract_penalties
- extract_contract_obligations
- summarize_contract_for_agents
- triage_contract
- triage_contract_batch_10
- scan_contract_portfolio_50
- scan_contract_portfolio_200
- compare_contract_risk
- review_vendor_contract_risk
- check_saas_terms
- check_nda_clauses
- extract_employment_terms
- extract_payment_terms
This list was read from the server itself, by connecting to it and calling tools/list on 6 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.