Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
PCFHub is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
8
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Find Power Apps PCF controls, read their docs, and validate pcfhub.json manifests.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http pcfhub-mcp https://pcfhub.dev/mcp
# 2 — ask your agent for something these tools do
# search, list_components, get_component and 5 more
PCFHub costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PCAll 1 server
pcfhub1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http pcfhub-mcp https://pcfhub.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What to look for, in plain words: "barcode scanner", "kanban", "date range". |
| limit | integer | no | How many results to return. Defaults to 10. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Words to match against names, taglines and descriptions. |
| category | string | no | A category slug, from list_taxonomy. |
| tags | array | no | Tag slugs, from list_taxonomy. A control must carry every tag given. |
| author | string | no | An author slug, from list_taxonomy. |
| control_type | string | no | 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. |
| host | string | no | Where the control has to run. A control supporting both hosts matches either. |
| sort | string | no | Defaults to relevance when there is a query, newest otherwise. |
| page | integer | no | Defaults to 1. |
| per_page | integer | no | Defaults to 24; at most 48. |
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 n
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The control's slug, e.g. "pcf-tag-list". |
| version | string | no | A specific release. Defaults to the latest stable one. |
| include_versions | boolean | no | Also return every release. Costs an extra query; leave off unless needed. |
| include_related | boolean | no | Also return similar controls. Costs an extra query; leave off unless needed. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The control's slug, e.g. "pcf-tag-list". |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The control's slug, e.g. "pcf-tag-list". |
| section | string | yes | Which section to read. |
| version | string | no | Documentation pinned to a specific release. Defaults to the current documentation. |
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 cap
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | yes | Which list to return. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | How many releases. Defaults to 20. |
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 — v
| Parameter | Type | Required | Notes |
|---|---|---|---|
| manifest | string | yes | The full contents of pcfhub.json, as JSON text. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install PCFHub or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish PCFHub can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.