file_a_claim — Coverage Cat MCP Tool
file_a_claim
(file a claim) is one of 23 tools on the
Coverage Cat
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call file_a_claim from your client
- Claude Code Coverage Cat file_a_claim run in your project directory
- Claude Desktop Coverage Cat file_a_claim ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Coverage Cat file_a_claim ~/.cursor/mcp.json
- VS Code Coverage Cat file_a_claim .vscode/mcp.json
- Zed Coverage Cat file_a_claim ~/.config/zed/settings.json
- Windsurf Coverage Cat file_a_claim ~/.codeium/windsurf/mcp_config.json
- Cline Coverage Cat file_a_claim ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Coverage Cat file_a_claim ~/.gemini/settings.json
- Grok Coverage Cat file_a_claim .mcp.json (in your project root)
- ChatGPT Coverage Cat file_a_claim Settings → Connectors → Advanced → Developer mode
- Claude.ai Coverage Cat file_a_claim Settings → Connectors → Add custom connector
- LangChain Coverage Cat file_a_claim pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http insurance https://www.coveragecat.com/api/consumer/mcp
Other tools on this server
- umbrella_consumer_prefill
- homeowners_consumer_prefill
- consumer_intake_issues
- consumer_intake_patch
- umbrella_consumer_select
- umbrella_consumer_bind
- umbrella_consumer_attach
- umbrella_consumer_payment
- umbrella_consumer_policy
- umbrella_consumer_service
- homeowners_consumer_select
- homeowners_consumer_bind
- homeowners_consumer_policy
- homeowners_consumer_service
- home_calculator
- umbrella_calculator
- auto_estimates
- collision_and_comprehensive_coverage
- homeowners_agent_finder
- docs_list_topics
- docs_search
- docs_get_resource
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.