log_audit_creator — QuassLabs API MCP Tool
log_audit_creator
(log audit creator) is one of 30 tools on the
QuassLabs API
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call log_audit_creator from your client
- Claude Code QuassLabs API log_audit_creator run in your project directory
- Claude Desktop QuassLabs API log_audit_creator ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor QuassLabs API log_audit_creator ~/.cursor/mcp.json
- VS Code QuassLabs API log_audit_creator .vscode/mcp.json
- Zed QuassLabs API log_audit_creator ~/.config/zed/settings.json
- Windsurf QuassLabs API log_audit_creator ~/.codeium/windsurf/mcp_config.json
- Cline QuassLabs API log_audit_creator ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI QuassLabs API log_audit_creator ~/.gemini/settings.json
- Grok QuassLabs API log_audit_creator .mcp.json (in your project root)
- ChatGPT QuassLabs API log_audit_creator Settings → Connectors → Advanced → Developer mode
- Claude.ai QuassLabs API log_audit_creator Settings → Connectors → Add custom connector
- LangChain QuassLabs API log_audit_creator pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http api https://api.quasslabs.com/mcp
Other tools on this server
- alignment_gate
- blm_land_lookup
- diagram_contrast
- humanizer_score
- saas_metrics
- acceptance_criteria_validator
- coverage_check
- defect_triage
- model_advisor
- tool_advisor
- humanize
- dependency_check
- log_analyzer
- ticket_lint
- story_lint
- estimate_sanity
- pr_description_lint
- commit_hygiene
- readability_grade
- regex_lint
- sprint_health
- worklog_guardrail
- uploads
- feedback
- buy_credits
- rate_call
- supply_chain_scan
- describe_diagram
- convert_diagram
This list was read from the server itself, by connecting to it and calling tools/list on 29 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.