start_fix_run — Fictura MCP Tool Mutating
start_fix_run
(start fix run) is one of 87 tools on the
Fictura
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call start_fix_run from your client
- Claude Code Fictura start_fix_run run in your project directory
- Claude Desktop Fictura start_fix_run ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Fictura start_fix_run ~/.cursor/mcp.json
- VS Code Fictura start_fix_run .vscode/mcp.json
- Zed Fictura start_fix_run ~/.config/zed/settings.json
- Windsurf Fictura start_fix_run ~/.codeium/windsurf/mcp_config.json
- Cline Fictura start_fix_run ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Fictura start_fix_run ~/.gemini/settings.json
- Grok Fictura start_fix_run .mcp.json (in your project root)
- ChatGPT Fictura start_fix_run Settings → Connectors → Advanced → Developer mode
- Claude.ai Fictura start_fix_run Settings → Connectors → Add custom connector
- LangChain Fictura start_fix_run pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://mcp.fictura.co/mcpOther tools on this server
- search_docs
- list_docs
- read_doc
- get_app_setup
- get_setup_step
- get_setup_status
- update_app_identity
- create_tracking_link
- get_analytics
- get_attribution_report
- list_users
- get_user
- check_entitlement
- get_tracking_plan
- list_surfaces
- get_surface
- list_templates
- list_experiments
- get_experiment
- create_experiment
- start_experiment
- pause_experiment
- resume_experiment
- stop_experiment
- get_acquisition_report
- get_store_analytics
- list_campaigns
- list_creators
- get_link_infrastructure
- get_push_config
- list_store_products
- list_error_issues
- search_error_issues
- search_error_events
- get_error_event
- get_error_issue
- get_error_issue_brief
- get_issue_tag_values
- get_issue_activity
- search_logs
- search_traces
- get_trace
- list_error_alerts
- list_alert_rules
- list_releases
- update_error_issue
- update_error_issues
- list_inbound_filters
- create_inbound_filter
- delete_inbound_filter
- get_uptime_monitor
- set_uptime_monitor
- get_error_settings
- update_tracing_settings
- get_performance_overview
- get_endpoint_summary
- list_dependencies
- get_span
- get_ai_usage
- get_jobs
- compare_releases
- get_web_vitals
- get_mobile_vitals
- list_monitors
- get_tracing_health
- create_ticket
- link_pull_request
- create_fix_pr
- create_pull_request
- get_pull_request_status
- get_fix_run
- get_paywall_doc
- validate_paywall_doc
- save_paywall_doc
- create_paywall_draft
- pair_editor
- editor_get_doc
- editor_set_doc
- unpair_editor
- get_onboarding_doc
- validate_onboarding_doc
- save_onboarding_doc
- create_onboarding_draft
- start_appsflyer_import
- get_appsflyer_import_status
- get_appsflyer_attribution_summary
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.