Skip to main content
The Matcher MCP server exposes Matcher’s reconciliation surface as Model Context Protocol tools. An AI assistant, or any MCP client, can then operate Matcher on your behalf. It can inspect contexts, start reconciliation runs, work exceptions, and pull reports. It has the same permissions you already have.
Matcher is only available if you’ve acquired the Matcher product. Want access? Get in touch with our team to learn more.

​
How it connects

The server speaks Streamable HTTP and exposes one MCP endpoint (POST /mcp). There is no stdio transport: every client connects to it as a remote server over the network. Point any Streamable-HTTP MCP client at the endpoint URL Lerian provides and send your Matcher bearer token on the connection. For example, with Claude Code:
Any MCP client that supports Streamable HTTP works the same way: give it the URL and the Authorization: Bearer <matcher-jwt> header.

​
Auth posture

For Matcher API calls, the server is a credential relay that adds no identity of its own:
  • Bearer token for API calls. Tools that dispatch Matcher API requests fail closed without a bearer token. They forward the client-supplied credential without logging, storing, or echoing it.
  • Local utilities. mcp_ping, matcher_list_operations, and matcher_describe_operation run locally and need no token. mcp_whoami does not call Matcher. It still needs a bearer credential, because it reports that a credential arrived. Without a credential, it returns a tool error.
  • Tenant follows the token for API calls. No API-dispatching tool accepts a tenant parameter. Matcher resolves the tenant from the relayed JWT.
  • No session state. Each request builds a fresh in-memory server.
To check your client configuration, call mcp_whoami with a bearer credential after you connect. It reports only that the credential arrived, never its value.

​
What you can do with it

The server exposes curated tool families for configuration, reconciliation runs, exceptions and disputes, ingestion, and reporting. It also exposes a generic bridge for operations with JSON request bodies. See Matcher MCP tools for the catalog.