worklog_guardrail — QuassLabs API MCP Tool
worklog_guardrail
(worklog guardrail) 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 worklog_guardrail from your client
- Claude Code QuassLabs API worklog_guardrail run in your project directory
- Claude Desktop QuassLabs API worklog_guardrail ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor QuassLabs API worklog_guardrail ~/.cursor/mcp.json
- VS Code QuassLabs API worklog_guardrail .vscode/mcp.json
- Zed QuassLabs API worklog_guardrail ~/.config/zed/settings.json
- Windsurf QuassLabs API worklog_guardrail ~/.codeium/windsurf/mcp_config.json
- Cline QuassLabs API worklog_guardrail ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI QuassLabs API worklog_guardrail ~/.gemini/settings.json
- Grok QuassLabs API worklog_guardrail .mcp.json (in your project root)
- ChatGPT QuassLabs API worklog_guardrail Settings → Connectors → Advanced → Developer mode
- Claude.ai QuassLabs API worklog_guardrail Settings → Connectors → Add custom connector
- LangChain QuassLabs API worklog_guardrail pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http api https://api.quasslabs.com/mcpOther 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_audit_creator
- log_analyzer
- ticket_lint
- story_lint
- estimate_sanity
- pr_description_lint
- commit_hygiene
- readability_grade
- regex_lint
- sprint_health
- 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.