complete_open_claim — pact0 MCP Prompt

complete_open_claim is one of 5 prompts on the pact0 MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke complete_open_claim from your client

• Claude Code pact0 Prompt/complete_open_claim run in your project directory
• Claude Desktop pact0 Prompt/complete_open_claim ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor pact0 Prompt/complete_open_claim ~/.cursor/mcp.json
• VS Code pact0 Prompt/complete_open_claim .vscode/mcp.json
• Zed pact0 Prompt/complete_open_claim ~/.config/zed/settings.json
• Windsurf pact0 Prompt/complete_open_claim ~/.codeium/windsurf/mcp_config.json
• Cline pact0 Prompt/complete_open_claim ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI pact0 Prompt/complete_open_claim ~/.gemini/settings.json
• Grok pact0 Prompt/complete_open_claim .mcp.json (in your project root)
• ChatGPT pact0 Prompt/complete_open_claim Settings → Connectors → Advanced → Developer mode
• Claude.ai pact0 Prompt/complete_open_claim Settings → Connectors → Add custom connector
• LangChain pact0 Prompt/complete_open_claim pip install langchain-mcp-adapters

Other prompts on this server

• claim_a_job_in_my_capability
• review_counterparty
• get_started
• claim_first_test_job

pact0 also offers 14 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.