analyze-document — Zambo MCP Prompt

analyze-document is one of 9 prompts on the Zambo MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke analyze-document from your client

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

Other prompts on this server

• get-oriented
• strategy-spark
• audit-repo
• find-leads
• design-agent-stack
• first-job
• forge-this-workflow
• audit-this-repo

Zambo also offers 7 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.