PBIFORGE
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | No | Anthropic API key (optional — only needed for LLM-powered features) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_dashboardA | Create a complete Power BI dashboard from a local dataset path. USE THIS TOOL when the user says "create a dashboard/report from this dataset" and provides a local file path. Prefer this over create_report because this reads real data rows and does not require an Anthropic API key. Supports CSV files. Returns a local .pbit file_path, not base64. |
| create_reportA | Create a new Power BI report from a natural language description. Do NOT use this when the user provides a CSV/dataset file path; use create_dashboard instead. This tool needs a valid Anthropic API key. Returns a session_id to use in all subsequent tool calls. Example: "monthly sales by region with YoY comparison for retail team" |
| add_visualA | Add a visual to an existing report session. description: plain English e.g. "bar chart of units sold by product category" page_name: which page to add to (default: Overview) |
| apply_image_themeC | Extract color palette from a dashboard image and apply it as the report theme. image_base64: base64-encoded image string media_type: image/png or image/jpeg |
| edit_stylingB | Edit report styling via natural language. Examples:
|
| add_filterB | Add a slicer or filter to the report. Examples:
|
| export_pbixA | Compile the current session into a .pbix file and return it as base64. The base64 string can be decoded and saved as report.pbix. |
| export_pbit_fileA | Compile the current session and save the .pbit locally. Claude Desktop should prefer this over export_pbix to avoid huge base64 output. |
| export_pbit_urlA | Compile the current session, save the .pbit on the hosted server, and return a public download URL. Set PUBLIC_BASE_URL on Railway for this tool. |
| create_from_csvA | Create a Power BI dashboard from a CSV file. Auto-generates KPI cards, bar chart, line chart, pie chart, and slicer — no prompt required. csv_base64: base64-encoded CSV bytes. filename: original filename (used for table naming in the data model). prompt: optional report title override (e.g. "Q4 Sales Overview"). image_base64: optional branding image (base64) to extract theme colors from. Returns: session_id, pbix_base64 (save as .pbit), report_title, columns_detected, domain. |
| create_from_csv_textB | Create a Power BI dashboard from raw CSV text. This is easier to use from Claude Desktop than base64 input. Does not require an Anthropic API key unless image theming is used elsewhere. |
| create_from_csv_file_pathB | Create a Power BI dashboard from a CSV file already on this computer. Preferred for Claude Desktop because it avoids putting large CSV/base64 data into the conversation context. |
| get_report_stateB | Return the current report structure for inspection. Useful for understanding what has been generated before editing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
The creation tools (create_dashboard, create_from_csv, create_from_csv_file_path, create_from_csv_text, create_report) have overlapping purposes, with subtle distinctions that may confuse an agent. Other tools like add_filter, add_visual, and export variants are clearer.
All tool names follow a consistent verb_noun pattern using underscores (e.g., add_filter, create_report, export_pbit_file). Even compound names like create_from_csv_file_path maintain the pattern, with no mixing of conventions.
13 tools cover creation, editing, theming, export, and inspection, which is well-scoped for a report generation server. Not over or under-loaded.
Covers most CRUD-like operations: create reports from various sources, add visuals/filters, edit styling, export results, and inspect state. Minor gap: no tools for deleting visuals, filters, or pages, but core workflows are supported.