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