The lookups that normally mean clicking through the maker portal — what attributes an entity has, what fires on its events, what the trace log said — answered in the conversation, against whichever environment you name.
A PowerPlatform and Dataverse server with a matching CLI. It reads entity metadata, records, plugins, solutions and security roles, and writes too — creating attributes and keys for automated environment setup. Every tool takes an optional environment parameter that picks which one it runs against.
- get-entity-metadata, get-entity-attributes and get-entity-attribute read an entity's definition at whatever depth you need
- get-entity-relationships and get-entity-keys cover how entities connect and what identifies them
- get-record and query-records read the data itself
- get-plugin-assemblies, get-plugin-assembly-complete and get-entity-plugin-pipeline map what runs on an entity's events, by assemblyName or entityName
- get-plugin-trace-logs reads the trace logs when something misbehaves
- create-entity-string-attribute and create-entity-alternate-key write configuration rather than only reading it
- The CLI writes the same results to a file-system cache instead of inline, which keeps a large environment out of the context window
A supported Node.js release, or the ghcr.io/michsob/powerplatform-mcp Docker image. Each environment needs a URL, client ID, client secret and tenant ID set as environment variables.
One command plus a key — npm install -g powerplatform-mcp, then supply credentials