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