manage-redo-queue — Senzing MCP Prompt
manage-redo-queue
is one of 31 prompts on the
Senzing
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke manage-redo-queue from your client
- Claude Code Senzing Prompt/manage-redo-queue run in your project directory
- Claude Desktop Senzing Prompt/manage-redo-queue ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Senzing Prompt/manage-redo-queue ~/.cursor/mcp.json
- VS Code Senzing Prompt/manage-redo-queue .vscode/mcp.json
- Zed Senzing Prompt/manage-redo-queue ~/.config/zed/settings.json
- Windsurf Senzing Prompt/manage-redo-queue ~/.codeium/windsurf/mcp_config.json
- Cline Senzing Prompt/manage-redo-queue ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Senzing Prompt/manage-redo-queue ~/.gemini/settings.json
- Grok Senzing Prompt/manage-redo-queue .mcp.json (in your project root)
- ChatGPT Senzing Prompt/manage-redo-queue Settings → Connectors → Advanced → Developer mode
- Claude.ai Senzing Prompt/manage-redo-queue Settings → Connectors → Add custom connector
- LangChain Senzing Prompt/manage-redo-queue pip install langchain-mcp-adapters
Other prompts on this server
- analyze-data-quality
- architect-cloud-deployment
- build-a-demo
- build-entity-explorer-ui
- build-reporting-dashboard
- build-robust-error-handling
- build-scalable-loader
- build-sdk-integration
- choose-a-database
- delete-and-erase
- deployment-options
- design-er-pipeline
- evaluate-er-results
- explain-entity-resolution
- how-would-senzing-fit
- install-senzing
- map-data-source
- migrate-v3-to-v4
- plan-a-poc
- plan-replication-and-ha
- platform-integration
- realtime-integration
- request-eval-license
- resolve-and-search
- run-entity-resolution
- senzing-roi
- show-me-er-in-action
- steward-entities
- troubleshoot-error
- why-senzing
Senzing also offers 2 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.