mcp-entity-resolver
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve_entityA | Resolve a messy entity name or partial record into a canonical match across known systems. Returns best match + confidence. Use this BEFORE any write or action on customer/account/vendor data. |
| fuzzy_match_recordsB | Compare two lists of records and return ranked matches. Ideal for reconciling Salesforce accounts vs SAP customers or ServiceNow CIs. |
| register_entityA | Register a known good entity into the resolver memory so future lookups can use it. Call this after a human confirms a match. |
| check_consistencyA | Check whether the same logical entity has conflicting attributes across systems (e.g. different addresses or status). |
| list_registered_entitiesA | List currently registered entities (useful for debugging agent memory). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct role: resolving single entities, batch matching, consistency checking, registration, and listing. No two tools overlap in purpose, making selection unambiguous.
All tool names follow a consistent verb_noun pattern in snake_case, such as check_consistency, resolve_entity, fuzzy_match_records, register_entity, list_registered_entities. The naming is predictable and uniform.
Five tools is well-scoped for an entity resolution server, covering lookup, reconciliation, consistency checks, and memory management without unnecessary bulk.
The core lifecycle of entity resolution is covered: resolve, reconcile, check consistency, register, and list. The only minor gap is lack of an explicit delete/unregister tool, but this is not essential for the primary workflow.