Senzing

Senzing MCP Server

Entity resolution for Identity Intelligence: dedupe, match, and link people and company records across systems. Know who is who. Reveal hidden relationships.

Install · What you can ask · Tools · Prompts · Privacy and terms · Questions and feedback

The Senzing® MCP server is a forward-deployed engineer in a box: ask it anything about Senzing. Every answer is grounded in Senzing's own documentation and indexed code rather than model training data. Use it to deduplicate lists, match or merge records across sources, screen against watchlists, and produce the resolved entities that golden records for MDM and customer 360 are built from.

Because it carries the full runbook, you don't drive it one step at a time. Hand your AI assistant a few unmapped data files and describe what you want, and it can map your sources, deploy and load Senzing, resolve and analyze the data, and build an interactive explorer over the results. What is normally a multi-week integration becomes an afternoon, with no entity-resolution background required.

You just ask. Then start answering who is who and who is related to whom, or build an entity-resolved knowledge graph that surfaces the connections nobody declared. Every resolution carries its evidence: why two records came together, or why they didn't. Your assistant can surface that explanation for any match you question.

Install

Endpoint: https://mcp.senzing.com/mcp (Streamable HTTP, no authentication) · Registry name: com.senzing/mcp · The hosted server is free to use; Senzing software is licensed separately.

The buttons above add the server in one click (Claude through its Connectors Directory). For other clients:

VS Code — .vscode/mcp.json

{
  "servers": {
    "senzing": {
      "type": "http",
      "url": "https://mcp.senzing.com/mcp"
    }
  }
}

Cursor and Kiro — mcp.json

{
  "mcpServers": {
    "senzing": {
      "url": "https://mcp.senzing.com/mcp"
    }
  }
}

stdio-only clients — via mcp-remote

{
  "mcpServers": {
    "senzing": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.senzing.com/mcp"]
    }
  }
}

Codex — ~/.codex/config.toml

[mcp_servers.senzing]
url = "https://mcp.senzing.com/mcp"

Tip: for the best experience, use an agentic coding client (Claude Code, Codex, Gemini CLI, Cursor); if your environment restricts network access, allowlist mcp.senzing.com. Mapping your own data and running Senzing need an assistant that can run code; questions, documentation search and SDK code work in any client.

What you can ask

• "Match these payment records to my customers and show me which ones didn't match."
• "Dedupe this list of people and show me the duplicates it found."
• "Here are three customer files from different systems. Build me a demo that finds the same people across them and lets me explore the matches."
• "Build me a service that matches incoming payment records to my customer master as they arrive."
• "How would entity resolution help with my problem, and what would it cost?"

Tools

Each piece is also available on its own: SDK code in Python, Java and C# (official SDKs) and Rust and TypeScript/Node.js (community SDKs), installation and deployment, error troubleshooting, V3→V4 migration, and pricing and ROI.

Prompts

The server also ships 31 ready-made prompts: workflow templates your client can offer as slash commands or menu items. A few of them:

Ask your assistant to list the Senzing prompts to see them all.

More from Senzing

Privacy and terms

The hosted server has its own privacy policy. In short:

• The server needs no live Senzing instance and no authentication. Your data files never leave your machine: mapping and resolution run locally, and only the tool arguments you send (field names, settings, questions) reach this server.
• Senzing is a headless developer library your assistant deploys locally in your environment. Mapping and resolution run there, never on Senzing's servers, and Senzing contains only the data you load into it.
• Do not send personal data, credentials or other sensitive information in prompts or tool arguments. Tool calls and their parameters may be logged.
• The hosted server is provided AS-IS, without warranty or support commitment. The server also exposes these terms as the senzing://terms-of-service resource.

Questions and feedback

Use senzing.com/contact or <support@senzing.com>, or ask your assistant to use submit_feedback.

See LICENSE.