How ttiama/pad-mcp works
pad-mcp is an MCP server that helps agents generate Power Automate Desktop flows using approved team knowledge and bundled action/type catalogs. The main workflow is: a developer selects Classic or Power Fx, searches catalog references and published patterns, then uses the returned Robin guidance to build a flow. Maintainers also create, review, publish, import, and export knowledge, and inspect usage statistics. The graph follows documented capabilities and shown imports/calls; unsampled handlers and storage details are represented only where the README or excerpts support them.
Main entry points: server.js MCP Server · index.js Application Startup · bootstrap.js Seed Bootstrap · store.js Knowledge Store
Components 16
MCP Runtime
- MCP Server
src/server.js - Development Prompts
src/prompts.js - Tool Schemas
src/schema.js - Call Rate Limiter
src/rate-limit.js - Application Startup
src/index.js
Team Knowledge
- Knowledge Store
src/store.js - SQLite Database
src/store.js - Seed Bootstrap
src/bootstrap.js - Initial Knowledge
knowledge/seed.json
PAD References
- Catalog Cache
src/catalog-cache.js - Catalog Search
src/catalog.js - Action and Type Catalogs
catalogs
Access and Operations
- Developer API Keys
src/api-keys.js - Usage Statistics
src/usage.js
Other components
- Developer
- Maintainer
Connections 22
- Developer → MCP Server: calls tools
README.md - Maintainer → MCP Server: manages knowledge
README.md - Application Startup → Knowledge Store: creates
src/index.js - Application Startup → Seed Bootstrap: runs bootstrap
src/index.js - Application Startup → MCP Server: starts app
src/index.js - Application Startup → Catalog Cache: creates
src/index.js - Application Startup → Call Rate Limiter: configures
src/index.js - Seed Bootstrap → Knowledge Store: seeds and publishes
src/bootstrap.js - Seed Bootstrap → Tool Schemas: validates seed
src/bootstrap.js - Seed Bootstrap → Initial Knowledge: reads seed
src/bootstrap.js - Knowledge Store → SQLite Database: reads and writes
src/store.js - MCP Server → Knowledge Store: handles knowledge tools
src/server.js - MCP Server → Tool Schemas: validates tool input
src/server.js - MCP Server → Catalog Cache: gets catalog
src/server.js - MCP Server → Development Prompts: builds guidance
src/server.js - MCP Server → Developer API Keys: authenticates keys
src/server.js - MCP Server → Usage Statistics: records and reports
src/server.js - MCP Server → Call Rate Limiter: limits calls
src/server.js - Catalog Cache → Catalog Search: builds index
src/catalog-cache.js - Catalog Search → Action and Type Catalogs: searches bundled data
- Usage Statistics → SQLite Database: records counters
src/usage.js - Developer API Keys → SQLite Database: stores key records
src/api-keys.js