vizro-mcp 0.1.2__py3-none-any.whl → 0.1.4__py3-none-any.whl

vizro_mcp/__init__.py

@@ -3,7 +3,7 @@ import sys
 
 from .server import mcp
 
-__version__ = "0.1.2"
+__version__ = "0.1.4"
 
 
 def main():

vizro_mcp/_schemas/__init__.py

@@ -1,11 +1,13 @@
 from .schemas import (
     AgGridEnhanced,
     ChartPlan,
+    FigureEnhanced,
     GraphEnhanced,
 )
 
 __all__ = [
     "AgGridEnhanced",
     "ChartPlan",
+    "FigureEnhanced",
     "GraphEnhanced",
 ]

vizro_mcp/_schemas/schemas.py

@@ -1,7 +1,8 @@
 """Schema defining pydantic models for usage in the MCP server."""
 
-from typing import Annotated, Any, Optional
+from typing import Annotated, Any
 
+import vizro.figures as vf
 import vizro.models as vm
 from pydantic import AfterValidator, BaseModel, Field, PrivateAttr, ValidationInfo
 
@@ -58,6 +59,21 @@ The only difference to the dash version is that:
     )
 
 
+FIGURE_NAMESPACE_FUNCTION_DOCS = {func: vf.__dict__[func].__doc__ for func in vf.__all__}
+
+
+class FigureEnhanced(vm.Figure):
+    """Figure model that allows to use dynamic figure functions."""
+
+    figure: dict[str, Any] = Field(
+        description=f"""This is the figure function to be displayed.
+
+Only use arguments from the below mapping of _target_ to figure function documentation:
+
+{FIGURE_NAMESPACE_FUNCTION_DOCS}"""
+    )
+
+
 ###### Chart functionality ######
 def _strip_markdown(code_string: str) -> str:
     """Remove any code block wrappers (markdown or triple quotes)."""
@@ -137,7 +153,7 @@ class ChartPlan(BaseModel):
             imports = [imp for imp in imports if "vizro" not in imp]
         return "\n".join(imports) + "\n"
 
-    def get_chart_code(self, chart_name: Optional[str] = None, vizro: bool = False):
+    def get_chart_code(self, chart_name: str | None = None, vizro: bool = False):
         chart_code = self.chart_code
         if vizro:
             chart_code = chart_code.replace(f"def {self.chart_name}", f"@capture('graph')\ndef {self.chart_name}")

vizro_mcp/_utils/configs.py

@@ -1,7 +1,7 @@
 """Pre-set configs for the Vizro MCP."""
 
 from dataclasses import dataclass
-from typing import Any, Literal, Optional
+from typing import Any, Literal
 
 
 @dataclass
@@ -10,7 +10,7 @@ class DFMetaData:
     file_path_or_url: str
     file_location_type: Literal["local", "remote"]
     read_function_string: Literal["pd.read_csv", "pd.read_json", "pd.read_html", "pd.read_parquet", "pd.read_excel"]
-    column_names_types: Optional[dict[str, str]] = None
+    column_names_types: dict[str, str] | None = None
 
 
 @dataclass

vizro_mcp/_utils/prompts.py

@@ -1,9 +1,11 @@
 """Prompts for the Vizro MCP."""
 # ruff: noqa: E501 #Ignore line length only in prompts
 
-from typing import Literal, Optional
+from typing import Literal, Protocol
 
 import vizro
+import vizro.actions as va
+import vizro.figures as vf
 import vizro.models as vm
 
 from vizro_mcp._utils.configs import SAMPLE_DASHBOARD_CONFIG
@@ -28,7 +30,9 @@ IMPORTANT:
 - ALWAYS CHECK SCHEMA: to start with, or when stuck, try enquiring the schema of the component in question with the `get_model_json_schema` tool (available models see below)
 
 - IF the user has no plan (ie no components or pages), use the config at the bottom of this prompt, OTHERWISE:
