agree_the_change — change order MCP Prompt

agree_the_change is one of 2 prompts on the change order MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke agree_the_change from your client

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

Other prompts on this server

• upgrade_to_pro

change order also offers 2 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.