pp

Desktop app, Setup Manager, CLI, MCP server, and library for working with Microsoft Power Platform.

pp provides authenticated access to Dataverse, Power Automate, Microsoft Graph, SharePoint REST, BAP, and Power Apps APIs. It includes PP Desktop for full Power Platform workspaces, PP Setup Manager for lightweight account and environment setup, plus an MCP server for AI assistant integration.

Install

pp is distributed as four related artifacts that share the same config and auth cache:

PP Desktop -- Electron app for account setup, environment management, and Power Platform workspaces.
PP Setup Manager -- pp setup / pp-setup, a lightweight local browser setup surface for accounts, environments, and MCP help.
CLI -- pp, the command-line tool for scripted and terminal use.
MCP server -- pp-mcp, a stdio server for AI clients.

Install prebuilt binaries from GitHub Releases, or build from source for development. Current release assets include CLI, Setup Manager, and MCP binaries for Windows, macOS (arm64), and Linux (x64), plus PP Desktop as a Windows installer component and standalone macOS/Linux Electron archives.

Windows

Download pp-installer.exe from the latest GitHub Release and run the installer. The installer offers these components:

PP Desktop installs the Electron app under Program Files\PP\desktop and creates a Start menu shortcut.
PP Setup Manager installs pp-setup.exe under Program Files\PP and creates a Start menu shortcut.
MCP server installs pp-mcp.exe under Program Files\PP for MCP clients.
Command-line tools installs pp.exe under Program Files\PP.

Leave Add pp command-line tools to PATH checked if you want to use pp, pp setup, and pp-mcp from PowerShell or from MCP client configs without a full path. If you skip PATH registration, launch Setup Manager from the Start menu and point MCP clients at C:\Program Files\PP\pp-mcp.exe.

PP Desktop is the full Windows workspace. Setup Manager is the smaller browser-based auth and configuration surface. Both use the same config and auth cache as the CLI and MCP server, so accounts and environments created in one surface are available to the others. Use pp setup for the lightweight browser flow and PP Desktop for the full graphical workspace. Desktop talks to its backend through Electron IPC; Setup Manager binds to 127.0.0.1 with a random per-run token.

macOS

Download pp-darwin-arm64.tar.gz from the latest GitHub Release, extract it, and place the pp, pp-setup, and pp-mcp binaries somewhere on your PATH:

curl -LO https://github.com/callumalpass/power-platform-devkit/releases/latest/download/pp-darwin-arm64.tar.gz
tar -xzf pp-darwin-arm64.tar.gz
sudo mv pp pp-setup pp-mcp /usr/local/bin/

For PP Desktop, download pp-desktop-darwin-arm64.zip, unzip it, and move PP Desktop.app to /Applications. The current macOS desktop archive is an unsigned development build, so macOS may ask you to approve it in System Settings before first launch.

Linux

Download pp-linux-x64.tar.gz from the latest GitHub Release, extract it, and place the binaries on your PATH:

curl -LO https://github.com/callumalpass/power-platform-devkit/releases/latest/download/pp-linux-x64.tar.gz
tar -xzf pp-linux-x64.tar.gz
sudo mv pp pp-setup pp-mcp /usr/local/bin/

For PP Desktop, download pp-desktop-linux-x64.tar.gz, extract it, and run the bundled Electron app:

curl -LO https://github.com/callumalpass/power-platform-devkit/releases/latest/download/pp-desktop-linux-x64.tar.gz
tar -xzf pp-desktop-linux-x64.tar.gz
./pp-desktop-linux-x64/pp

Unreleased builds

For unreleased builds, download the pp-<platform>-<arch>-<commit> artifact from the latest successful CI workflow run. Linux and macOS artifacts include both the CLI/Setup/MCP archive and the PP Desktop archive.

Quick start

Open the setup surface:

pp setup

Log in with a browser-based auth flow:

pp auth login myaccount

Add a Dataverse environment:

pp env add dev --url https://myorg.crm.dynamics.com --account myaccount

Verify connectivity:

pp whoami --env dev

Send a Dataverse request:

pp dv /accounts --env dev

CLI reference

