Power Apps via pac: solutions, canvas Power Fx source, Dataverse metadata, FetchXML, gated imports.
Connect Runs on your machine
claude mcp add fxray -e FXRAY_CONFIG=<FXRAY_CONFIG> -e FXRAY_WORKSPACE=<FXRAY_WORKSPACE> -e FXRAY_HOME=<FXRAY_HOME> -- uvx fxray==0.1.0
{
"mcpServers": {
"fxray": {
"command": "uvx",
"args": [
"fxray==0.1.0"
],
"env": {
"FXRAY_CONFIG": "<FXRAY_CONFIG>",
"FXRAY_WORKSPACE": "<FXRAY_WORKSPACE>",
"FXRAY_HOME": "<FXRAY_HOME>"
}
}
}
}
{
"mcpServers": {
"fxray": {
"command": "uvx",
"args": [
"fxray==0.1.0"
],
"env": {
"FXRAY_CONFIG": "<FXRAY_CONFIG>",
"FXRAY_WORKSPACE": "<FXRAY_WORKSPACE>",
"FXRAY_HOME": "<FXRAY_HOME>"
}
}
}
}
{
"servers": {
"fxray": {
"type": "stdio",
"command": "uvx",
"args": [
"fxray==0.1.0"
],
"env": {
"FXRAY_CONFIG": "<FXRAY_CONFIG>",
"FXRAY_WORKSPACE": "<FXRAY_WORKSPACE>",
"FXRAY_HOME": "<FXRAY_HOME>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
FXRAY_CONFIGOptional | Path to fxray.toml (environment allowlist, write gate, pac path). Optional if the file is in the working folder or the per-user folder. |
FXRAY_WORKSPACEOptional | Folder whose fxray.toml to use when FXRAY_CONFIG is not set. |
FXRAY_HOMEOptional | Per-user folder (default %LOCALAPPDATA%\fxray on Windows, ~/.config/fxray elsewhere). |
Details
| Package | [email protected] (PYPI, stdio) |
| First published | 23 Sep 2026 |
| Last updated | 23 Sep 2026 |
| Registry name | io.github.S-CurveLabs/fxray |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
