mcp-metricflow
A Model Context Protocol (MCP) server that provides MetricFlow CLI tools through both SSE (with optional API key authentication) and STDIO interfaces.
Table of Contents
Overview
This project provides a Model Context Protocol (MCP) server that wraps MetricFlow CLI commands, making them accessible through both Server-Sent Events (SSE) and Standard Input/Output (STDIO) interfaces. It enables seamless integration with Claude Desktop and other MCP-compatible clients.
Setup
# Install uv at https://docs.astral.sh/uv/getting-started/installation/
# Copy environment template
cp .env.template .env
# ...and then jump to # Configuration section to fulfill it
Configuration
Edit the .env file with your specific configuration:
# Required: Path to your dbt project
DBT_PROJECT_DIR=/path/to/your/dbt/project e.g. /Users/dat/repos/il/jaffle-shop
# Optional: Other configurations
DBT_PROFILES_DIR=/path/to/.dbt
MF_PATH=mf
MF_TMP_DIR=/path/to/tmp
# SSE server configuration (optional)
MCP_HOST=localhost
MCP_PORT=8000
# API key authentication for SSE mode (optional)
MCP_API_KEY=your-secret-api-key
MCP_REQUIRE_AUTH=false
Running the MCP Server
STDIO Mode ✅
For integration with Claude Desktop (or any other MCP Client tool), use STDIO mode with the following uvx command:
uvx --env-file /path/to/.env --with "mcp-metricflow[snowflake]" mcp-metricflow
Sample .env file:
DBT_PROJECT_DIR=/Users/xxx/sources/jaffle-shop
DBT_PROFILES_DIR=/Users/xxx/.dbt
MF_TMP_DIR=/Users/xxx/.dbt/tmp
Add this configuration to the respective client's config file:
{
"mcpServers": {
"mcp-metricflow": {
"command": "uvx",
"args": [
"--env-file", "<path-to-.env-file>",
"--with", "mcp-metricflow[snowflake]",
"mcp-metricflow"
]
},
}
}
NOTE: Currently only support Snowflake with this extra dependency specified:
"--with", "mcp-metricflow[snowflake]"
NOTE: We might have to use absolute path for example:
/Users/xxx/.local/bin/uvxinstead ofuvxalone. Usewhich uvxto get the full path
SSE Mode 🚧
For web-based integration or direct HTTP access:
# export DBT_PROFILES_DIR=~/.dbt
uv run python src/main_sse.py
The server will start on http://localhost:8000 (or the host/port specified in your environment variables).
API Key Authentication
The SSE server supports optional API key authentication. To enable authentication:
-
Set the required environment variables:
export MCP_API_KEY="your-secret-api-key" export MCP_REQUIRE_AUTH="true"
-
Access authenticated endpoints by including the API key in the Authorization header:
# Health check (no authentication required) curl http://localhost:8000/health # SSE endpoint (requires authentication when enabled) curl -H "Authorization: Bearer your-secret-api-key" http://localhost:8000/sse
Authentication Configuration:
MCP_API_KEY: The secret API key for authentication (required whenMCP_REQUIRE_AUTH=true)MCP_REQUIRE_AUTH: Enable/disable authentication (true,1,yes,onto enable; default:false)
Security Notes:
- The
/healthendpoint is always accessible without authentication for monitoring purposes - The
/sseendpoint requires authentication whenMCP_REQUIRE_AUTH=true - API keys are case-sensitive and support special characters
- Store API keys securely and avoid committing them to version control
Available Tools
The MCP server exposes the following MetricFlow CLI tools:
| Tool | Description | Required Parameters | Optional Parameters |
|---|---|---|---|
query |
Execute MetricFlow queries | session_id, metrics |
group_by, start_time, end_time, where, order, limit, saved_query, explain, show_dataflow_plan, show_sql_descriptions |
list_metrics |
List available metrics | None | search, show_all_dimensions |
list_dimensions |
List available dimensions | None | metrics |
list_entities |
List available entities | None | metrics |
list_dimension_values |
List values for a dimension | dimension, metrics |
start_time, end_time |
validate_configs |
Validate model configurations | None | dw_timeout, skip_dw, show_all, verbose_issues, semantic_validation_workers |
health_checks |
Perform system health checks | None | None |
Each tool includes comprehensive documentation accessible through the MCP interface.
Project Structure
src/
├── config/
│ └── config.py # Configuration management
├── server/
│ ├── auth.py # API key authentication
│ ├── sse_server.py # SSE server implementation
│ └── stdio_server.py # STDIO server implementation
├── tools/
│ ├── prompts/mf_cli/ # Tool documentation (*.md files)
│ ├── metricflow/ # MetricFlow CLI wrappers
│ │ ├── base.py # Shared command execution
│ │ ├── query.py # Query functionality
│ │ ├── list_metrics.py # List metrics
│ │ ├── list_dimensions.py # List dimensions
│ │ ├── list_entities.py # List entities
│ │ ├── list_dimension_values.py # List dimension values
│ │ ├── validate_configs.py # Configuration validation
│ │ └── health_checks.py # Health checks
│ └── cli_tools.py # MCP tool registration
├── utils/
│ ├── logger.py # Logging configuration
│ └── prompts.py # Prompt loading utilities
├── main_sse.py # SSE server entry point
└── main_stdio.py # STDIO server entry point
Contributing ✨
If you've ever wanted to contribute to this tool, and a great cause, now is your chance!
See the contributing docs CONTRIBUTING for more information.
If you've found this tool to be very helpful, please consider giving the repository a star, sharing it on social media, or even writing a blog post about it 💌
Finally, super thanks to our Contributors:
Metadata
Release files for mcp-metricflow 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mcp_metricflow-1.0.0.tar.gz | 39.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_metricflow-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 67.8 kB
Release files / mcp_metricflow-1.0.0.tar.gz
| Download URL | mcp_metricflow-1.0.0.tar.gz |
|---|---|
| Size | 39.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c8b7687c40a60cd331a177359a30889683e24cab410bbbfcfb5654e2bedf17ee
|
|
BLAKE2b-256 checksum How to use checksums |
a36f4db63b0a348227e1eb6e2ff23e83a90efd912799e4b3c7684858159ef61a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 29, 2025.
Transparency logRelease files / mcp_metricflow-1.0.0-py3-none-any.whl
| Download URL | mcp_metricflow-1.0.0-py3-none-any.whl |
|---|---|
| Size | 28.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7f9a544b813a37893aff8ec82ac1f67f642e55df57073022bc9716aee8b031e0
|
|
BLAKE2b-256 checksum How to use checksums |
615d2e69076a977abe4ae64227c44e178335a68162a7f9a4a5f53441f54a1486
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 29, 2025.
Transparency logSecurity for mcp-metricflow 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for mcp_metricflow-1.0.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 29, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.