fix_issues_in_code — Seonix MCP Prompt
fix_issues_in_code
is one of 11 prompts on the
Seonix
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke fix_issues_in_code from your client
- Claude Code Seonix Prompt/fix_issues_in_code run in your project directory
- Claude Desktop Seonix Prompt/fix_issues_in_code ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Seonix Prompt/fix_issues_in_code ~/.cursor/mcp.json
- VS Code Seonix Prompt/fix_issues_in_code .vscode/mcp.json
- Zed Seonix Prompt/fix_issues_in_code ~/.config/zed/settings.json
- Windsurf Seonix Prompt/fix_issues_in_code ~/.codeium/windsurf/mcp_config.json
- Cline Seonix Prompt/fix_issues_in_code ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Seonix Prompt/fix_issues_in_code ~/.gemini/settings.json
- Grok Seonix Prompt/fix_issues_in_code .mcp.json (in your project root)
- ChatGPT Seonix Prompt/fix_issues_in_code Settings → Connectors → Advanced → Developer mode
- Claude.ai Seonix Prompt/fix_issues_in_code Settings → Connectors → Add custom connector
- LangChain Seonix Prompt/fix_issues_in_code pip install langchain-mcp-adapters
Other prompts on this server
Seonix also offers 5 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 5 November 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.