Ask Senzing
v0.6.5Ask anything about Senzing — products, the SDK, entity-resolution concepts, configuration, and error codes — and it politely declines everything else.
Try a real Senzing question
The same assistant is the ✦ Ask Senzing button on docs.senzing.com. It searches the docs live and cites its sources.
Grounded in live Senzing MCP calls
Every answer is grounded in the Senzing MCP as the single source of truth. There is no cached or derived index — the assistant produces each answer from live MCP calls made at the moment you ask.
Scope is structural, not just prompt-based. The assistant can reach nothing but the Senzing MCP — no web search, no other data source. An off-topic question surfaces nothing relevant, so the assistant declines and points you back to what it can help with.
You ask a question
About products, the SDK, entity-resolution concepts, configuration, or error codes.
The model chooses MCP tools
It drives the MCP's tools agentically: it chooses which tools to call, refines and chains those calls. The one tool that sends anything,
submit_feedback(evaluation-license requests and feedback), runs only after you confirm exactly what will be sent.search_docsexplain_error_codefind_examplesget_sdk_referencesdk_guidereporting_guidesubmit_feedbackLive calls return the docs
Each call runs against the Senzing MCP at the moment you ask; there is no cached answer and no separate index.
A grounded answer that cites the docs
It writes the answer from what the calls returned and links the docs pages those calls surfaced.
Use the Senzing MCP with your own LLM
The same Senzing knowledge that powers this assistant is available as a public MCP server. Connect it to your own LLM or agent for accurate, up-to-date Senzing answers grounded in the same source of truth.
Streamable HTTP transport. It works via the Anthropic Messages API mcp_servers connector and any MCP-aware client (Claude Desktop and other MCP clients). No authentication required.
Ask your AI assistant
To get started, ask your AI assistant:
"Add the Senzing MCP server at https://mcp.senzing.com/mcp"
Add it as an MCP server
{
"mcpServers": {
"senzing": {
"type": "url",
"url": "https://mcp.senzing.com/mcp"
}
}
}
Tool-first rule
Tell your LLM to call get_capabilities first, and to treat the Senzing MCP as the exclusive source of truth for anything Senzing.
Training data is often wrong or outdated for Senzing — wrong attribute names, wrong method signatures, wrong base images — so the model should use the MCP's tools and never supplement or "improve" their results with prior knowledge.
What you get
get_capabilitiesDiscover the full toolset and workflows firstsearch_docsPrimary docs / pricing / architecture / deployment retrievalexplain_error_codeLook up Senzing error codes and meaningsfind_examplesWorking code from indexed GitHub reposget_sdk_referenceV4 method signatures & per-binding argument types, flags, V3→V4 migrationsdk_guideInstall / configure / load / export across platformsgenerate_scaffoldGenerate correct SDK initialization & scaffoldingmapping_workflowMap source JSON to the Senzing entity modelreporting_guideER reporting & visualization patterns
Provided as-is
Have a Senzing question?
Open the assistant and ask — it searches the docs live and cites its sources.