PCFHub

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Find Power Apps PCF controls, read their docs, and validate pcfhub.json manifests.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "PCFHub": {
      "url": "https://pcfhub.dev/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (8)

• search read-only

  Full-text search across every published PCF control and its documentation, ranked by relevance. Use it when you know what a control should do but not what it is called; use list_components instead to filter by category, tag, author or control type, and get_component when you already have a slug. Returns control and documentation hits, each with a snippet and a URL. A query that matches nothing is an empty result rather than an error, and a misspelling may be answered with results for a corrected spelling, which the result states.

  Parameters:

  • query (required) — string — What to look for, in plain words: "barcode scanner", "kanban", "date range".
  • limit — integer — How many results to return. Defaults to 10.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world not declared

• list_components read-only

  Browse the PCFHub catalog by category, tag, author, control type, host or text, paged and sorted. Use it to enumerate or narrow the catalog; use search for a plain-language question about what a control should do, and get_component for one control in full. Filters take slugs, which list_taxonomy supplies. Nothing here fails on bad input: an unrecognised sort falls back to the default, and filters matching nothing return an empty page — so read `total` and `sort` from the result rather than assuming the filters applied.

  Parameters:

  • host — string — Where the control has to run. A control supporting both hosts matches either.
  • page — integer — Defaults to 1.
  • sort — string — Defaults to relevance when there is a query, newest otherwise.
  • tags — array — Tag slugs, from list_taxonomy. A control must carry every tag given.
  • query — string — Words to match against names, taglines and descriptions.
  • author — string — An author slug, from list_taxonomy.
  • category — string — A category slug, from list_taxonomy.
  • per_page — integer — Defaults to 24; at most 48.
  • control_type — string — field binds one column on a form; dataset renders a view; virtual is a React control; grid_customizer changes how an editable grid renders cells.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world not declared

• get_component read-only

  Everything about one control by its slug: what it does, its control type, license and repository, the current release's properties, and download links for its solutions. Use it once search or list_components has given you a slug; use get_doc_page for installation and configuration instructions, which this does not return. An unknown slug, or a version the control never released, returns an error naming the tool to call instead. include_versions and include_related each cost an extra query, so leave them off unless you need the release history or similar controls.

  Parameters:

  • slug (required) — string — The control's slug, e.g. "pcf-tag-list".
  • version — string — A specific release. Defaults to the latest stable one.
  • include_related — boolean — Also return similar controls. Costs an extra query; leave off unless needed.
  • include_versions — boolean — Also return every release. Costs an extra query; leave off unless needed.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world not declared

• list_doc_sections read-only

  The documentation sections one control publishes — overview, installation, canvas, model_driven, examples, limitations and so on — each with its title and URL. Use it before get_doc_page to learn which sections that control actually has; it returns no page content, and get_component covers the property reference. A control with no documentation and a slug that does not exist return the same error on purpose, so fall back to search rather than concluding the slug is wrong.

  Parameters:

  • slug (required) — string — The control's slug, e.g. "pcf-tag-list".

  Hints: read-only yes · destructive not declared · idempotent yes · open-world not declared

• get_doc_page read-only

  Read one documentation section of a control as Markdown — installation steps, canvas or model-driven configuration, examples, limitations. Use list_doc_sections first for the sections that control publishes; use get_component instead for the structured property reference. Passing a version returns the documentation pinned to that release rather than the current page. A section the control does not document returns an error pointing at list_doc_sections, and the Markdown comes back without the frontmatter the site keeps.

  Parameters:

  • slug (required) — string — The control's slug, e.g. "pcf-tag-list".
  • section (required) — string — Which section to read.
  • version — string — Documentation pinned to a specific release. Defaults to the current documentation.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world not declared

• list_taxonomy read-only

  The vocabulary list_components filters by: the category tree, the tags in use, the authors with a published control, or the hosts a control can run in, each with its slug and a count. Use it to turn a name a person used into a slug; it returns no controls, so pass the slug to list_components to see them. Not paged — categories come back as a full tree and authors as a full list, while tags are capped at the 500 most used.

  Parameters:

  • kind (required) — string — Which list to return.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world not declared

• list_releases read-only

  The most recent releases across every control on PCFHub, newest first: which control, which version, whether it is a prerelease, and when it shipped. Use it for what has changed hub-wide; for one control's own history call get_component with include_versions instead. Bounded by limit, at most 50, and not paged — there is no cursor, so it cannot walk back beyond the newest 50.

  Parameters:

  • limit — integer — How many releases. Defaults to 20.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world not declared

• validate_manifest read-only

  Check a pcfhub.json against the rules PCFHub applies when it publishes a control: the schema version, the control block (namespace, constructor, type and framework), the demo's fidelity, bundle and presets, the media files it declares, and the release artifacts it expects to find. Use it while writing or reviewing that file, before a release is tagged. An invalid manifest is an ordinary result — valid false, with errors that block publishing and warnings that do not, each carrying the JSON pointer it applies to — so read the result rather than retrying. Only an empty, unreadable or oversized manifest (over 64 KB) is an error.

  Parameters:

  • manifest (required) — string — The full contents of pcfhub.json, as JSON text.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world not declared

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.