dbt Semantic Layer MCP Server

Created By
TommyBeza year ago
MCP Server for querying DBT Semantic Layer
Overview

What is dbt Semantic Layer MCP Server?

The dbt Semantic Layer MCP Server is a Model-Connector-Presenter server that facilitates seamless querying of the dbt Semantic Layer through AI assistants like Claude Desktop.

How to use dbt Semantic Layer MCP Server?

To use the MCP Server, install it via Smithery and configure it with your dbt Cloud account. Once set up, you can interact with the dbt Semantic Layer using natural language queries through your AI assistant.

Key features of dbt Semantic Layer MCP Server?

  • 🔍 Metric Discovery: Browse and search available metrics in your dbt Semantic Layer.
  • 📊 Query Creation: Generate and execute semantic queries through natural language.
  • 🧮 Data Analysis: Filter, group, and order metrics for deeper insights.
  • 📈 Result Visualization: Display query results in an easy-to-understand format.

Use cases of dbt Semantic Layer MCP Server?

  1. Querying business metrics directly through natural language.
  2. Analyzing data trends and metrics with dimensional breakdowns.
  3. Visualizing results within AI assistant interfaces for better decision-making.

FAQ from dbt Semantic Layer MCP Server?

  • What do I need to use this server?

You need a dbt Cloud account with Semantic Layer enabled and API access to your dbt Cloud instance.

  • How do I install the MCP Server?

The recommended way to install is via Smithery using the command: npx -y @smithery/cli install @TommyBez/dbt-semantic-layer-mcp --client claude.

  • What can I ask the MCP Server?

You can ask about available metrics, query specific metrics, and analyze trends using natural language.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
TommyBez
Star
1
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago