Skip to main content
The Matcher MCP server exposes a curated tool surface — one ergonomic, validated tool per common operation — plus a generic trio that can reach any operation in the Matcher API. Tools follow a family_action naming convention (for example, context_list or match_run_start), so related tools share a prefix. This page lists the families with representative examples; it is deliberately not an exhaustive catalog. Connect a client and list the available tools to see the full surface for your version.

Curated families


CategoryFamiliesWhat they coverRepresentative tools
Configurationcontext_*, source_*, field_map_*Reconciliation contexts, their data sources, and the field maps that normalize incoming records.context_create, context_setup_progress, source_list, field_map_update
Matching rulesmatch_rule_*The match rules a context applies, including their evaluation order.match_rule_create, match_rule_reorder
Feesfee_schedule_*, fee_rule_*Expected-fee schedules and the rules attached to them, including simulation before rollout.fee_schedule_simulate, fee_rule_create
Reconciliation runsmatch_run_*Driving reconciliation — start a run, follow its progress, inspect the resulting match groups.match_run_start, match_run_groups
Exceptionsexception_*Working unmatched transactions — listing, history and comments, per-exception actions, and bulk operations.exception_list, exception_force_match, exception_bulk_resolve
Disputesdispute_*The dispute lifecycle for contested exceptions.dispute_submit_evidence, dispute_close
Ingestioningestion_*The import lifecycle — upload data, inspect jobs and per-row errors, search and ignore transactions.ingestion_upload, ingestion_job_errors_list
Reportingdashboard_*, report_*Dashboard aggregates and focused slices, plus report reads, counts, and exports.dashboard_match_rate, report_summary, report_export_unmatched

Generic trio


When a curated tool doesn’t cover an operation, the generic trio reaches the entire Matcher API surface:
ToolPurpose
matcher_list_operationsList every operation the connected Matcher exposes.
matcher_describe_operationDescribe one operation — parameters, request body schema, and responses.
matcher_invokeAssemble, validate, and dispatch any operation with your relayed credentials.
Curated tools and matcher_invoke share one HTTP client and one token relay, so authorization and error mapping behave identically on both surfaces — Matcher errors come back as RFC 9457 problem details either way.

Utilities


ToolPurpose
mcp_pingConfirm the server is reachable.
mcp_whoamiReport whether your client’s bearer credential arrived — presence only, never the value.