Developer-first toolkit for authoring Power Apps PCF manifests and running a local proxy that removes the publish loop.

For detailed guides, API reference, and examples, see the documentation.

Lifecycle
Core Stack
Navigation

1. Install (recommended): uv tool install pcf-toolkit@latest
2. Initialize a proxy config: pcf-toolkit proxy init
3. Build your control so out/controls/{PCF_NAME} exists.
4. Start the proxy: pcf-toolkit proxy start MyComponent

Run without install (useful in CI or scripts):

uvx pcf-toolkit --help

Requirements:

• Python 3.13
• uv (recommended for install/run)
• mitmproxy (required for proxy mode; auto-installed if auto_install: true)
• Optional: Microsoft PAC CLI (pac) for environment discovery

Feature Badge	Details
	Intercepts PCF webresource requests and serves your local build without publishing.
	Strict schema validation with readable errors.
	Stable, ordered XML output for clean diffs.
	Import legacy XML and keep authoring in YAML or JSON.
	Export JSON Schema for editor validation and linting.
	Diagnoses ports, mitmproxy, certs, and dist paths.

Proxy config (pcf-proxy.yaml)

Top-level keys:

proxy:

http_server:

bundle:

browser:

mitmproxy:

environments:

Manifest authoring

• Author manifests in YAML or JSON.
• Generate XML with pcf-toolkit generate.
• Import existing XML with pcf-toolkit import-xml.
• Validate with pcf-toolkit validate.

Environment variables

Used internally (set automatically by the CLI):

• Provider: GitHub Actions (.github/workflows/ci.yml).
• Triggers: pushes to main, PRs targeting main, and tags starting with v.
• Build steps: install uv, install Python 3.13, sync deps, build schema snapshot and JSON schema.
• Guardrail: git diff --exit-code ensures generated schema artifacts are committed.
• Tests: pytest with coverage report (terminal output only).
• Publish: on tags v*, builds and publishes to PyPI with uv publish.

• Optional: Microsoft PAC CLI (pac) for environment discovery and selection.
• The proxy expects your control to build into bundle.dist_path (defaults to out/controls/{PCF_NAME}).
• The proxy intercepts /webresources/{PCF_NAME}/... requests and serves files from your local build output.

• The toolkit does not manage authentication.
• PAC CLI uses your existing Power Platform login for environment discovery.
• The proxy does not store tokens or credentials; it only rewrites webresource requests.

• No telemetry is emitted by default.
• No analytics or event collection is built into the CLI.

• This project does not require a database.

• Use pcf-toolkit proxy doctor to check ports, mitmproxy, certs, and dist paths.
• Active proxy sessions store PID metadata in .pcf-toolkit/proxy.session.json.
• Detached runs write logs to .pcf-toolkit/proxy.log.

Install dev dependencies:

uv sync --extra dev

Run tests:

uv run --python 3.13 pytest

Regenerate schema artifacts:

uv run --python 3.13 --script scripts/build_schema_snapshot.py
uv run --python 3.13 --script scripts/build_json_schema.py

If you run scripts/extract_spec.py, install browser binaries first:

uv run --python 3.13 python -m playwright install

Build a wheel locally:

uv build

• Python 3.13 available.
• schemas/pcf-manifest.schema.json and data/schema_snapshot.json regenerated.
• pcf-toolkit proxy doctor passes for your target component.
• CI pipeline is green and release tag is created for publishing.

• CLI: Typer-based commands in pcf_toolkit.cli and pcf_toolkit.proxy.cli.
• Manifest tooling: Pydantic models validate YAML/JSON and serialize deterministic XML.
• Proxy workflow: mitmproxy addon rewrites PCF webresource requests to a local http.server instance.
• Schema pipeline: scripts extract and normalize Microsoft Learn references into JSON Schema and snapshots.

• Manifest invalid: run pcf-toolkit validate and fix fields reported in the error table.
• Dist path missing: run your PCF build or update bundle.dist_path in pcf-proxy.yaml.
• Config not found: run pcf-toolkit proxy init or pass --config.
• mitmproxy missing: run pcf-toolkit proxy doctor --fix or set mitmproxy.path.
• mitmproxy CA cert missing: run pcf-toolkit proxy doctor and follow OS-specific guidance.
• Browser did not open: set crm_url and check browser.prefer or browser.path.
• Ports already in use: change proxy.port or http_server.port.

• License: LICENSE.md (Vectorfy Co Community Use License).
• No secrets are stored in the repo; use placeholders in configs.
• Some badges use stand-in icons (Typer uses FastAPI, Proxy uses Server Fault).