-- make a plan of what components you would like to use, then request all necessary schemas using the `get_model_json_schema` tool (start with `Dashboard`, and don't forget `Graph`)
+- make a plan of what components you would like to use, then request all necessary schemas using the `get_model_json_schema` tool
+  - start with `Dashboard`, don't forget `Graph`,
+  - MUST explicitly set layout (layout setting is NOT optional, contrary to what schema says)
 - assemble your components into a page, then add the page or pages to a dashboard, DO NOT show config or code to the user until you have validated the solution
 - ALWAYS validate the dashboard configuration using the `validate_dashboard_config` tool
 - using `custom_chart` is encouraged for advanced visualizations, no need to call the planner tool in advanced mode
@@ -50,24 +54,46 @@ GENERIC_HOST_INSTRUCTIONS = """
     instead and explain how to run it
 """
 
+
+# Protocol class does not seem to matter for static type checkers - implemented nonetheless for correctness
+# TODO: Check why type errors in MODEL_GROUPS would not be picked up by mypy
+class HasNameAndDoc(Protocol):
+    """Protocol for objects that have a name and a docstring."""
+
+    __name__: str
+    __doc__: str | None
+
+
 # This dict is used to give the model and overview of what is available in the vizro.models namespace.
 # It helps it to narrow down the choices when asking for a model.
-MODEL_GROUPS: dict[str, list[type[vm.VizroBaseModel]]] = {
+# Intentionally omitted: Accordion, Action, Table, Layout and VizroBaseModel
+MODEL_GROUPS: dict[str, list[type[HasNameAndDoc]]] = {
     "main": [vm.Dashboard, vm.Page],
-    "components": [vm.Card, vm.Button, vm.Text, vm.Container, vm.Tabs, vm.Graph, vm.AgGrid],  #'Figure', 'Table'
+    "static components": [
+        vm.Card,
+        vm.Button,
+        vm.Text,
+        vm.Container,
+        vm.Tabs,
+    ],
+    "dynamic components - ie reactive to controls": [vm.Figure, vm.Graph, vm.AgGrid],
     "layouts": [vm.Grid, vm.Flex],
-    "controls": [vm.Filter, vm.Parameter],
-    "selectors": [
+    "controls - control display of dynamic components": [vm.Filter, vm.Parameter],
+    "selectors - input mechanisms for controls": [
         vm.Dropdown,
         vm.RadioItems,
         vm.Checklist,
         vm.DatePicker,
         vm.Slider,
         vm.RangeSlider,
-        vm.DatePicker,
+        vm.Switch,
     ],
     "navigation": [vm.Navigation, vm.NavBar, vm.NavLink],
-    "additional_info": [vm.Tooltip],
+    "additional_info - info about the component": [vm.Tooltip],
+    "actions available for the actions argument of a model": [
+        getattr(va, func) for func in va.__all__ if not hasattr(getattr(va, func), "__deprecated__")
+    ],
+    "functions available for vm.Figure(...,figure=...) model": [getattr(vf, func) for func in vf.__all__],
 }
 
 
@@ -134,7 +160,7 @@ Create a super simple Vizro dashboard with one page and one chart and one filter
 """
 
 
-def get_dashboard_prompt(file_path_or_url: str, user_context: Optional[str] = None) -> str:
+def get_dashboard_prompt(file_path_or_url: str, user_context: str | None = None) -> str:
     """Get a prompt for creating a Vizro dashboard."""
     USER_INSTRUCTIONS = f"""
 3. Create a Vizro dashboard that follows the user context:
@@ -165,7 +191,7 @@ Create a dashboard based on the following dataset: `{file_path_or_url}`. Proceed
 """
 
 
-def get_chart_prompt(file_path_or_url: str, user_context: Optional[str] = None) -> str:
+def get_chart_prompt(file_path_or_url: str, user_context: str | None = None) -> str:
     """Get a prompt for creating a Vizro chart."""
     FALLBACK_INSTRUCTIONS = """
 - Think what chart could reflect this data-set best, ideally the chart shows some insights about the data-set

vizro_mcp/_utils/utils.py

@@ -7,7 +7,7 @@ import json
 import re
 from dataclasses import dataclass
 from pathlib import Path
-from typing import TYPE_CHECKING, Literal, Optional, Union
+from typing import TYPE_CHECKING, Literal
 from urllib.parse import quote, urlencode
 
 import pandas as pd
@@ -44,7 +44,7 @@ def convert_github_url_to_raw(path_or_url: str) -> str:
 
 
 def load_dataframe_by_format(
-    path_or_url: Union[str, Path], mime_type: Optional[str] = None
+    path_or_url: str | Path, mime_type: str | None = None
 ) -> tuple[pd.DataFrame, Literal["pd.read_csv", "pd.read_json", "pd.read_html", "pd.read_excel", "pd.read_parquet"]]:
     """Load a dataframe based on file format determined by MIME type or file extension."""
     file_path_str_lower = str(path_or_url).lower()
@@ -152,6 +152,9 @@ def get_python_code_and_preview_link(
         "from vizro import Vizro",
         "import pandas as pd",
         "from vizro.managers import data_manager",
+        "import vizro.figures as vf",
+        # TODO: Temporary workaround for Figure model support; required until vizro>=0.1.46
+        # Remove this import once minimum supported vizro version is >=0.1.46.
     ]
     custom_imports = [
         imp for custom_chart in custom_charts for imp in custom_chart.get_imports(vizro=True).split("\n") if imp.strip()

vizro_mcp/server.py

@@ -4,8 +4,9 @@ import mimetypes
 import webbrowser
 from dataclasses import dataclass
 from pathlib import Path
-from typing import Any, Literal, Optional
+from typing import Any, Literal
 
+import vizro
 import vizro.models as vm
 from mcp.server.fastmcp import FastMCP
 from pydantic import Field, ValidationError
@@ -14,6 +15,7 @@ from vizro import Vizro
 from vizro_mcp._schemas import (
     AgGridEnhanced,
     ChartPlan,
+    FigureEnhanced,
     GraphEnhanced,
 )
 from vizro_mcp._utils import (
@@ -45,7 +47,7 @@ class ValidateResults:
     valid: bool
     message: str
     python_code: str
-    pycafe_url: Optional[str]
+    pycafe_url: str | None
     browser_opened: bool
 
 
@@ -55,8 +57,8 @@ class DataAnalysisResults:
 
     valid: bool
     message: str
-    df_info: Optional[DFInfo]
-    df_metadata: Optional[DFMetaData]
+    df_info: DFInfo | None
+    df_metadata: DFMetaData | None
 
 
 @dataclass
@@ -70,28 +72,28 @@ class ModelJsonSchemaResults:
 
 # TODO: check on https://github.com/modelcontextprotocol/python-sdk what new things are possible to do here
 mcp = FastMCP(
-    "MCP server to help create Vizro dashboards and charts.",
+    name=f"MCP server to help create Vizro dashboards and charts. Server Vizro version: {vizro.__version__}",
 )
 
 
 @mcp.tool()
 def get_vizro_chart_or_dashboard_plan(
-    user_plan: Literal["chart", "dashboard"],
-    user_host: Literal["generic_host", "ide"],
-    advanced_mode: bool = False,
+    user_plan: Literal["chart", "dashboard"] = Field(description="The type of Vizro thing the user wants to create"),
+    user_host: Literal["generic_host", "ide"] = Field(
+        description="The host the user is using, if 'ide' you can use the IDE/editor to run python code"
+    ),
+    advanced_mode: bool = Field(
+        default=False,
+        description="""Only call if you need to use custom CSS, custom components or custom actions.
+No need to call this with advanced_mode=True if you need advanced charts,
+use `custom_charts` in the `validate_dashboard_config` tool instead.""",
+    ),
 ) -> str:
     """Get instructions for creating a Vizro chart or dashboard. Call FIRST when asked to create Vizro things.
 
     Must be ALWAYS called FIRST with advanced_mode=False, then call again with advanced_mode=True
     if the JSON config does not suffice anymore.
 
-    Args:
-        user_plan: The type of Vizro thing the user wants to create
-        user_host: The host the user is using, if "ide" you can use the IDE/editor to run python code
-        advanced_mode: Only call if you need to use custom CSS, custom components or custom actions.
-            No need to call this with advanced_mode=True if you need advanced charts, use `custom_charts` in
-            the `validate_dashboard_config` tool instead.
-
     Returns:
         Instructions for creating a Vizro chart or dashboard
     """
@@ -101,20 +103,29 @@ def get_vizro_chart_or_dashboard_plan(
         return f"{get_dashboard_instructions(advanced_mode, user_host)}"
 
 
-@mcp.tool()
-def get_model_json_schema(model_name: str) -> ModelJsonSchemaResults:
+@mcp.tool(description=f"Get the JSON schema for the specified Vizro model. Server Vizro version: {vizro.__version__}")
+def get_model_json_schema(
+    model_name: str = Field(
+        description="Name of the Vizro model to get schema for (e.g., 'Card', 'Dashboard', 'Page')"
+    ),
+) -> ModelJsonSchemaResults:
     """Get the JSON schema for the specified Vizro model.
 
-    Args:
-        model_name: Name of the Vizro model to get schema for (e.g., 'Card', 'Dashboard', 'Page')
-
     Returns:
         JSON schema of the requested Vizro model
     """
+    if not hasattr(vm, model_name):
+        return ModelJsonSchemaResults(
+            model_name=model_name,
+            json_schema={},
+            additional_info=f"Model '{model_name}' not found in vizro.models",
+        )
+
     modified_models = {
         "Graph": GraphEnhanced,
         "AgGrid": AgGridEnhanced,
         "Table": AgGridEnhanced,
+        "Figure": FigureEnhanced,
     }
 
     if model_name in modified_models:
@@ -124,15 +135,23 @@ def get_model_json_schema(model_name: str) -> ModelJsonSchemaResults:
             additional_info="""LLM must remember to replace `$ref` with the actual config. Request the schema of
 that model if necessary. Do NOT forget to call `validate_dashboard_config` after each iteration.""",
         )
-
-    if not hasattr(vm, model_name):
+    deprecated_models = {"filter_interaction": "set_control", "Layout": "Grid"}
+    if model_name in deprecated_models:
         return ModelJsonSchemaResults(
             model_name=model_name,
             json_schema={},
-            additional_info=f"Model '{model_name}' not found in vizro.models",
+            additional_info=f"Model '{model_name}' is deprecated. Use {deprecated_models[model_name]} instead.",
         )
 
     model_class = getattr(vm, model_name)
+    if model_name in {"Grid", "Flex"}:
+        return ModelJsonSchemaResults(
+            model_name=model_name,
+            json_schema=model_class.model_json_schema(schema_generator=NoDefsGenerateJsonSchema),
+            additional_info="""Grid layout: use integers starting from 0 to reference elements.
+Elements can't overlap, must be rectangular, and rows must have equal column counts.""",
+        )
+
     return ModelJsonSchemaResults(
         model_name=model_name,
         json_schema=model_class.model_json_schema(schema_generator=NoDefsGenerateJsonSchema),
@@ -142,7 +161,11 @@ that model if necessary. Do NOT forget to call `validate_dashboard_config` after
 
 
 @mcp.tool()
-def get_sample_data_info(data_name: Literal["iris", "tips", "stocks", "gapminder"]) -> DFMetaData:
+def get_sample_data_info(
+    data_name: Literal["iris", "tips", "stocks", "gapminder"] = Field(
+        description="Name of the dataset to get sample data for"
+    ),
+) -> DFMetaData:
     """If user provides no data, use this tool to get sample data information.
 
     Use the following data for the below purposes:
@@ -151,9 +174,6 @@ def get_sample_data_info(data_name: Literal["iris", "tips", "stocks", "gapminder
         - stocks: stock prices, good for line, scatter, generally things that change over time
         - gapminder: demographic data, good for line, scatter, generally things with maps or many categories
 
-    Args:
-        data_name: Name of the dataset to get sample data for
-
     Returns:
         Data info object containing information about the dataset.
     """
@@ -168,7 +188,9 @@ def get_sample_data_info(data_name: Literal["iris", "tips", "stocks", "gapminder
 
 
 @mcp.tool()
-def load_and_analyze_data(path_or_url: str) -> DataAnalysisResults:
+def load_and_analyze_data(
+    path_or_url: str = Field(description="Absolute (important!) local file path or URL to a data file"),
+) -> DataAnalysisResults:
     """Use to understand local or remote data files. Must be called with absolute paths or URLs.
 
     Supported formats:
@@ -179,9 +201,6 @@ def load_and_analyze_data(path_or_url: str) -> DataAnalysisResults:
     - OpenDocument Spreadsheet (.ods)
     - Parquet (.parquet)
 
-    Args:
-        path_or_url: Absolute (important!) local file path or URL to a data file
-
     Returns:
         DataAnalysisResults object containing DataFrame information and metadata
     """
@@ -225,22 +244,22 @@ column types for passing along to the `validate_dashboard_config` or `validate_c
 # - data_infos: check we are referring to the correct dataframe, or at least A DF
 @mcp.tool()
 def validate_dashboard_config(
-    dashboard_config: dict[str, Any],
-    data_infos: list[DFMetaData],
-    custom_charts: list[ChartPlan],
-    auto_open: bool = True,
+    dashboard_config: dict[str, Any] = Field(
+        description="Either a JSON string or a dictionary representing a Vizro dashboard model configuration"
+    ),
+    data_infos: list[DFMetaData] = Field(
+        description="List of DFMetaData objects containing information about the data files"
+    ),
+    custom_charts: list[ChartPlan] = Field(
+        description="List of ChartPlan objects containing information about the custom charts in the dashboard"
+    ),
+    auto_open: bool = Field(default=True, description="Whether to automatically open the PyCafe link in a browser"),
 ) -> ValidateResults:
     """Validate Vizro model configuration. Run ALWAYS when you have a complete dashboard configuration.
 
     If successful, the tool will return the python code and, if it is a remote file, the py.cafe link to the chart.
     The PyCafe link will be automatically opened in your default browser if auto_open is True.
 
-    Args:
-        dashboard_config: Either a JSON string or a dictionary representing a Vizro dashboard model configuration
-        data_infos: List of DFMetaData objects containing information about the data files
-        custom_charts: List of ChartPlan objects containing information about the custom charts in the dashboard
-        auto_open: Whether to automatically open the PyCafe link in a browser
-
     Returns:
         ValidationResults object with status and dashboard details
     """
@@ -296,7 +315,7 @@ def create_starter_dashboard():
 @mcp.prompt()
 def create_dashboard(
     file_path_or_url: str = Field(description="The absolute path or URL to the data file you want to use."),
-    context: Optional[str] = Field(default=None, description="(Optional) Describe the dashboard you want to create."),
+    context: str | None = Field(default=None, description="(Optional) Describe the dashboard you want to create."),
 ) -> str:
     """Prompt template for creating an EDA dashboard based on one dataset."""
     return get_dashboard_prompt(file_path_or_url, context)
@@ -304,17 +323,12 @@ def create_dashboard(
 
 @mcp.tool()
 def validate_chart_code(
-    chart_config: ChartPlan,
-    data_info: DFMetaData,
-    auto_open: bool = True,
+    chart_config: ChartPlan = Field(description="A ChartPlan object with the chart configuration"),
+    data_info: DFMetaData = Field(description="Metadata for the dataset to be used in the chart"),
+    auto_open: bool = Field(default=True, description="Whether to automatically open the PyCafe link in a browser"),
 ) -> ValidateResults:
     """Validate the chart code created by the user and optionally open the PyCafe link in a browser.
 
-    Args:
-        chart_config: A ChartPlan object with the chart configuration
-        data_info: Metadata for the dataset to be used in the chart
-        auto_open: Whether to automatically open the PyCafe link in a browser
-
     Returns:
         ValidationResults object with status and dashboard details
     """
@@ -358,7 +372,7 @@ def validate_chart_code(
 @mcp.prompt()
 def create_vizro_chart(
     file_path_or_url: str = Field(description="The absolute path or URL to the data file you want to use."),
-    context: Optional[str] = Field(default=None, description="(Optional) Describe the chart you want to create."),
+    context: str | None = Field(default=None, description="(Optional) Describe the chart you want to create."),
 ) -> str:
     """Prompt template for creating a Vizro chart."""
     return get_chart_prompt(file_path_or_url, context)

vizro_mcp-0.1.4.dist-info/METADATA

@@ -0,0 +1,202 @@
+Metadata-Version: 2.4
+Name: vizro-mcp
+Version: 0.1.4
+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
+Classifier: Programming Language :: Python :: 3.14
+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.4.dist-info/RECORD

@@ -0,0 +1,14 @@
+vizro_mcp/__init__.py,sha256=b07rnAb9ypm8N9O4fLH5LYOeVC48ncU5k_xesNH0zmc,379
+vizro_mcp/py.typed,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+vizro_mcp/server.py,sha256=DoD1B_-EeHcTJSAog6lyaAi-_AA4u1dXAsHLgq0ku3Y,13689
+vizro_mcp/_schemas/__init__.py,sha256=0lk_CiNjo4QFyX0i-VuSeL7EMM6sD_2p836y-ftM3Gs,196
+vizro_mcp/_schemas/schemas.py,sha256=6XCNSTag7RL0xL3SkRVMlJ2GOW0nbm73drhcKRpNfOU,8795
+vizro_mcp/_utils/__init__.py,sha256=ucPbfXe8kEFT7chz6ed_BeqAw71MnoWlZTYyCp4tPYY,1130
+vizro_mcp/_utils/configs.py,sha256=DH5B-RbtLuAkq6cgVL7oBOg3J-T_Mi4ovU430h5iUus,3614
+vizro_mcp/_utils/prompts.py,sha256=TJ--Tpv_tw2L8Tbt6PtaCA435HhUPpqUibNoEryKu94,10767
+vizro_mcp/_utils/utils.py,sha256=1CAD1U27Uca_9KmR3SolimFqMrWVlWApKOFSWDvpeRY,8173
+vizro_mcp-0.1.4.dist-info/METADATA,sha256=3iHwiGkUAQpUM0zX0X47G5_0F6sSQARAcLa-eetlgXU,12413
+vizro_mcp-0.1.4.dist-info/WHEEL,sha256=WLgqFyCfm_KASv4WHyYy0P3pM_m7J5L9k2skdKLirC8,87
+vizro_mcp-0.1.4.dist-info/entry_points.txt,sha256=iSUzPHvx4Ogsn91tK2C0OHxI44SNCHT1F1zUqbTj5O0,45
+vizro_mcp-0.1.4.dist-info/licenses/LICENSE.txt,sha256=z8d0m5b2O9McPEK1xHG_dWgUBT6EfBDz6wA0F7xSPTA,11358
+vizro_mcp-0.1.4.dist-info/RECORD,,

{vizro_mcp-0.1.2.dist-info → vizro_mcp-0.1.4.dist-info}/WHEEL

@@ -1,4 +1,4 @@
 Wheel-Version: 1.0
-Generator: hatchling 1.27.0
+Generator: hatchling 1.28.0
 Root-Is-Purelib: true
 Tag: py3-none-any

vizro_mcp-0.1.2.dist-info/METADATA

@@ -1,323 +0,0 @@
-Metadata-Version: 2.4
-Name: vizro-mcp
-Version: 0.1.2
-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.42
-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 server
-
-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/vizro-mcp.gif" width="600" alt="Vizro MCP Demo">
-
-### Quick install
-
-| Host                                      | Prerequisite                                                  | Link                                                                                                                                                                                                                                                                                                                                   | Notes                                                                   |
-| ----------------------------------------- | ------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
-| [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/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)                                             |                                                                         |
-| [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/install-mcp?name=vizro-mcp&config=eyJjb21tYW5kIjoiZG9ja2VyIHJ1biAtaSAtLXJtIG1jcC92aXpybyJ9)                                                                          | 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) |
-
-## Features of Vizro-MCP
-
-Vizro-MCP provides tools and templates to create a functioning Vizro chart or dashboard step by step. Benefits include:
-
-✅ 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.
-
-### Without Vizro-MCP
-
-Without Vizro-MCP, if you try to make a dashboard using an LLM, it could choose any framework, and use it without specific guidance, design principles, or consistency. The results are:
-
-❌ A random choice of frontend framework or charting library.
-
-❌ 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.
-
-## 🛠️ Get started
-
-Vizro-MCP can be run in two ways: using [`uvx`](https://docs.astral.sh/uv/guides/tools/) or using [`Docker`](https://www.docker.com/get-started/). It works with any MCP-enabled LLM client such as Cursor or Claude Desktop.
-
-If you want to run Vizro-MCP directly from source, skip to the end of this page to [Development or running from source](#development-or-running-from-source).
-
-### Prerequisites
-
-- [uv](https://docs.astral.sh/uv/getting-started/installation/) **or** [Docker](https://www.docker.com/get-started/)
-- Any LLM application that supports MCP, such as [Claude Desktop](https://claude.ai/download) or [Cursor](https://www.cursor.com/downloads)
-
-### Setup Instructions
-
-The general server config is mostly the same for all hosts:
-
-#### 1. Set up configuration
-
-**Using `uvx`**
-
-```json
-{
-  "mcpServers": {
-    "vizro-mcp": {
-      "command": "uvx",
-      "args": [
-        "vizro-mcp"
-      ]
-    }
-  }
-}
-```
-
-**Using `Docker`**
-
-```json
-{
-  "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"
-      ]
-    }
-  }
-}
-```
-
-> To use local data with Vizro-MCP, mount your data directory or directories into the container. 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, it is recommended that the `dst` path matches the `src` path.
-
-#### 2. Add the Configuration to MCP enabled LLM applications
-
-In principle, the Vizro MCP server works with _any_ MCP enabled LLM applications but we recommend Claude Desktop or Cursor as popular choices (see more detailed instructions below). Different AI tools may use different setup methods or connection settings. Check each tool's docs for details.
-
-<details>
-<summary><strong>Claude Desktop</strong></summary>
-
-- Add the configuration to your `claude_desktop_config.json` ([found via Developer Settings](https://modelcontextprotocol.io/quickstart/user#2-add-the-filesystem-mcp-server)).
-
-- Restart Claude Desktop. After a few moments, you should see the vizro-mcp menu in the settings/context menu:
-
-    <img src="assets/claude_working.png" alt="Claude Desktop MCP Server Icon" width="300"/>
-
-> ⚠️ **Warning:** In some hosts (like Claude Desktop) the free plan might be less performant, which may cause issues when the request is too complex. In cases where the request causes the UI to crash, opt for using a paid plan, or reduce your request's complexity.
-
-</details>
-
-<details>
-<summary><strong>Cursor</strong></summary>
-<br >
-
-[![Install with UVX in Cursor](https://img.shields.io/badge/Cursor-Install-0098FF?style=flat-square&logo=visualstudiocode&logoColor=white)](https://cursor.com/install-mcp?name=vizro-mcp&config=eyJjb21tYW5kIjoidXZ4IHZpenJvLW1jcCJ9)
-
-- Add the above configuration to your `mcp.json` ([see Cursor Settings](https://docs.cursor.com/context/model-context-protocol#configuration-locations)) or click the button above.
-
-- After a short pause, you should see a green light in the MCP menu:
-
-    ![Cursor MCP Server Icon](assets/cursor_working.png)
-
-</details>
-
-<details>
-<summary><strong>Other MCP Clients</strong></summary>
-
-<br />
-
-[![Install with UVX in VS Code](https://img.shields.io/badge/VS_Code-Install_all-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)
-
-- Add the configuration as per your client's documentation.
-
-- Check your client's documentation for where to place the config and how to verify the server is running.
-
-</details>
-
-## 💻 Usage
-
-The MCP server is designed to get you started on Vizro dashboards and charts by creating beautiful working dashboards based on the core Vizro features. It is not designed to replace a human developer when going beyond the core features, e.g. when building an application that requires custom CSS or bespoke Dash components.
-
-### Use prompt templates to get specific dashboards quickly
-
-Prompt templates are not available in all MCP hosts, but when they are, you can use them to get specific dashboards quickly. To access them (e.g. in Claude Desktop), click on the plus icon below the chat, and choose _`Add from vizro-mcp`_.
-
-<img src="assets/claude_prompt.png" alt="Claude Desktop MCP Server Icon" width="300"/>
-
-The **easiest** way to get started with Vizro dashboards is to choose the template `create_starter_dashboard` and just send the prompt. This will create a super simple dashboard with one page, one chart, and one filter. Take it from there!
-
-### Create a Vizro dashboard based on local or remote data
-
-You can also ask the LLM to create specific dashboards based on local or remote data if you already have an idea of what you want. Example prompts could be:
-
-> _Create a Vizro dashboard with one page, a scatter chart, and a filter based on `<insert absolute file path or public URL>` data._
-
-> _Create a simple two page Vizro dashboard, with first page being a correlation analysis of `<insert absolute file path or public URL>` data, and the second page being a map plot of `<insert absolute file path or public URL>` data_
-
-You can find a set of sample CSVs to try out in the [Plotly repository](https://github.com/plotly/datasets/tree/master).
-
-You can even ask for a dashboard without providing data:
-
-> _Create a Vizro dashboard with one page, a scatter chart, and a filter._
-
-In general, it helps to specify Vizro in the prompt and to keep it as precise (and simple) as possible.
-
-### Get a live preview of your dashboard
-
-When the LLM chooses to use the tool `validate_dashboard_config`, and the tool executes successfully, the LLM will return a link to a live preview of the dashboard if only public data accessed via URL is used. By default, the LLM will even open the link in your browser for you unless you tell it not to. In Claude Desktop, you can see the output of the tool by opening the tool collapsible and scrolling down to the very bottom.
-
-<img src="assets/claude_validate.png" width="300"/>
-
-You can also ask the model to give you the link, but it will attempt to regenerate it, which is very error prone and slow.
-
-### Create Vizro charts
-
-If you don't want to create an entire Vizro dashboard, you can still use Vizro-MCP to create the code for a single chart. If you're not sure what kind of chart you want, check out the [Vizro Visual Vocabulary](https://huggingface.co/spaces/vizro/demo-visual-vocabulary) for ideas.
-
-The **easiest** way to create a Vizro chart is to choose the template `create_vizro_chart` and just send the prompt. This will create a simple chart that you can alter. Take it from there!
-
-Alternatively, you can just ask in the chat, for example:
-
-> _Create a scatter based on the iris dataset._
-
-> _Create a bar chart based on `<insert absolute file path or public URL>` data._
-
-## 🔍 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.
-
-In general the most critical part of the process is the `load_and_analyze_data` tool. This tool, running on your machine, will load local or remote data into a pandas DataFrame and provide a 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.
-
-The second most critical part is the `validate_dashboard_config` tool. This tool will attempt to instantiate the Vizro model configuration and return the Python code and visualization link for valid configurations. If the configuration is valid, it will also return and attempt to open 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.
-
-## Available Tools (if client allows)
-
-The Vizro MCP server provides the following tools. In general you should not need to use them directly, but in special cases you could ask the LLM to call them directly to help it find its way.
-
-- `get_vizro_chart_or_dashboard_plan` - Get a structured step-by-step plan for creating either a chart or dashboard. Provides guidance on the entire creation process.
-- `get_model_json_schema` - Retrieves the complete JSON schema for any specified Vizro model, useful for understanding required and optional parameters.
-- `validate_dashboard_config` - Tests Vizro model configurations by attempting to instantiate them. Returns Python code and visualization links for valid configurations.
-- `load_and_analyze_data` - Loads a CSV file from a local path or URL into a pandas DataFrame and provides detailed analysis of its structure and content.
-- `validate_chart_code` - Validates the code created for a chart and returns feedback on its correctness.
-- `get_sample_data_info` - Provides information about sample datasets that can be used for testing and development.
-
-## Available Prompts (if client allows)
-
-- `create_starter_dashboard` - Use this prompt template to get started with Vizro dashboards.
-- `create_dashboard` - Use this prompt template to create a dashboard based on a local or remote CSV dataset.
-- `create_vizro_chart` - Use this prompt template to create a Vizro styled plotly chart based on a local or remote CSV dataset.
-
-## Development or running from source
-
-If you are a developer, or if you are running Vizro-MCP from source, you need to clone the Vizro repo. 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 your 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`.
-
-## Disclaimers
-
-<details>
-<summary><strong>Third party API</strong></summary>
-
-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.
-
-</details>
-
-<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.
-
-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.2.dist-info/RECORD

@@ -1,14 +0,0 @@
-vizro_mcp/__init__.py,sha256=7rO7QeDAQXQ4DcfmJpU0uGgW7R0TMp2xgbAYNViFACE,379
-vizro_mcp/py.typed,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
-vizro_mcp/server.py,sha256=m4IQQlYve1p4fCkAPa5Cgtv9hnxykA7UHItrRVCVBWQ,12647
-vizro_mcp/_schemas/__init__.py,sha256=sCAIowgWm-qq8N3aMpVPx9WnbgoBal15AR3cg9rw8Yw,154
-vizro_mcp/_schemas/schemas.py,sha256=fWsx7iz99kIlff0d2TUGGUnlQ8lHez--gXkIFwbQ1pQ,8348
-vizro_mcp/_utils/__init__.py,sha256=ucPbfXe8kEFT7chz6ed_BeqAw71MnoWlZTYyCp4tPYY,1130
-vizro_mcp/_utils/configs.py,sha256=28ALgRgKYzRnPunSTjZxHFz2kyQy8yW4ZLhDgCUkE0s,3627
-vizro_mcp/_utils/prompts.py,sha256=YPk7fEVWkb1VGcRQ5uoFG8mGBnln65IK87GB0MXw9Fk,9754
-vizro_mcp/_utils/utils.py,sha256=XQcUBtyEd7eHCxQp4N92VUGsJ7bLwj9jSJVTgYCFRSc,7990
-vizro_mcp-0.1.2.dist-info/METADATA,sha256=fvXDcNLZq5Z1JEWjIFoId-shcR-6b-yOo-YoGUlGfS0,20077
-vizro_mcp-0.1.2.dist-info/WHEEL,sha256=qtCwoSJWgHk21S1Kb4ihdzI2rlJ1ZKaIurTj_ngOhyQ,87
-vizro_mcp-0.1.2.dist-info/entry_points.txt,sha256=iSUzPHvx4Ogsn91tK2C0OHxI44SNCHT1F1zUqbTj5O0,45
-vizro_mcp-0.1.2.dist-info/licenses/LICENSE.txt,sha256=z8d0m5b2O9McPEK1xHG_dWgUBT6EfBDz6wA0F7xSPTA,11358
-vizro_mcp-0.1.2.dist-info/RECORD,,