listing_text_audit — Catalog QA Desk MCP Tool
listing_text_audit
(listing text audit) is one of 7 tools on the
Catalog QA Desk
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call listing_text_audit from your client
- Claude Code Catalog QA Desk listing_text_audit run in your project directory
- Claude Desktop Catalog QA Desk listing_text_audit ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Catalog QA Desk listing_text_audit ~/.cursor/mcp.json
- VS Code Catalog QA Desk listing_text_audit .vscode/mcp.json
- Zed Catalog QA Desk listing_text_audit ~/.config/zed/settings.json
- Windsurf Catalog QA Desk listing_text_audit ~/.codeium/windsurf/mcp_config.json
- Cline Catalog QA Desk listing_text_audit ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Catalog QA Desk listing_text_audit ~/.gemini/settings.json
- Grok Catalog QA Desk listing_text_audit .mcp.json (in your project root)
- ChatGPT Catalog QA Desk listing_text_audit Settings → Connectors → Advanced → Developer mode
- Claude.ai Catalog QA Desk listing_text_audit Settings → Connectors → Add custom connector
- LangChain Catalog QA Desk listing_text_audit pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http catalog-qa https://catalogqa.openkrill.app/mcp
Other tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 10 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.