Senzing MCP MCP server

The Senzing MCP server provides AI assistants with entity resolution capabilities through the Model Context Protocol. It offers 13 tools and 31 prompts for data mapping, SDK code generation, ER reporting and visualization, documentation search, error troubleshooting, and sample data access. The server works entirely from pre-fetched documentation and indexed content, never connecting to live Senzing instances or handling PII.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Senzing

MCP endpoint (Streamable HTTP)

https://mcp.senzing.com/mcp

Vendor documentation

What you can do with it

Map source data fields to Senzing format with fuzzy matching
Generate SDK scaffold code for Python, Java, C#, or Rust
Search documentation and explain error codes
Access sample datasets like Las Vegas or London for demos

Tools advertised by the last live check:

analyze_record
download_resource
explain_error_code
find_examples
generate_scaffold
get_capabilities
get_sample_data
get_sdk_reference
mapping_workflow
reporting_guide
sdk_guide
search_docs
submit_feedback

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http senzing-mcp https://mcp.senzing.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add senzing-mcp --url https://mcp.senzing.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable senzing-mcp in your MCP settings.

Cursor configuration

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

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "senzing-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.senzing.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start senzing-mcp and inspect its tools.

VS Code configuration

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

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http senzing-mcp https://mcp.senzing.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

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

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "senzing-mcp": {
      "serverUrl": "https://mcp.senzing.com/mcp"
    }
  }
}

See all 1,583

Do you run Senzing MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing