get_fix_run — Seonix MCP Tool Read-only
get_fix_run
(get fix run) is one of 41 tools on the
Seonix
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_fix_run from your client
- Claude Code Seonix get_fix_run run in your project directory
- Claude Desktop Seonix get_fix_run ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Seonix get_fix_run ~/.cursor/mcp.json
- VS Code Seonix get_fix_run .vscode/mcp.json
- Zed Seonix get_fix_run ~/.config/zed/settings.json
- Windsurf Seonix get_fix_run ~/.codeium/windsurf/mcp_config.json
- Cline Seonix get_fix_run ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Seonix get_fix_run ~/.gemini/settings.json
- Grok Seonix get_fix_run .mcp.json (in your project root)
- ChatGPT Seonix get_fix_run Settings → Connectors → Advanced → Developer mode
- Claude.ai Seonix get_fix_run Settings → Connectors → Add custom connector
- LangChain Seonix get_fix_run pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http seonix https://api.seonix.ai/mcpOther tools on this server
- acknowledge_issue
- analyze_seo
- apply_fix
- get_account
- get_ai_visibility
- get_article
- get_blog_integration_guide
- get_calendar
- get_cluster
- get_fix_plan
- get_issue
- get_plan_status
- get_playbook
- get_project
- get_remediation_profile
- get_results
- get_scan_status
- get_seo_progress
- get_site_dna
- get_site_health
- gsc_coverage
- gsc_impact
- gsc_opportunities
- gsc_page_queries
- gsc_status
- gsc_timeseries
- gsc_top_pages
- gsc_top_queries
- list_articles
- list_channels
- list_clusters
- list_issues
- list_keyword_candidates
- list_playbooks
- list_projects
- list_scans
- rollback_fix
- score_article
- start_scan
- unacknowledge_issue
This list was read from the server itself, by connecting to it and calling tools/list on 5 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.