remediation_plan — Agent Ready MCP Prompt

remediation_plan is one of 3 prompts on the Agent Ready MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke remediation_plan from your client

• Claude Code Agent Ready Prompt/remediation_plan run in your project directory
• Claude Desktop Agent Ready Prompt/remediation_plan ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Agent Ready Prompt/remediation_plan ~/.cursor/mcp.json
• VS Code Agent Ready Prompt/remediation_plan .vscode/mcp.json
• Zed Agent Ready Prompt/remediation_plan ~/.config/zed/settings.json
• Windsurf Agent Ready Prompt/remediation_plan ~/.codeium/windsurf/mcp_config.json
• Cline Agent Ready Prompt/remediation_plan ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Agent Ready Prompt/remediation_plan ~/.gemini/settings.json
• Grok Agent Ready Prompt/remediation_plan .mcp.json (in your project root)
• ChatGPT Agent Ready Prompt/remediation_plan Settings → Connectors → Advanced → Developer mode
• Claude.ai Agent Ready Prompt/remediation_plan Settings → Connectors → Add custom connector
• LangChain Agent Ready Prompt/remediation_plan pip install langchain-mcp-adapters

Other prompts on this server

• scan
• interpret_scan

Agent Ready 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 24 September 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.