Developer Tools

pcfhub.dev

Provides full-text search and browsing of the PCFHub catalog of Power Apps Component Framework controls, including component details and documentation pages.

1 endpoint8 known toolsFirst detected September 14, 2026Last detected September 14, 2026

ENDPOINT 1

https://pcfhub.dev/mcp

No auth detected

MCP server metadata

Name: PCFHub
Version: 1.0.0

Capabilities

toolsresourcesprompts

Server instructions

PCFHub (https://pcfhub.dev) is a catalog of Power Apps Component Framework (PCF) controls: code components for model-driven and canvas apps in the Power Platform. Every control listed has documentation, a property reference and downloadable solutions. A typical flow: 1. `search` when you know what the control should do, or `list_components` to browse by category, tag or control type. 2. `get_component` for its properties, current release and download links. 3. `list_doc_sections` and `get_doc_page` for installation, configuration and examples, as Markdown. When writing or reviewing a `pcfhub.json` for a control repository, run `validate_manifest` — it applies the hub's own rules. Prefer the URLs these tools return when citing a control, so the user can open the page. Only published components are visible; if a slug is not found, search rather than guessing.

Known tools 8

search

Full-text search across every published PCF control and its documentation.

Inferred read-only

list_components

Browse the PCFHub catalog with optional filters: a text query, category slug, tag slugs, author slug and control type.

Inferred read-only

get_component

Everything about one control by its slug: what it does, its control type, license and repository, the current release's properties (name, type, usage, required, description) and download links for its solutions.

Inferred read-only

list_doc_sections

The documentation sections a control has — overview, installation, canvas, model_driven, examples, limitations and so on.

Inferred read-only

get_doc_page

Read one documentation section of a control as Markdown — installation steps, canvas or model-driven configuration, examples, limitations.

Inferred read-only

list_taxonomy

The category tree, every tag in use, or every author with a published control — each with its slug and how many controls it has.

Inferred read-only

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.

Inferred read-only

validate_manifest

Check the contents of a pcfhub.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.pcfhub]
url = "https://pcfhub.dev/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "pcfhub": {
      "type": "http",
      "url": "https://pcfhub.dev/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: pcfhub
Remote MCP URL: https://pcfhub.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "pcfhub": {
      "url": "https://pcfhub.dev/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "pcfhub": {
      "type": "http",
      "url": "https://pcfhub.dev/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

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

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.