vizro-mcp 0.1.1__tar.gz → 0.1.3__tar.gz

vizro_mcp-0.1.3/.dockerignore

@@ -0,0 +1,10 @@
+assets
+changelog.d
+tests
+.venv
+.pytest_cache
+__pycache__
+*.pyc
+*.pkl
+*.ipynb
+*.log

vizro_mcp-0.1.3/.readthedocs.yaml

@@ -0,0 +1,19 @@
+# Read the Docs configuration file for MkDocs projects
+# See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
+
+# Required
+version: 2
+
+# Set the version of Python and other tools you might need
+build:
+  os: ubuntu-22.04
+  tools:
+    python: "3.12"
+  commands:
+    # Remove the `click` installation constraint once the
+    # https://github.com/pypa/hatch/issues/2050 is resolved.
+    - pip install hatch "click<8.3.0"
+    - cd vizro-mcp/ && hatch run docs:pip tree
+    - cd vizro-mcp/ && hatch run docs:build
+    - mkdir --parents $READTHEDOCS_OUTPUT
+    - mv vizro-mcp/site/ $READTHEDOCS_OUTPUT/html

vizro_mcp-0.1.3/CHANGELOG.md

@@ -0,0 +1,50 @@
+<a id='changelog-0.1.3'></a>
+
+# 0.1.3 — 2025-09-29
+
+## Added
+
+- Added ability to use KPI cards in `Figure`. ([#1392](https://github.com/mckinsey/vizro/pull/1392))
+
+## Changed
+
+- Updated Layout prompting for better Layout performance of the MCP server. ([#1405](https://github.com/mckinsey/vizro/pull/1405))
+
+- Updated Vizro version to >=0.1.46. ([#1423](https://github.com/mckinsey/vizro/pull/1423))
+
+## Fixed
+
+- Added tool parameter descriptions to Field definition instead of docstring so that they display properly in hosts like Cursor. ([#1374](https://github.com/mckinsey/vizro/pull/1374)) <a id='changelog-0.1.2'></a>
+
+# 0.1.2 — 2025-06-30
+
+## Added
+
+- Add Dockerfile for Vizro MCP server to enable containerized local setup. ([#1184](https://github.com/mckinsey/vizro/pull/1184))
+
+- Add capability to create custom charts (beyond Plotly Express) with Vizro-MCP. ([#1227](https://github.com/mckinsey/vizro/pull/1227))
+
+## Changed
+
+- Update Vizro version to `>=0.1.42`. ([#1227](https://github.com/mckinsey/vizro/pull/1227))
+
+- Improve usability of MCP server in IDE environments like Cursor. ([#1227](https://github.com/mckinsey/vizro/pull/1227))
+
+<a id='changelog-0.1.1'></a>
+
+# 0.1.1 — 2025-05-15
+
+### Fixed
+
+- Fix name conflict with `langchain` by avoiding use of conflicting parameter names in tools. ([#1177](https://github.com/mckinsey/vizro/pull/1177))
+
+<a id='changelog-0.1.0'></a>
+
+# 0.1.0 — 2025-05-06
+
+## Added
+
+- Initial release of the Vizro MCP server. ([#1125](https://github.com/mckinsey/vizro/pull/1125))
+    - still experimental, please provide feedback via [github issues](https://github.com/mckinsey/vizro/issues)
+    - pinned `vizro` version to `0.1.38`
+    - published with 6 tools and 3 prompt templates

vizro_mcp-0.1.3/Dockerfile

@@ -0,0 +1,10 @@
+FROM ghcr.io/astral-sh/uv:python3.12-bookworm-slim
+
+WORKDIR /app
+
+COPY pyproject.toml uv.lock ./
+RUN uv sync --frozen --no-install-project --no-dev --no-editable
+
+COPY . /app
+
+ENTRYPOINT ["uv", "run", "vizro-mcp"]

vizro_mcp-0.1.3/PKG-INFO

@@ -0,0 +1,201 @@
+Metadata-Version: 2.4
+Name: vizro-mcp
+Version: 0.1.3
+Summary: MCP server to help create Vizro dashboards and charts
+Author: Vizro Team
+License-File: LICENSE.txt
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Requires-Python: >=3.10
+Requires-Dist: click>=8.1.7
+Requires-Dist: httpx>=0.28.1
+Requires-Dist: mcp[cli]>=1.6.0
+Requires-Dist: pandas[excel,html,parquet]
+Requires-Dist: vizro>=0.1.46
+Description-Content-Type: text/markdown
+
+<!-- <a href="https://glama.ai/mcp/servers/@mckinsey/vizro">
+  <img width="380" height="200" src="https://glama.ai/mcp/servers/@mckinsey/vizro/badge" />
+</a> -->
+
+# Vizro-MCP
+
+Vizro-MCP is a [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) server, which works alongside an LLM to help you create Vizro dashboards and charts.
+
+<img src="docs/assets/images/vizro-mcp.gif" width="600" alt="Vizro-MCP Demo">
+
+To find out more, consult the [Vizro-MCP documentation](https://vizro.readthedocs.io/projects/vizro-mcp/).
+
+## Set up Vizro-MCP
+
+Vizro-MCP is best used with Claude Desktop, Cursor or VS Code. However, it can be used with most LLM products that enable configuration of MCP server usage.
+
+> 💡 Tip: For best performance, we recommend using the `claude-4-sonnet` model, or another high-performing model of your choice. Using the often offered `auto` setting may lead to inconsistent or unexpected results.
+
+Our documentation offers separate, detailed steps for [Claude Desktop](https://vizro.readthedocs.io/projects/vizro-mcp/en/latest/pages/guides/set-up-vizro-mcp-with-claude/), [Cursor](https://vizro.readthedocs.io/projects/vizro-mcp/en/latest/pages/guides/set-up-vizro-mcp-with-cursor/) and [VS Code](https://vizro.readthedocs.io/projects/vizro-mcp/en/latest/pages/guides/set-up-vizro-mcp-with-vscode/).
+
+### Basic configuration
+
+The following is for those familiar with MCP server setup who are comfortable with basic configuration settings. You must have downloaded and installed the LLM app you want to configure and use as a MCP host.
+
+<details>
+<summary><strong>Quick setup for Vizro-MCP using uv</strong></summary>
+
+You must first install [uv](https://docs.astral.sh/uv/getting-started/installation/).
+
+Next, open a terminal window and type `uv` to confirm that is available. To get the path to `uvx`, type the following:
+
+```shell
+which uv
+```
+
+Copy the path returned, and add the following to the JSON file used to configure MCP servers for your LLM app. Be sure to substitute your path to uv as returned above, for the placeholder given:
+
+```
+{
+  "mcpServers": {
+    "vizro-mcp": {
+      "command": "/placeholder-path/uvx",
+      "args": [
+        "vizro-mcp"
+      ]
+    }
+  }
+}
+```
+
+**Quick install**
+
+| Host                                      | Prerequisite                                                  | Link                                                                                                                                                                                                                                                                                       |
+| ----------------------------------------- | ------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| [Cursor](https://www.cursor.com/)         | [uv](https://docs.astral.sh/uv/getting-started/installation/) | [![Install with UVX in Cursor](https://img.shields.io/badge/Cursor-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://cursor.com/en/install-mcp?name=vizro-mcp&config=eyJjb21tYW5kIjoidXZ4IHZpenJvLW1jcCJ9)                                                  |
+| [VS Code](https://code.visualstudio.com/) | [uv](https://docs.astral.sh/uv/guides/tools/)                 | [![Install with UVX in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://insiders.vscode.dev/redirect/mcp/install?name=vizro-mcp&config=%7B%22command%22%3A%22uvx%22%2C%22args%22%3A%5B%22vizro-mcp%22%5D%7D) |
+
+</details>
+
+<details>
+<summary><strong>Quick setup for Vizro-MCP using Docker</strong></summary>
+
+You must first install [Docker](https://www.docker.com/get-started/).
+
+Next, add the following to the JSON file used to configure MCP servers for your LLM app.
+
+```
+{
+  "mcpServers": {
+    "vizro-mcp": {
+      "command": "docker",
+      "args": [
+        "run",
+        "-i",
+        "--rm",
+        "mcp/vizro"
+      ]
+    }
+  }
+}
+```
+
+**To use local data with Docker**
+
+Mount your data directory or directories into the container with the following extended configuration. Replace `</absolute/path/to/allowed/dir>` (syntax for folders) or `</absolute/path/to/data.csv>` (syntax for files) with the absolute path to your data on your machine. For consistency, we recommend that the `dst` path matches the `src` path.
+
+```
+{
+  "mcpServers": {
+    "vizro-mcp": {
+      "command": "docker",
+      "args": [
+        "run",
+        "-i",
+        "--rm",
+        "--mount",
+        "type=bind,src=</absolute/path/to/allowed/dir>,dst=</absolute/path/to/allowed/dir>",
+        "--mount",
+        "type=bind,src=</absolute/path/to/data.csv>,dst=</absolute/path/to/data.csv>",
+        "mcp/vizro"
+      ]
+    }
+  }
+}
+```
+
+**Quick install**
+
+| Host                                      | Prerequisite                                  | Link                                                                                                                                                                                                                                                                                                                                   | Notes                                                                   |
+| ----------------------------------------- | --------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
+| [Cursor](https://www.cursor.com/)         | [Docker](https://www.docker.com/get-started/) | [![Install with Docker in Cursor](https://img.shields.io/badge/Cursor-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://cursor.com/en/install-mcp?name=vizro-mcp&config=eyJjb21tYW5kIjoiZG9ja2VyIHJ1biAtaSAtLXJtIG1jcC92aXpybyIsImVudiI6e319)                                                           | For local data access, [mount your data directory](#setup-instructions) |
+| [VS Code](https://code.visualstudio.com/) | [Docker](https://www.docker.com/get-started/) | [![Install with Docker in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://insiders.vscode.dev/redirect/mcp/install?name=vizro-mcp&config=%7B%22command%22%3A%22docker%22%2C%22args%22%3A%5B%22run%22%2C%22-i%22%2C%22--rm%22%2C%22mcp%2Fvizro%22%5D%7D) | For local data access, [mount your data directory](#setup-instructions) |
+
+</details>
+
+## Disclaimers
+
+### Transparency and trust
+
+MCP servers are a relatively new concept, and it is important to be transparent about what the tools are capable of so you can make an informed choice as a user. Overall, the Vizro MCP server only reads data, and never writes, deletes or modifies any data on your machine.
+
+### Third party API
+
+Users are responsible for anything done via their host LLM application.
+
+Users are responsible for procuring any and all rights necessary to access any third-party generative AI tools and for complying with any applicable terms or conditions thereof.
+
+Users are wholly responsible for the use and security of the third-party generative AI tools and of Vizro.
+
+### Legal information
+
+<details>
+<summary><strong>User acknowledgments</strong></summary>
+
+Users acknowledge and agree that:
+
+Any results, options, data, recommendations, analyses, code, or other information (“Outputs”) generated by any third-party generative AI tools (“GenAI Tools”) may contain some inaccuracies, biases, illegitimate, potentially infringing, or otherwise inappropriate content that may be mistaken, discriminatory, or misleading.
+
+McKinsey & Company:
+
+(i) expressly disclaims the accuracy, adequacy, timeliness, reliability, merchantability, fitness for a particular purpose, non-infringement, safety or completeness of any Outputs,
+
+(ii) shall not be liable for any errors, omissions, or other defects in, delays or interruptions in such Outputs, or for any actions taken in reliance thereon, and
+
+(iii) shall not be liable for any alleged violation or infringement of any right of any third party resulting from the users’ use of the GenAI Tools and the Outputs.
+
+The Outputs shall be verified and validated by the users and shall not be used without human oversight and as a sole basis for making decisions impacting individuals.
+
+Users remain solely responsible for the use of the Output, in particular, the users will need to determine the level of human oversight needed to be given the context and use case, as well as for informing the users’ personnel and other affected users about the nature of the GenAI Output. Users are also fully responsible for their decisions, actions, use of Vizro and Vizro-MCP and compliance with applicable laws, rules, and regulations, including but not limited to confirming that the Outputs do not infringe any third-party rights.
+
+</details>
+
+<details>
+<summary><strong>Warning and safety usage for generative AI models</strong></summary>
+
+Vizro-MCP is used by generative AI models because large language models (LLMs) represent significant advancements in the AI field. However, as with any powerful tool, there are potential risks associated with connecting to a generative AI model.
+
+We recommend users research and understand the selected model before using Vizro-MCP. We also recommend users to check the MCP server code before using it.
+
+Users are encouraged to treat AI-generated content as supplementary, always apply human judgment, approach with caution, review the relevant disclaimer page, and consider the following:
+
+<ol>
+<li>Hallucination and misrepresentation</li>
+Generative models can potentially generate information while appearing factual, being entirely fictitious or misleading.
+
+The vendor models might lack real-time knowledge or events beyond its last updates. Vizro-MCP output may vary and you should always verify critical information. It is the user's responsibility to discern the accuracy, consistent, and reliability of the generated content.
+
+<li>Unintended and sensitive output</li>
+The outputs from these models can be unexpected, inappropriate, or even harmful. Users as human in the loop is an essential part. Users must check and interpret the final output. It is necessary to approach the generated content with caution, especially when shared or applied in various contexts.
+
+<li>Data privacy</li>
+Your data is sent to model vendors if you connect to LLMs via their APIs. For example, if you connect to the model from OpenAI, your data will be sent to OpenAI via their API. Users should be cautious about sharing or inputting any personal or sensitive information.
+
+<li>Bias and fairness</li>
+Generative AI can exhibit biases present in their training data. Users need to be aware of and navigate potential biases in generated outputs and be cautious when interpreting the generated content.
+
+<li>Malicious use</li>
+These models can be exploited for various malicious activities. Users should be cautious about how and where they deploy and access such models.
+</ol>
+It's crucial for users to remain informed, cautious, and ethical in their applications.
+
+</details>

vizro_mcp-0.1.3/README.md

@@ -0,0 +1,182 @@
+<!-- <a href="https://glama.ai/mcp/servers/@mckinsey/vizro">
+  <img width="380" height="200" src="https://glama.ai/mcp/servers/@mckinsey/vizro/badge" />
+</a> -->
+
+# Vizro-MCP
+
+Vizro-MCP is a [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) server, which works alongside an LLM to help you create Vizro dashboards and charts.
+
+<img src="docs/assets/images/vizro-mcp.gif" width="600" alt="Vizro-MCP Demo">
+
+To find out more, consult the [Vizro-MCP documentation](https://vizro.readthedocs.io/projects/vizro-mcp/).
+
+## Set up Vizro-MCP
+
+Vizro-MCP is best used with Claude Desktop, Cursor or VS Code. However, it can be used with most LLM products that enable configuration of MCP server usage.
+
+> 💡 Tip: For best performance, we recommend using the `claude-4-sonnet` model, or another high-performing model of your choice. Using the often offered `auto` setting may lead to inconsistent or unexpected results.
+
+Our documentation offers separate, detailed steps for [Claude Desktop](https://vizro.readthedocs.io/projects/vizro-mcp/en/latest/pages/guides/set-up-vizro-mcp-with-claude/), [Cursor](https://vizro.readthedocs.io/projects/vizro-mcp/en/latest/pages/guides/set-up-vizro-mcp-with-cursor/) and [VS Code](https://vizro.readthedocs.io/projects/vizro-mcp/en/latest/pages/guides/set-up-vizro-mcp-with-vscode/).
+
+### Basic configuration
+
+The following is for those familiar with MCP server setup who are comfortable with basic configuration settings. You must have downloaded and installed the LLM app you want to configure and use as a MCP host.
+
+<details>
+<summary><strong>Quick setup for Vizro-MCP using uv</strong></summary>
+
+You must first install [uv](https://docs.astral.sh/uv/getting-started/installation/).
+
+Next, open a terminal window and type `uv` to confirm that is available. To get the path to `uvx`, type the following:
+
+```shell
+which uv
+```
+
+Copy the path returned, and add the following to the JSON file used to configure MCP servers for your LLM app. Be sure to substitute your path to uv as returned above, for the placeholder given:
+
+```
+{
+  "mcpServers": {
+    "vizro-mcp": {
+      "command": "/placeholder-path/uvx",
+      "args": [
+        "vizro-mcp"
+      ]
+    }
+  }
+}
+```
+
+**Quick install**
+
+| Host                                      | Prerequisite                                                  | Link                                                                                                                                                                                                                                                                                       |
+| ----------------------------------------- | ------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| [Cursor](https://www.cursor.com/)         | [uv](https://docs.astral.sh/uv/getting-started/installation/) | [![Install with UVX in Cursor](https://img.shields.io/badge/Cursor-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://cursor.com/en/install-mcp?name=vizro-mcp&config=eyJjb21tYW5kIjoidXZ4IHZpenJvLW1jcCJ9)                                                  |
+| [VS Code](https://code.visualstudio.com/) | [uv](https://docs.astral.sh/uv/guides/tools/)                 | [![Install with UVX in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://insiders.vscode.dev/redirect/mcp/install?name=vizro-mcp&config=%7B%22command%22%3A%22uvx%22%2C%22args%22%3A%5B%22vizro-mcp%22%5D%7D) |
+
+</details>
+
+<details>
+<summary><strong>Quick setup for Vizro-MCP using Docker</strong></summary>
+
+You must first install [Docker](https://www.docker.com/get-started/).
+
+Next, add the following to the JSON file used to configure MCP servers for your LLM app.
+
+```
+{
+  "mcpServers": {
+    "vizro-mcp": {
+      "command": "docker",
+      "args": [
+        "run",
+        "-i",
+        "--rm",
+        "mcp/vizro"
+      ]
+    }
+  }
+}
+```
+
+**To use local data with Docker**
+
+Mount your data directory or directories into the container with the following extended configuration. Replace `</absolute/path/to/allowed/dir>` (syntax for folders) or `</absolute/path/to/data.csv>` (syntax for files) with the absolute path to your data on your machine. For consistency, we recommend that the `dst` path matches the `src` path.
+
+```
+{
+  "mcpServers": {
+    "vizro-mcp": {
+      "command": "docker",
+      "args": [
+        "run",
+        "-i",
+        "--rm",
+        "--mount",
+        "type=bind,src=</absolute/path/to/allowed/dir>,dst=</absolute/path/to/allowed/dir>",
+        "--mount",
+        "type=bind,src=</absolute/path/to/data.csv>,dst=</absolute/path/to/data.csv>",
+        "mcp/vizro"
+      ]
+    }
+  }
+}
+```
+
+**Quick install**
+
+| Host                                      | Prerequisite                                  | Link                                                                                                                                                                                                                                                                                                                                   | Notes                                                                   |
+| ----------------------------------------- | --------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
+| [Cursor](https://www.cursor.com/)         | [Docker](https://www.docker.com/get-started/) | [![Install with Docker in Cursor](https://img.shields.io/badge/Cursor-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://cursor.com/en/install-mcp?name=vizro-mcp&config=eyJjb21tYW5kIjoiZG9ja2VyIHJ1biAtaSAtLXJtIG1jcC92aXpybyIsImVudiI6e319)                                                           | For local data access, [mount your data directory](#setup-instructions) |
+| [VS Code](https://code.visualstudio.com/) | [Docker](https://www.docker.com/get-started/) | [![Install with Docker in VS Code](https://img.shields.io/badge/VS_Code-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://insiders.vscode.dev/redirect/mcp/install?name=vizro-mcp&config=%7B%22command%22%3A%22docker%22%2C%22args%22%3A%5B%22run%22%2C%22-i%22%2C%22--rm%22%2C%22mcp%2Fvizro%22%5D%7D) | For local data access, [mount your data directory](#setup-instructions) |
+
+</details>
+
+## Disclaimers
+
+### Transparency and trust
+
+MCP servers are a relatively new concept, and it is important to be transparent about what the tools are capable of so you can make an informed choice as a user. Overall, the Vizro MCP server only reads data, and never writes, deletes or modifies any data on your machine.
+
+### Third party API
+
+Users are responsible for anything done via their host LLM application.
+
+Users are responsible for procuring any and all rights necessary to access any third-party generative AI tools and for complying with any applicable terms or conditions thereof.
+
+Users are wholly responsible for the use and security of the third-party generative AI tools and of Vizro.
+
+### Legal information
+
+<details>
+<summary><strong>User acknowledgments</strong></summary>
+
+Users acknowledge and agree that:
+
+Any results, options, data, recommendations, analyses, code, or other information (“Outputs”) generated by any third-party generative AI tools (“GenAI Tools”) may contain some inaccuracies, biases, illegitimate, potentially infringing, or otherwise inappropriate content that may be mistaken, discriminatory, or misleading.
+
+McKinsey & Company:
+
+(i) expressly disclaims the accuracy, adequacy, timeliness, reliability, merchantability, fitness for a particular purpose, non-infringement, safety or completeness of any Outputs,
+
+(ii) shall not be liable for any errors, omissions, or other defects in, delays or interruptions in such Outputs, or for any actions taken in reliance thereon, and
+
+(iii) shall not be liable for any alleged violation or infringement of any right of any third party resulting from the users’ use of the GenAI Tools and the Outputs.
+
+The Outputs shall be verified and validated by the users and shall not be used without human oversight and as a sole basis for making decisions impacting individuals.
+
+Users remain solely responsible for the use of the Output, in particular, the users will need to determine the level of human oversight needed to be given the context and use case, as well as for informing the users’ personnel and other affected users about the nature of the GenAI Output. Users are also fully responsible for their decisions, actions, use of Vizro and Vizro-MCP and compliance with applicable laws, rules, and regulations, including but not limited to confirming that the Outputs do not infringe any third-party rights.
+
+</details>
+
+<details>
+<summary><strong>Warning and safety usage for generative AI models</strong></summary>
+
+Vizro-MCP is used by generative AI models because large language models (LLMs) represent significant advancements in the AI field. However, as with any powerful tool, there are potential risks associated with connecting to a generative AI model.
+
+We recommend users research and understand the selected model before using Vizro-MCP. We also recommend users to check the MCP server code before using it.
+
+Users are encouraged to treat AI-generated content as supplementary, always apply human judgment, approach with caution, review the relevant disclaimer page, and consider the following:
+
+<ol>
+<li>Hallucination and misrepresentation</li>
+Generative models can potentially generate information while appearing factual, being entirely fictitious or misleading.
+
+The vendor models might lack real-time knowledge or events beyond its last updates. Vizro-MCP output may vary and you should always verify critical information. It is the user's responsibility to discern the accuracy, consistent, and reliability of the generated content.
+
+<li>Unintended and sensitive output</li>
+The outputs from these models can be unexpected, inappropriate, or even harmful. Users as human in the loop is an essential part. Users must check and interpret the final output. It is necessary to approach the generated content with caution, especially when shared or applied in various contexts.
+
+<li>Data privacy</li>
+Your data is sent to model vendors if you connect to LLMs via their APIs. For example, if you connect to the model from OpenAI, your data will be sent to OpenAI via their API. Users should be cautious about sharing or inputting any personal or sensitive information.
+
+<li>Bias and fairness</li>
+Generative AI can exhibit biases present in their training data. Users need to be aware of and navigate potential biases in generated outputs and be cautious when interpreting the generated content.
+
+<li>Malicious use</li>
+These models can be exploited for various malicious activities. Users should be cautious about how and where they deploy and access such models.
+</ol>
+It's crucial for users to remain informed, cautious, and ethical in their applications.
+
+</details>

vizro_mcp-0.1.3/docs/index.md

@@ -0,0 +1,35 @@
+---
+hide:
+  - navigation
+  - toc
+---
+
+# Vizro-MCP
+
+Vizro-MCP is a [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) server, which works alongside a LLM to help you create Vizro dashboards and charts.
+
+<img src="./assets/images/vizro-mcp.gif" width="600" alt="Vizro-MCP Demo">
+
+<div class="grid cards" markdown>
+
+- :fontawesome-solid-wand-magic-sparkles:{ .lg .middle } __Benefits of Vizro-MCP__
+
+    - One consistent framework for charts and dashboards with one common design language.
+
+    - Validated config output that is readable and easy to alter or maintain.
+
+    - Live preview of the dashboard to iterate the design until the dashboard is perfect.
+
+    - Use of local or remote datasets simply by providing a path or URL.
+
+- :fontawesome-solid-heart-crack:{ .lg .middle } __Without Vizro-MCP__
+
+    - Limited guidance, design principles, and consistency.
+
+    - Results tend to be a vibe-coded mess that may or may not run, but certainly is not very maintainable.
+
+    - No way to easily preview the dashboard.
+
+    - No easy way to connect to real data.
+
+</div>

vizro_mcp-0.1.3/docs/pages/API-reference/API-reference.md

@@ -0,0 +1,16 @@
+# API reference
+
+The API reference serves mostly as a reference what tools are available to the model and what prompts are available to the user. The Vizro-MCP server works by allowing the LLM to call this set of carefully crafted tools. You will never call these tools directly, but this reference gives an overview over what these tools do and what the model will get as information when deciding which tool to call. Should your host not support tool calling, the usability of the MCP server is limited.
+
+!!! note
+    The `validate_dashboard_config` tool opens a link to a live preview of the dashboard, which will take you to [PyCafe](https://py.cafe). If you don't want to open the link, you can tell the LLM to not do so.
+
+    The `load_and_analyze_data` tool loads a CSV file from a local path or URL into a pandas DataFrame and provides detailed analysis of its structure and content. It only uses `pd.read_xxx`, so in general there is no need to worry about privacy or data security. However, you should only run Vizro-MCP locally, not as a hosted server, because there is currently no authentication to manage access.
+
+
+::: vizro_mcp.server
+    options:
+        filters:
+        - "!^Data"
+        - "!^Model"
+        - "!^Validate"

vizro_mcp-0.1.3/docs/pages/explanation/contribute.md

@@ -0,0 +1,33 @@
+# Contribute to Vizro-MCP
+
+We are always happy to receive contributions to [Vizro](https://github.com/mckinsey/vizro) and Vizro-MCP!
+
+To contribute to Vizro-MCP you'll need to follow the same [contribution process as for the parent Vizro project](https://vizro.readthedocs.io/en/stable/pages/explanation/contributing/).
+
+## How to use a developer build of Vizro-MCP
+
+If you are a developer, or if you are running Vizro-MCP from source, you need to clone the [Vizro GitHub repository](https://github.com/mckinsey/vizro/tree/main).
+
+To configure the Vizro-MCP server details:
+
+Add the following to your MCP configuration:
+
+```json
+{
+  "mcpServers": {
+    "vizro-mcp": {
+      "command": "uv",
+      "args": [
+        "run",
+        "--directory",
+        "<PATH TO VIZRO>/vizro-mcp/",
+        "vizro-mcp"
+      ]
+    }
+  }
+}
+```
+
+Replace `<PATH TO VIZRO>` with the actual path to the clone of the Vizro repository.
+
+You may also need to provide the full path to your `uv` executable, so instead of `"uv"` you would use something like `"/Users/<your-username>/.local/bin/uv"`. To discover the path of `uv` on your machine, in your terminal app, type `which uv`.