run_task_quality_gate — 2ools MCP Tool Mutating
run_task_quality_gate
(run task quality gate) is one of 81 tools on the
2ools
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call run_task_quality_gate from your client
- Claude Code 2ools run_task_quality_gate run in your project directory
- Claude Desktop 2ools run_task_quality_gate ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor 2ools run_task_quality_gate ~/.cursor/mcp.json
- VS Code 2ools run_task_quality_gate .vscode/mcp.json
- Zed 2ools run_task_quality_gate ~/.config/zed/settings.json
- Windsurf 2ools run_task_quality_gate ~/.codeium/windsurf/mcp_config.json
- Cline 2ools run_task_quality_gate ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI 2ools run_task_quality_gate ~/.gemini/settings.json
- Grok 2ools run_task_quality_gate .mcp.json (in your project root)
- ChatGPT 2ools run_task_quality_gate Settings → Connectors → Advanced → Developer mode
- Claude.ai 2ools run_task_quality_gate Settings → Connectors → Add custom connector
- LangChain 2ools run_task_quality_gate pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://2ools.app/mcp
Other tools on this server
- create_public_preview
- list_build_systems
- list_connected_engines
- get_project_engine_workspace
- attach_project_engine_workspace
- register_existing_project
- build_from_conversation
- start_project_on_engine
- refine_project
- get_build
- get_engine_dispatch
- compare_versions
- list_approval_requests
- approve_version
- reject_version
- cancel_build
- get_account_profile
- update_account_profile
- get_project_access
- invite_project_member
- update_project_member_role
- remove_project_member
- revoke_project_invite
- list_projects
- get_project
- get_project_context
- continue_project
- refresh_project_cockpit
- activate_project
- get_project_mission
- get_project_intelligence
- update_project_intelligence
- get_project_discipline
- list_project_engineering_decisions
- answer_project_engineering_decision
- manage_project_discipline
- update_project_mission
- review_project_mission
- manage_work_watchdog
- act_on_project_os_task
- update_living_plan
- render_project_preview
- list_project_agents
- get_agent
- run_project_agent
- get_project_agent_mode
- configure_project_agent_mode
- advance_project_agent_mode
- dispatch_project_work
- get_project_work_dispatch
- cancel_agent_run
- get_project_activity
- wait_for_project_activity
- list_project_feedback
- add_project_feedback
- resolve_project_feedback
- list_project_pins
- add_project_pin
- remove_project_pin
- prepare_version_export
- get_version_share_link
- create_version_share_link
- revoke_version_share_link
- list_artifacts
- get_artifact
- prepare_artifact_upload
- prepare_artifact_download
- list_artifact_approval_requests
- approve_artifact_version
- reject_artifact_version
- get_task_quality_gate
- get_work_handoff
- prepare_work_handoff
- list_work_assignments
- create_work_assignment
- claim_work_assignment
- heartbeat_work_session
- checkpoint_work_session
- submit_work_session
- decide_work_assignment
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.