dispute_case_builder — mcp MCP Tool
dispute_case_builder
(dispute case builder) is one of 87 tools on the
mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call dispute_case_builder from your client
- Claude Code mcp dispute_case_builder run in your project directory
- Claude Desktop mcp dispute_case_builder ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor mcp dispute_case_builder ~/.cursor/mcp.json
- VS Code mcp dispute_case_builder .vscode/mcp.json
- Zed mcp dispute_case_builder ~/.config/zed/settings.json
- Windsurf mcp dispute_case_builder ~/.codeium/windsurf/mcp_config.json
- Cline mcp dispute_case_builder ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI mcp dispute_case_builder ~/.gemini/settings.json
- Grok mcp dispute_case_builder .mcp.json (in your project root)
- ChatGPT mcp dispute_case_builder Settings → Connectors → Advanced → Developer mode
- Claude.ai mcp dispute_case_builder Settings → Connectors → Add custom connector
- LangChain mcp dispute_case_builder pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://mcp.medigami.com/public/mcpOther tools on this server
- scan_bill_for_errors
- generate_appeal_letter
- optimize_prescription
- analyze_glp1_pathways
- verify_attestation
- watch_appeal_outcome
- watch_claim_denial
- format_citation
- submit_denial_letter
- verify_mcp_response
- format_medigami_citation
- estimate_appeal_success
- resolve_denial
- maximize_recovery
- explain_appeal_success
- negotiate_bill_script
- batch_scan_bills
- lookup_icd10
- lookup_cpt
- lookup_npi
- verify_dea_authorization
- lookup_provider_taxonomy
- resolve_codes
- code_conflict_detector
- fair_price_estimator
- price_variance_analyzer
- claim_consistency_checker
- bundling_violation_detector
- appeal_success_predictor
- generate_appeal_letter_v2
- negotiation_strategy_generator
- insurance_response_interpreter
- settlement_optimizer
- patient_cost_forecaster
- insurance_plan_optimizer
- cash_vs_insurance_optimizer
- financial_risk_exposure_model
- cpt_to_icd_mapper
- icd_to_cpt_mapper
- code_bundle_validator
- unbundling_detector
- cash_price_estimator
- zip_based_price_variance
- regional_price_benchmark
- specialty_price_benchmark
- inflation_adjusted_price_model
- deductible_impact_calculator
- coinsurance_simulator
- copay_model
- billing_charge_vs_allowed_delta
- price_anomaly_detector
- overpriced_service_detector
- market_price_distribution_model
- price_outlier_detector
- procedure_cost_decomposition
- price_recommendation_engine
- claim_duplicate_line_detector
- denial_reason_classifier
- appeal_argument_generator
- denial_response_builder
- evidence_pack_generator
- claim_rebuttal_generator
- appeal_escalation_path_finder
- payer_specific_appeal_templates
- denial_code_explainer
- claim_reconsideration_builder
- supporting_document_selector
- out_of_pocket_optimizer
- financial_exposure_model
- procedure_affordability_ranker
- treatment_cost_comparator
- bill_shock_predictor
- payment_plan_optimizer
- financial_assistance_finder
- patient_cost_explainer
- healthcare_budget_forecaster
- medical_spending_analyzer
- insurance_value_optimizer
- patient_financial_risk_score
- decode_denial
- get_appeal_deadline
- get_venue
- medigami_odds
- medigami_roast
- medigami_deadline
- medigami_rate
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.