Command	Description
`pp auth login <account>`	Create or update an account and run a login flow
`pp auth list`	List configured accounts
`pp auth inspect <account>`	Show account details
`pp auth remove <account>`	Remove an account
`pp env list`	List configured environments
`pp env inspect <alias>`	Show environment details
`pp env discover <account>`	Discover environments accessible to an account
`pp env add <alias>`	Add an environment (`--url URL --account ACCOUNT`)
`pp env remove <alias>`	Remove an environment
`pp request <path> --env ALIAS`	Send an authenticated API request
`pp whoami --env ALIAS`	Run Dataverse WhoAmI
`pp ping --env ALIAS`	Check API connectivity
`pp token --env ALIAS`	Print a bearer token
`pp mcp`	Start the MCP server
`pp setup`	Open Setup Manager in a local browser
`pp migrate-config`	Migrate legacy config
`pp update [--check]`	Check GitHub releases for a newer version
`pp completion [zsh\|bash\|powershell]`	Print shell completion script

All commands accept --help for usage details. Most commands accept --config-dir DIR to override the config location, --credential-store auto|os|file to choose where interactive auth caches are kept, and --no-interactive-auth to disable browser-based auth prompts.

pp update checks the latest GitHub Release and prints the appropriate download instructions for your current install path.

Auth flows

The pp auth login command supports multiple authentication methods:

--browser (default) -- Interactive browser login via MSAL
--device-code -- Device code flow for headless environments
--client-secret -- Service principal auth (--tenant-id, --client-id, --client-secret-env required)
--env-token -- Read a token from an environment variable (--env-var required)
--static-token -- Use a fixed token string (--token required)

Interactive user and device-code accounts store their MSAL token cache in the OS credential store when available. --credential-store auto is the default: macOS uses Keychain, Windows uses DPAPI-protected storage, Linux uses Secret Service when available, and headless/CI environments fall back to the existing 0600 file cache. Use --credential-store os to require OS-backed storage or --credential-store file for deterministic local test/config directories.

API shortcuts

The commands pp dv, pp flow, pp graph, pp sharepoint/pp sp, pp bap, and pp powerapps are shortcuts for pp request --api <type>. They accept the same flags as pp request. pp canvas-authoring provides canvas authoring helpers and falls back to the same request shortcut when the first argument is not a helper command.

# Dataverse query
pp dv /accounts --env dev --query '$top=5'

# Graph request
pp graph /me --env dev
pp graph /me --account work

# SharePoint REST request
pp sp https://contoso.sharepoint.com/sites/site/_api/web --account work
pp sharepoint https://contoso.sharepoint.com/sites/site/_api/web/lists --env dev

# Power Automate flows
pp flow /flows --env dev

# Power Apps canvas authoring cluster discovery
pp canvas-authoring /gateway/cluster --env dev --read

# Power Apps canvas authoring session start
pp canvas-authoring session start --env dev --app <app-id>

# Fetch and validate Canvas YAML through a live authoring session
pp canvas-authoring yaml fetch --env dev --app <app-id> --out ./canvas-src
pp canvas-authoring yaml validate --env dev --app <app-id> --dir ./canvas-src

# List and describe available Canvas controls
pp canvas-authoring controls list --env dev --app <app-id>
pp canvas-authoring controls describe --env dev --app <app-id> Label

# Low-level Canvas document-server RPC
pp canvas-authoring invoke --env dev --app <app-id> --class documentservicev2 --oid 1 --method keepalive

# SignalR-backed Canvas document RPC, useful for query-style methods
pp canvas-authoring rpc --env dev --app <app-id> --class document --oid 2 --method geterrorsasync

Dataverse, Flow, BAP, Power Apps, Canvas Authoring, and custom requests are environment-scoped and require --env. Graph and SharePoint are account-scoped and can use --account directly; passing --env for those APIs is a shorthand for "use this environment's configured account".

The --api flag on pp request also accepts custom for arbitrary endpoints.

SharePoint REST requests require a full SharePoint URL. The token audience is the URL origin, for example https://contoso.sharepoint.com for https://contoso.sharepoint.com/sites/site/_api/web.

