S-Curve Labs

S-Curve LabsHelp

Help index

Help index

Setup steps and the fixes we're asked about most, for each product family. If your question isn't here, contact support.

1Add a Power BI visual

S-Curve Labs visuals are published on Microsoft AppSource. To add one to a report:

  1. Open the report for editing in Power BI Desktop or the Power BI service.
  2. In the Visualizations pane, select … (Get more visuals), then Get more visuals.
  3. Search for S-Curve Labs or the visual's name, then select Add.

The visual's icon appears in the Visualizations pane, and it is saved with the report, so everyone who opens the report sees it without installing anything.

2Can't add a visual

Power BI administrators decide whether people can add visuals from AppSource, and whether only certified visuals are allowed. If Get more visuals is missing or a visual won't add, the setting is usually the cause.

Ask your Power BI administrator either to allow the visual or to add it to your organization's visuals. Once it is there, it appears under My organization in the same dialog.

3Export and subscriptions

Microsoft only renders certified custom visuals in some places, including exports to PowerPoint and report pages sent by email subscription. A visual that isn't certified still works in the report itself but may show as blank there. Each visual's AppSource listing shows whether it is certified.

4Visual updates

When we publish a new version of a visual, reports that use it from AppSource pick it up automatically. Microsoft rolls updates out over a couple of weeks, so a fix we announce may take that long to reach your tenant. Visuals your administrator added to your organization's visuals are updated by your administrator.

5Visual guides

Each visual gets a guide here when it goes live on AppSource: what it shows, which fields it needs, and its Format pane settings.

No visuals are listed yet. Guides appear here as each one is published.

6Set up an MCP server

Each server is a Python package on PyPI. The simplest way to run one is uv: install it once, and uvx <name> fetches and runs the server with the right Python, with nothing else to install.

  1. Install uv, or use pip install <name> in a Python environment you manage.
  2. Add the server to your assistant. In Claude Code: claude mcp add --scope user longpath -- uvx longpath. In VS Code, add it to .vscode/mcp.json as shown on the MCP servers page.
  3. Restart or reload the assistant, then ask it what tools the server provides.

Each server's PyPI page has its own setup notes, configuration options and tool list: dax-quax · letin · sqlglass · longpath · fxray.

7MCP troubleshooting

The server doesn't show up in my assistant

Run the same command your assistant uses (for example uvx longpath) in a terminal. If it prints an error, that's the problem; if it starts and waits quietly, the server is fine and is waiting for a client (press Ctrl+C to stop it). Then check that the command in your assistant's config matches exactly, and restart the assistant.

A write didn't happen

That's usually by design. Tools that change things return a plan first (a diff, a preview SELECT, or the commands a dry run would run). Nothing is applied until the call passes dry_run=false or writes are turned on in the server's config. The server's PyPI page lists which switch it uses.

It can't find Power BI Desktop, Excel or the Power Platform CLI

The servers that work with Microsoft software (dax-quax, letin, fxray) need it installed on the same machine, and some features are Windows-only. The server's PyPI page lists what it needs.