chieflab_use_manual_fallback — ChiefLab MCP Tool
chieflab_use_manual_fallback
(chieflab use manual fallback) is one of 45 tools on the
ChiefLab
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call chieflab_use_manual_fallback from your client
- Claude Code ChiefLab chieflab_use_manual_fallback run in your project directory
- Claude Desktop ChiefLab chieflab_use_manual_fallback ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ChiefLab chieflab_use_manual_fallback ~/.cursor/mcp.json
- VS Code ChiefLab chieflab_use_manual_fallback .vscode/mcp.json
- Zed ChiefLab chieflab_use_manual_fallback ~/.config/zed/settings.json
- Windsurf ChiefLab chieflab_use_manual_fallback ~/.codeium/windsurf/mcp_config.json
- Cline ChiefLab chieflab_use_manual_fallback ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ChiefLab chieflab_use_manual_fallback ~/.gemini/settings.json
- Grok ChiefLab chieflab_use_manual_fallback .mcp.json (in your project root)
- ChatGPT ChiefLab chieflab_use_manual_fallback Settings → Connectors → Advanced → Developer mode
- Claude.ai ChiefLab chieflab_use_manual_fallback Settings → Connectors → Add custom connector
- LangChain ChiefLab chieflab_use_manual_fallback pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http chieflab https://api.chieflab.io/api/mcp
Other tools on this server
- chieflab_help
- chieflab_get_users_after_build
- chieflab_connect_provider
- chieflab_retry_blocked_action
- chieflab_set_company_profile
- chieflab_get_company_profile
- chieflab_list_specialists
- chieflab_request_specialist
- chieflab_force_measurement_due
- chieflab_persistence_health
- chieflab_query_proof_ledger
- chieflab_set_publishing_targets
- chieflab_get_publishing_targets
- chieflab_suggest_next_move
- chieflab_create_next_move_action
- chieflab_regenerate_visual_asset
- chieflab_record_manual_metrics
- chieflab_measure_reddit
- chieflab_measure_hacker_news
- chieflab_review_visual_asset
- chieflab_execute_approved_action
- chieflab_check_measurement_due
- chieflab_skip_next_move
- chieflab_mark_action_done
- chieflab_record_manual_publish
- chieflab_connector_status
- chieflab_signup_workspace
- chieflab_launch_product
- chieflab_redraft
- chieflab_set_provider_key
- chieflab_inbox
- chieflab_status
- chieflab_boot
- chieflab_verify_install
- chieflab_brain_summary
- chieflab_search_capabilities
- chieflab_get_capability
- chieflab_create_work_request
- chieflab_approve_action
- chieflab_continue_launch_loop
- chieflab_post_launch_review
- chieflab_prepare_next_move
- chieflab_publish_approved_post
- chieflab_send_approved_email
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.