# PCFHub

- Registry name: `io.github.pcfhub/pcfhub` · version 1.0.0
- Categories (automatic, keyword rules): Code & repositories, Developer tools, Scraping & browsing, Search & data, Education
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.pcfhub%2Fpcfhub
- Server page: https://mcpstation.net/s/io.github.pcfhub--pcfhub.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://pcfhub.dev/mcp`

## Tools (as reported by the server, not verified)

- `search`: 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. Ret
- `list\_components`: 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 sup
- `get\_component`: 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, whic
- `list\_doc\_sections`: 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 prope
- `get\_doc\_page`: 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 t
- `list\_taxonomy`: 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
- `list\_releases`: 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, an
- `validate\_manifest`: 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 writi

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html