Power Portals Pro
io.github.Power-Portals-ProPublished by GitHub account Power-Portals-Prov13.0.0Updated Nov 3, 2026
Component API, code samples and Dataverse metadata for building Power Portals Pro portals.
Overview
Local MCP server that gives an assistant Power Portals Pro component API, code samples and Dataverse metadata for building portals.
- What you can do
- Provide component API reference and code samples for Power Portals Pro
- Supply Dataverse metadata relevant to building portals
- Serve as a local stdio reference source while an assistant writes portal code
- No individual tools are listed in the manifest, so exact operations are not documented
- When to use it
- Use when building or extending a Power Portals Pro portal and you want the assistant to work from the product's component API, sample code and Dataverse metadata instead of guessing.
- Requirements
- Runs as a local process on the user's machine over stdio, installed from the NuGet package PowerPortalsPro.Mcp. Desktop only; no web execution. No authentication, environment variables or headers are declared.
Installation
In SourceWeft
- Open Power Portals Pro in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Power Portals Pro — Public Issue Tracker
Welcome! This repository exists solely as the public issue tracker for Power Portals Pro.
Because the main product codebase is private, this repository provides a place for customers and partners to:
- Report bugs
- Request new features
- Ask questions
- Track progress on upcoming improvements
How to Use This Repository
🐞 Report a Bug
Open an Issue using the Bug Report template.
Please include:
- Steps to reproduce
- Expected behavior
- Actual behavior
- Screenshots or recordings (if applicable)
💡 Request a Feature
Use the Feature Request template.
Tell us:
- What problem you're trying to solve
- Why it matters
- Any examples or context
❓ Ask a Question
Use the General Question template.
🔒 About the Main Codebase
The primary Power Portals Pro repository is private.
This public tracker allows us to collaborate openly without exposing proprietary code.
📬 Thank You
Your feedback directly shapes the roadmap.
We appreciate your time and contributions.
Source: README.md at commit 0d22671
Tools
0Version history
16- v13.0.0LatestNov 3, 2026
- v12.0.0Nov 1, 2026
- v11.4.0Oct 23, 2026
- v11.3.0Oct 22, 2026
- v11.2.0Oct 20, 2026
- v11.1.0Oct 16, 2026
- v11.0.0Oct 14, 2026
- v10.5.0Oct 13, 2026
- v10.4.0Oct 9, 2026
- v10.3.0Oct 9, 2026
- v10.2.0Oct 6, 2026
- v10.1.0Oct 5, 2026
- v10.0.0Sep 27, 2026
- v9.1.0Sep 24, 2026
- v9.0.0Sep 18, 2026
- v8.1.0Sep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.