How jhenomm/pp-docs-mcp works
PP Docs is an MCP server that turns Power Platform exports into structured Markdown or Word documentation, optionally saved to SharePoint. A client submits a request; the server routes single-file or solution workflows, solution inspection produces a component manifest, and selected flows, Copilot topics, and Power Apps screens are documented with an AI provider before output generation. The repository also supports agent-level overviews and direct .msapp screen extraction. The graph follows documented workflows and sampled imports/calls; some server routing and output behavior is established by the README rather than inspected implementation details.
Main entry points: process-solution.js Solution processor · index.js MCP server · document-flow.js Flow docs · document-copilot-topic.js Topic docs
Components 15
Request handling
- MCP server
src/index.js - File detection
src/index.js
Component documentation
- Flow docs
src/tools/document-flow.js - Topic docs
src/tools/document-copilot-topic.js - Power Apps docs
src/tools/document-power-app.js - Agent overview
src/tools/document-agent.js - AI provider client
src/ai-client.js
Solution workflows
- Solution inspector
src/tools/inspect-solution.js - Solution processor
src/tools/process-solution.js - MSAPP extractor
src/tools/msapp-extractor.js
Generation and storage
- DOCX generator
src/tools/generate-docx.js - SharePoint I/O
src/tools/sharepoint-output.js
Other components
- MCP client
- LLM services
- SharePoint
Connections 26
- MCP client → MCP server: sends requests
README.md - MCP server → File detection: routes requests
README.md - MCP server → Solution inspector: inspects solutions
src/index.js - MCP server → Solution processor: processes solutions
src/index.js - MCP server → Flow docs: routes flow docs
src/index.js - MCP server → Topic docs: routes topic docs
src/index.js - MCP server → Power Apps docs: routes app docs
src/index.js - Solution processor → Solution inspector: uses manifest
src/tools/process-solution.js - Solution processor → Flow docs: documents flows
src/tools/process-solution.js - Solution processor → Topic docs: documents topics
src/tools/process-solution.js - Solution processor → Power Apps docs: documents screens
src/tools/process-solution.js - Solution processor → Agent overview: creates overview
src/tools/process-solution.js - Solution processor → MSAPP extractor: extracts screens
src/tools/process-solution.js - Solution processor → DOCX generator: generates documents
src/tools/process-solution.js - Solution processor → SharePoint I/O: downloads and uploads
src/tools/process-solution.js - Solution inspector → SharePoint I/O: downloads source
src/tools/inspect-solution.js - Flow docs → AI provider client: requests content
src/tools/document-flow.js - Topic docs → AI provider client: requests content
src/tools/document-copilot-topic.js - Power Apps docs → AI provider client: requests content
src/tools/document-power-app.js - Agent overview → AI provider client: requests overview
src/tools/document-agent.js - AI provider client → LLM services: calls configured provider
src/ai-client.js - Flow docs → DOCX generator: generates DOCX
src/tools/document-flow.js - Flow docs → SharePoint I/O: uploads output
src/tools/document-flow.js - Topic docs → DOCX generator: generates DOCX
src/tools/document-copilot-topic.js - Topic docs → SharePoint I/O: uploads output
src/tools/document-copilot-topic.js - SharePoint I/O → SharePoint: reads and writes files
README.md