fix_ai_track — mastering MCP Prompt
fix_ai_track
is one of 2 prompts on the
mastering
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke fix_ai_track from your client
- Claude Code mastering Prompt/fix_ai_track run in your project directory
- Claude Desktop mastering Prompt/fix_ai_track ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor mastering Prompt/fix_ai_track ~/.cursor/mcp.json
- VS Code mastering Prompt/fix_ai_track .vscode/mcp.json
- Zed mastering Prompt/fix_ai_track ~/.config/zed/settings.json
- Windsurf mastering Prompt/fix_ai_track ~/.codeium/windsurf/mcp_config.json
- Cline mastering Prompt/fix_ai_track ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI mastering Prompt/fix_ai_track ~/.gemini/settings.json
- Grok mastering Prompt/fix_ai_track .mcp.json (in your project root)
- ChatGPT mastering Prompt/fix_ai_track Settings → Connectors → Advanced → Developer mode
- Claude.ai mastering Prompt/fix_ai_track Settings → Connectors → Add custom connector
- LangChain mastering Prompt/fix_ai_track pip install langchain-mcp-adapters
Other prompts on this server
mastering also offers 4 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 14 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.