fxray

io.github.S-CurveLabsPublished by GitHub account S-CurveLabsv0.1.0Updated Oct 24, 2026

Power Apps via pac: solutions, canvas Power Fx source, Dataverse metadata, FetchXML, gated imports.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Lets an assistant work with Power Apps projects through the pac CLI: solutions, canvas Power Fx source, Dataverse metadata, FetchXML, and gated imports.

What you can do
fxray is a local MCP server that exposes Microsoft Power Platform tooling to an assistant, described as "Power Apps via pac: solutions, canvas Power Fx source, Dataverse metadata, FetchXML, gated imports." It works with solutions, canvas app Power Fx source, Dataverse metadata and FetchXML queries, and it can perform imports that are gated. It runs as a local process over stdio and is desktop only.
When to use it
Worth adding when an assistant needs to inspect or modify Power Apps and Dataverse artifacts on a developer machine, for example reading canvas Power Fx source, querying Dataverse metadata or FetchXML, or running gated solution imports. Not useful if you do not work with Power Platform projects.
Requirements
A local Python environment to install the fxray package from PyPI, run over stdio on a desktop machine. Configuration comes from fxray.toml, located via FXRAY_CONFIG, or found in the working folder or the per-user folder set by FXRAY_HOME (default %LOCALAPPDATA%\fxray on Windows, ~/.config/fxray elsewhere); FXRAY_WORKSPACE selects the folder whose fxray.toml to use when FXRAY_CONFIG is not set. No authentication is declared.
Before you install
The configuration file controls an environment allowlist, a write gate, and a pac path, so review it before use. Imports are described as gated, but they can still change Power Platform environments; confirm what an import will modify before approving it. No credentials are declared by the server itself.

Installation

In SourceWeft

  1. Open fxray in the dashboard and add it to a workspace.
  2. 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

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 23, 2026

Score

25% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.