> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# Matcher MCP tools

> The tool families the Matcher MCP server exposes — curated tools by category, plus generic discovery and JSON-relay tools for Matcher operations.

The Matcher MCP server exposes a **curated** tool surface — ergonomic, validated tools for common operations — plus a **generic discovery pair** and a **JSON relay** for indexed operations. Curated 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

***

| Category                | Families                               | What they cover                                                                                             | Representative tools                                                          |
| ----------------------- | -------------------------------------- | ----------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
| **Configuration**       | `context_*`, `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 rules**      | `match_rule_*`                         | The match rules a context applies, including their evaluation order.                                        | `match_rule_create`, `match_rule_reorder`                                     |
| **Fees**                | `fee_schedule_*`, `fee_rule_*`         | Expected-fee schedules and the rules attached to them, including simulation before rollout.                 | `fee_schedule_simulate`, `fee_rule_create`                                    |
| **Reconciliation runs** | `match_run_*`                          | Driving reconciliation — start a run, follow its progress, inspect the resulting match groups.              | `match_run_start`, `match_run_groups`                                         |
| **Exceptions**          | `exception_*`                          | Working unmatched transactions — listing, history and comments, per-exception actions, and bulk operations. | `exception_list`, `exception_force_match`, `exception_bulk_resolve`           |
| **Disputes**            | `dispute_*`                            | The dispute lifecycle for contested exceptions.                                                             | `dispute_submit_evidence`, `dispute_close`                                    |
| **Ingestion**           | `ingestion_*`                          | The import lifecycle — upload data, inspect jobs and per-row errors, search and ignore transactions.        | `ingestion_upload`, `ingestion_job_errors_list`                               |
| **Reporting**           | `dashboard_*`, `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 the operation you need, use the generic tools to inspect the API contract embedded when the server starts and, when the operation accepts a JSON body (or needs no body), invoke it:

| Tool                         | Purpose                                                                                                                                                                                            |
| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `matcher_list_operations`    | List the operations in the embedded OpenAPI index built when the MCP server starts; optionally filter by tag. It does not call Matcher or require a credential.                                    |
| `matcher_describe_operation` | Describe one indexed operation — its method, templated path, path and query parameters, summary, and, when present, a dereferenced JSON request-body schema. It does not include response schemas. |
| `matcher_invoke`             | Assemble, validate, and dispatch an indexed operation with path/query parameters and, where applicable, a JSON request body, using your relayed credentials.                                       |

`matcher_invoke` does not support multipart or raw-binary bodies. Use an applicable curated tool or call the Matcher HTTP API directly for those operations. Curated tools and `matcher_invoke` share the same HTTP-client contract, fail-closed token relay, and [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457) error mapping. For Matcher API failures, both return structured tool errors that preserve the problem's status, title, detail, and code.

## Utilities

***

| Tool         | Purpose                                                                                                                             |
| ------------ | ----------------------------------------------------------------------------------------------------------------------------------- |
| `mcp_ping`   | Confirm the server is reachable.                                                                                                    |
| `mcp_whoami` | Report whether your client's bearer credential arrived — presence only, never the value; returns a tool error when none is present. |