canvas-authoring targets the Power Apps canvas authoring service used by Studio and the Microsoft canvas authoring MCP server. Relative paths are rooted at the environment cluster-discovery host (https://<encoded-environment-id>.environment.api.powerplatform.com), so /gateway/cluster is the first low-level probe. Fully qualified authoring gateway URLs are preserved and authenticated with the canvas authoring resource. The session start helper wraps the known cluster discovery and authoring session start flow, and redacts session secrets from output unless --raw is provided. session request sends a versioned request with the active session headers; the yaml, controls, apis, datasources, and accessibility commands are thin wrappers around those MCP-style REST endpoints. invoke posts directly to /api/v2/invoke; rpc uses the authoring SignalR channel and waits for the matching document-server response.

pp canvas-authoring yaml validate uses the live session-backed validate-directory endpoint. Valid YAML can update the dirty draft visible in Maker/Studio, while invalid YAML returns diagnostics.

Canvas authoring is a first-party Microsoft resource that rejects pp's normal public client during interactive auth. For user and device-code accounts that do not already specify --client-id, pp uses the Power Apps Studio public client for canvas-authoring requests only, defaults that login to device code because the Studio client does not allow pp's localhost browser callback, and keeps that token in a separate cache entry so other APIs continue to use the normal pp client.

See Canvas Authoring API notes for the observed MCP-backed YAML endpoints, session headers, and adjacent Studio APIs.

jq response transforms

Request commands can apply a jq expression to JSON responses before printing the result:

pp dv /accounts --env dev --query '$select=name,accountid' --query '$top=50' --jq '.value | map({name, accountid})'

This runs jq in-process through WebAssembly instead of shelling out to a local jq binary. Prefer API-native filters such as $select, $filter, and $top first, then use --jq to trim or reshape the JSON that is returned.

PP Desktop

Click the walkthrough for the full MP4.

PP Desktop provides:

Setup -- Manage accounts and environments
Console -- Send requests to supported Power Platform APIs
Dataverse -- Browse entities and metadata, build OData queries, and execute FetchXML
Automate -- Inspect Power Automate flows and runs
Apps -- Inspect Power Apps inventory
Platform -- Inspect platform environment metadata
FetchXML -- Execute FetchXML queries

Desktop communicates with the local backend through Electron IPC. Launch the lightweight browser surface with pp setup, or use PP Desktop for the full workspace.

PP Setup Manager

Setup Manager is a smaller browser surface for configuration:

pp setup        # or: pp-setup

It focuses on account management, environment management, access checks, and MCP setup guidance from the Desktop app.

Setup Manager starts a loopback-only HTTP server on 127.0.0.1 with a random available port and a random per-run token. The token gates API calls, the server stays local to the machine, and the process stops through the Quit action, Ctrl+C, or the idle timeout.

MCP server

The MCP server exposes Power Platform operations as tools for AI assistants (e.g., Claude Desktop). It is a separate stdio process, usually launched by the MCP client. It shares pp config and auth with Desktop and the CLI.

pp mcp        # or: pp-mcp

Options:

--config-dir DIR -- Override config directory
--allow-interactive-auth -- Enable browser-based auth prompts (disabled by default in MCP mode)
--tool-name-style dotted|underscore -- Expose default dotted tool names (pp.account.list) or Copilot-compatible underscore names (pp_account_list)

Tool names

By default, tools are namespaced under pp.:

pp.account.list, pp.account.inspect, pp.account.login, pp.account.remove
pp.environment.list, pp.environment.inspect, pp.environment.add, pp.environment.discover, pp.environment.remove
pp.request, pp.dv_request, pp.flow_request, pp.graph_request, pp.sharepoint_request, pp.bap_request, pp.powerapps_request
pp.whoami, pp.ping, pp.token

When started with --tool-name-style underscore, dots are replaced by underscores (e.g. pp_account_list).

jq in MCP tools

The request tools accept jq to transform JSON responses before the MCP result is returned:

{
  "environment": "dev",
  "path": "/accounts",
  "query": { "$select": "name,accountid", "$top": "50" },
  "jq": ".value | map({name, accountid})"
}

For advanced limits, pass an object:

{
  "jq": {
    "expr": ".value[] | {name, accountid}",
    "maxOutputBytes": 50000,
    "timeoutMs": 2000
  }
}

Use raw: true when the jq expression intentionally returns text instead of JSON.

Client setup

See docs/mcp-clients.md for setup instructions for Claude Code, Codex CLI, GitHub Copilot CLI, and GitHub Copilot in VS Code.

Library usage

The package exports a side-effect-free TypeScript library, plus CLI and MCP entry points.

`pp` (main)

The stable public API for account management, environment management, API requests, Dataverse helpers, Flow and FetchXML language helpers, diagnostics, and MCP server creation.

import { PpClient } from 'pp';

const pp = new PpClient();

const accounts = await pp.accounts.list();
const response = await pp.request({
  env: 'dev',
  api: 'dv',
  path: '/accounts',
  query: { $select: 'name,accountid', $top: '5' },
  readIntent: true
});

Focused subpath exports are also available: pp/api, pp/auth, pp/client, pp/config, pp/dataverse, pp/diagnostics, pp/environments, pp/fetchxml-language, pp/flow-language, and pp/request.

`pp/mcp`

Functions to create and start an MCP server programmatically.

import { createPpMcpServer, startPpMcpServer } from 'pp/mcp';

// Create a server instance
const server = createPpMcpServer({ configDir: '/path/to/config' });

// Or start with stdio transport
const { server, transport } = await startPpMcpServer();

`pp/mcp-server`

Standalone MCP server entry point. Starts the server immediately on import.

`pp/experimental/canvas-authoring`

Experimental Canvas Authoring helpers. These wrap observed Studio/MCP-backed endpoints and may change more frequently than the stable API.

See Library usage for auth, request, error handling, and testing recipes. See API stability for the SemVer policy.

Development

Build from source

pnpm install
pnpm build

This produces ESM and CJS outputs in dist/, including the pp, pp-setup, and pp-mcp binaries plus the bundled PP Desktop assets under dist/desktop/ and Setup Manager assets under dist/setup/.

Run PP Desktop from source with live rebuilds:

pnpm run dev:desktop

This starts Electron from dist/desktop, watches the Desktop main/preload code and renderer code, restarts Electron when main/preload changes, and reloads the renderer when React/UI code changes. Dev mode uses a separate Electron profile so it can run next to an installed or manually launched PP Desktop instance while still sharing the normal pp config and auth cache.

Run the Electron E2E suite with:

pnpm run test:e2e:desktop

On Linux this runs the Electron app under xvfb-run by default, so the test window does not attach to the active desktop session or steal focus. Set PP_DESKTOP_E2E_SHOW_WINDOW=1 to run the same suite with a visible window for debugging.

Windows packaging

Build self-contained executables with:

pnpm run build:sea

This emits pp, pp-setup, and pp-mcp for the current host under release/<platform>-<arch>/, with .exe extensions on Windows.

Build the Electron desktop directory with:

pnpm run package:desktop

The SEA build emits pp, pp-setup, and pp-mcp under release/<platform>-<arch>/. The Electron packaging step emits the desktop app under release/electron/; CI archives this as pp-desktop-linux-x64.tar.gz on Linux and pp-desktop-darwin-arm64.zip on macOS. The Inno Setup installer definition at packaging/windows/pp.iss emits release/installer/pp-installer.exe, installs into Program Files\PP, offers Desktop, Setup Manager, MCP, and CLI components, optionally adds command-line tools to PATH, creates Start menu shortcuts for PP Desktop and PP Setup Manager, and registers uninstall support.

Name		Name	Last commit message	Last commit date
Latest commit History 530 Commits
.github/workflows		.github/workflows
canvas-src		canvas-src
docs		docs
packaging/windows		packaging/windows
scripts		scripts
src		src
test		test
.codex		.codex
.editorconfig		.editorconfig
.gitignore		.gitignore
.prettierignore		.prettierignore
.prettierrc.json		.prettierrc.json
.tmp-ui-test.mjs		.tmp-ui-test.mjs
LICENSE		LICENSE
README.md		README.md
electron-builder.json		electron-builder.json
eslint.config.js		eslint.config.js
package.json		package.json
playwright.ui.config.ts		playwright.ui.config.ts
pnpm-lock.yaml		pnpm-lock.yaml
tsconfig.json		tsconfig.json
tsconfig.test.json		tsconfig.test.json
tsup.config.ts		tsup.config.ts

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

pp

Install

Windows

macOS

Linux

Unreleased builds

Quick start

CLI reference

Auth flows

API shortcuts

jq response transforms

PP Desktop

PP Setup Manager

MCP server

Tool names

jq in MCP tools

Client setup

Library usage

`pp` (main)

`pp/mcp`

`pp/mcp-server`

`pp/experimental/canvas-authoring`

Development

Build from source

Windows packaging

About

Uh oh!

Releases 9

Packages

Uh oh!

Contributors

Uh oh!

Languages

Folders and files

Latest commit

History

Repository files navigation

pp

Install

Windows

macOS

Linux

Unreleased builds

Quick start

CLI reference

Auth flows

API shortcuts

jq response transforms

PP Desktop

PP Setup Manager

MCP server

Tool names

jq in MCP tools

Client setup

Library usage

pp (main)

pp/mcp

pp/mcp-server

pp/experimental/canvas-authoring

Development

Build from source

Windows packaging

About

Resources

License

Uh oh!

Stars

Watchers

Forks

Releases 9

Packages 0

Uh oh!

Contributors

Uh oh!

Languages

`pp` (main)

`pp/mcp`

`pp/mcp-server`

`pp/experimental/canvas-authoring`

Packages